It’s True, “We” Don’t Care About Accessibility on Linux

https://tesk.page/2025/06/18/its-true-we-dont-care-about-accessibility-on-linux/

#linux #a11y #foss #accessibility

It’s True, “We” Don’t Care About Accessibility on Linux

https://tesk.page/2025/06/18/its-true-we-dont-care-about-accessibility-on-linux/

#linux #a11y #foss #accessibility

Steam just added screen reader support in the latest Big Picture Mode beta. On the Deck. On SteamOS. On Linux.
Not hacked in. Not community-patched. Built-in. From Valve.
There's an accessibility tab. There's a screen reader. There's high-contrast mode, UI scaling, color filters, reduced motion, and more.
I can’t believe I’m saying this but: I need a Steam Deck now.
Accessibility isn’t just coming to gaming — it’s here, and it’s official.
Let’s make some noise so they keep going.
🔗 https://www.theverge.com/games/689922/steam-is-adding-screen-reader-support-and-other-accessibility-tools
#Accessibility #Gaming #SteamDeck #ScreenReader #Linux #valve

Steam just added screen reader support in the latest Big Picture Mode beta. On the Deck. On SteamOS. On Linux.
Not hacked in. Not community-patched. Built-in. From Valve.
There's an accessibility tab. There's a screen reader. There's high-contrast mode, UI scaling, color filters, reduced motion, and more.
I can’t believe I’m saying this but: I need a Steam Deck now.
Accessibility isn’t just coming to gaming — it’s here, and it’s official.
Let’s make some noise so they keep going.
🔗 https://www.theverge.com/games/689922/steam-is-adding-screen-reader-support-and-other-accessibility-tools
#Accessibility #Gaming #SteamDeck #ScreenReader #Linux #valve

I didn’t plan to write about Wayland yet. But Xorg is dying — not eventually, but now. GNOME’s dropping X11 support. RHEL already removed it. Ubuntu and Fedora are next. And if you rely on accessibility, you don’t get to wait this one out.
So here’s Post 4 of I Want to Love Linux. It Doesn’t Love Me Back.
I’m using Wayland now. Primarily. Not because I love it. Because the fallback is disappearing, and I want to be there helping fix what comes next. GNOME with Orca actually works. KDE and COSMIC are making progress. I’ve talked to the people involved. They care.
But a lot is broken.
MATE — the desktop most blind users preferred — isn’t on Wayland.
ocrdesktop doesn’t work. xdotool is gone.
wlroots compositors still don’t reliably support Orca’s keybindings, especially on laptops.
This isn’t GNOME’s fault. They’re the only reason accessibility on Wayland works at all.
But the old excuses are gone. “Just use Xorg” isn’t going to be an option much longer.
So yeah. I’m a Wayland shill now. Because I’m using it. Because I have to.
And I want to make sure we’re not excluded from what comes next.
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/
#Linux #Wayland #Accessibility #Orca #GNOME #KDE #COSMIC #FOSS #a11y #BlindTech #xorg

I didn’t plan to write about Wayland yet. But Xorg is dying — not eventually, but now. GNOME’s dropping X11 support. RHEL already removed it. Ubuntu and Fedora are next. And if you rely on accessibility, you don’t get to wait this one out.
So here’s Post 4 of I Want to Love Linux. It Doesn’t Love Me Back.
I’m using Wayland now. Primarily. Not because I love it. Because the fallback is disappearing, and I want to be there helping fix what comes next. GNOME with Orca actually works. KDE and COSMIC are making progress. I’ve talked to the people involved. They care.
But a lot is broken.
MATE — the desktop most blind users preferred — isn’t on Wayland.
ocrdesktop doesn’t work. xdotool is gone.
wlroots compositors still don’t reliably support Orca’s keybindings, especially on laptops.
This isn’t GNOME’s fault. They’re the only reason accessibility on Wayland works at all.
But the old excuses are gone. “Just use Xorg” isn’t going to be an option much longer.
So yeah. I’m a Wayland shill now. Because I’m using it. Because I have to.
And I want to make sure we’re not excluded from what comes next.
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/
#Linux #Wayland #Accessibility #Orca #GNOME #KDE #COSMIC #FOSS #a11y #BlindTech #xorg

I didn’t plan to write about Wayland yet. But Xorg is dying — not eventually, but now. GNOME’s dropping X11 support. RHEL already removed it. Ubuntu and Fedora are next. And if you rely on accessibility, you don’t get to wait this one out.
So here’s Post 4 of I Want to Love Linux. It Doesn’t Love Me Back.
I’m using Wayland now. Primarily. Not because I love it. Because the fallback is disappearing, and I want to be there helping fix what comes next. GNOME with Orca actually works. KDE and COSMIC are making progress. I’ve talked to the people involved. They care.
But a lot is broken.
MATE — the desktop most blind users preferred — isn’t on Wayland.
ocrdesktop doesn’t work. xdotool is gone.
wlroots compositors still don’t reliably support Orca’s keybindings, especially on laptops.
This isn’t GNOME’s fault. They’re the only reason accessibility on Wayland works at all.
But the old excuses are gone. “Just use Xorg” isn’t going to be an option much longer.
So yeah. I’m a Wayland shill now. Because I’m using it. Because I have to.
And I want to make sure we’re not excluded from what comes next.
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/
#Linux #Wayland #Accessibility #Orca #GNOME #KDE #COSMIC #FOSS #a11y #BlindTech #xorg

Steam just added screen reader support in the latest Big Picture Mode beta. On the Deck. On SteamOS. On Linux.
Not hacked in. Not community-patched. Built-in. From Valve.
There's an accessibility tab. There's a screen reader. There's high-contrast mode, UI scaling, color filters, reduced motion, and more.
I can’t believe I’m saying this but: I need a Steam Deck now.
Accessibility isn’t just coming to gaming — it’s here, and it’s official.
Let’s make some noise so they keep going.
🔗 https://www.theverge.com/games/689922/steam-is-adding-screen-reader-support-and-other-accessibility-tools
#Accessibility #Gaming #SteamDeck #ScreenReader #Linux #valve

Steam just added screen reader support in the latest Big Picture Mode beta. On the Deck. On SteamOS. On Linux.
Not hacked in. Not community-patched. Built-in. From Valve.
There's an accessibility tab. There's a screen reader. There's high-contrast mode, UI scaling, color filters, reduced motion, and more.
I can’t believe I’m saying this but: I need a Steam Deck now.
Accessibility isn’t just coming to gaming — it’s here, and it’s official.
Let’s make some noise so they keep going.
🔗 https://www.theverge.com/games/689922/steam-is-adding-screen-reader-support-and-other-accessibility-tools
#Accessibility #Gaming #SteamDeck #ScreenReader #Linux #valve

I didn’t plan to write about Wayland yet. But Xorg is dying — not eventually, but now. GNOME’s dropping X11 support. RHEL already removed it. Ubuntu and Fedora are next. And if you rely on accessibility, you don’t get to wait this one out.
So here’s Post 4 of I Want to Love Linux. It Doesn’t Love Me Back.
I’m using Wayland now. Primarily. Not because I love it. Because the fallback is disappearing, and I want to be there helping fix what comes next. GNOME with Orca actually works. KDE and COSMIC are making progress. I’ve talked to the people involved. They care.
But a lot is broken.
MATE — the desktop most blind users preferred — isn’t on Wayland.
ocrdesktop doesn’t work. xdotool is gone.
wlroots compositors still don’t reliably support Orca’s keybindings, especially on laptops.
This isn’t GNOME’s fault. They’re the only reason accessibility on Wayland works at all.
But the old excuses are gone. “Just use Xorg” isn’t going to be an option much longer.
So yeah. I’m a Wayland shill now. Because I’m using it. Because I have to.
And I want to make sure we’re not excluded from what comes next.
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/
#Linux #Wayland #Accessibility #Orca #GNOME #KDE #COSMIC #FOSS #a11y #BlindTech #xorg

Steam just added screen reader support in the latest Big Picture Mode beta. On the Deck. On SteamOS. On Linux.
Not hacked in. Not community-patched. Built-in. From Valve.
There's an accessibility tab. There's a screen reader. There's high-contrast mode, UI scaling, color filters, reduced motion, and more.
I can’t believe I’m saying this but: I need a Steam Deck now.
Accessibility isn’t just coming to gaming — it’s here, and it’s official.
Let’s make some noise so they keep going.
🔗 https://www.theverge.com/games/689922/steam-is-adding-screen-reader-support-and-other-accessibility-tools
#Accessibility #Gaming #SteamDeck #ScreenReader #Linux #valve

Steam just added screen reader support in the latest Big Picture Mode beta. On the Deck. On SteamOS. On Linux.
Not hacked in. Not community-patched. Built-in. From Valve.
There's an accessibility tab. There's a screen reader. There's high-contrast mode, UI scaling, color filters, reduced motion, and more.
I can’t believe I’m saying this but: I need a Steam Deck now.
Accessibility isn’t just coming to gaming — it’s here, and it’s official.
Let’s make some noise so they keep going.
🔗 https://www.theverge.com/games/689922/steam-is-adding-screen-reader-support-and-other-accessibility-tools
#Accessibility #Gaming #SteamDeck #ScreenReader #Linux #valve

I wanna give a shoutout to all the people working on making accessibility on Linux a better place. There is still a lot of work to do, with frustrating barriers. However, there are a lot of people working in projects like KDE, GNOME, Elementary, etc. who truly care about accessibility, and want to see it get better.

In my opinion, the more people who are given the opportunity to use computers in a way that works for them, the better.

#accessibility #linux

I didn’t plan to write about Wayland yet. But Xorg is dying — not eventually, but now. GNOME’s dropping X11 support. RHEL already removed it. Ubuntu and Fedora are next. And if you rely on accessibility, you don’t get to wait this one out.
So here’s Post 4 of I Want to Love Linux. It Doesn’t Love Me Back.
I’m using Wayland now. Primarily. Not because I love it. Because the fallback is disappearing, and I want to be there helping fix what comes next. GNOME with Orca actually works. KDE and COSMIC are making progress. I’ve talked to the people involved. They care.
But a lot is broken.
MATE — the desktop most blind users preferred — isn’t on Wayland.
ocrdesktop doesn’t work. xdotool is gone.
wlroots compositors still don’t reliably support Orca’s keybindings, especially on laptops.
This isn’t GNOME’s fault. They’re the only reason accessibility on Wayland works at all.
But the old excuses are gone. “Just use Xorg” isn’t going to be an option much longer.
So yeah. I’m a Wayland shill now. Because I’m using it. Because I have to.
And I want to make sure we’re not excluded from what comes next.
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/
#Linux #Wayland #Accessibility #Orca #GNOME #KDE #COSMIC #FOSS #a11y #BlindTech #xorg

Ooo lookie, accessibility is not planned. Lol. As usual. Cause foss is just a toy that no one actually depends on.

https://github.com/Ylianst/MeshCentral/issues/3355

#accessibility #foss #RemoteDesktop #Mesh

Seeing #CSS carousels being promoted as accessible again, so here is a periodic reminder:

#CSS carousels are not "accessible by default" https://www.sarasoueidan.com/blog/css-carousels-accessibility/

They are still highly experimental and there are still many open #accessibility questions & issues being discussed.

+The browser will not do everything for you—you'll still have work to do, too.

Seeing #CSS carousels being promoted as accessible again, so here is a periodic reminder:

#CSS carousels are not "accessible by default" https://www.sarasoueidan.com/blog/css-carousels-accessibility/

They are still highly experimental and there are still many open #accessibility questions & issues being discussed.

+The browser will not do everything for you—you'll still have work to do, too.

Hey unsighted fedi-folx! When it comes to good alt-text...

Please select all that apply.

#Poll #Accessibility #AltText

Hey unsighted fedi-folx! When it comes to good alt-text...

Please select all that apply.

#Poll #Accessibility #AltText

Hey unsighted fedi-folx! When it comes to good alt-text...

Please select all that apply.

#Poll #Accessibility #AltText

Hey unsighted fedi-folx! When it comes to good alt-text...

Please select all that apply.

#Poll #Accessibility #AltText

URGENT: Accessibility for disabled people is about to be removed from federal buildings —unless we act by MONDAY.
Taking action will require only three minutes of your time.

The U.S. Department of Energy (DOE) has issued a "direct final rule" that would eliminate the long-standing requirement that new buildings constructed with federal funds must be accessible to people with disabilities.
They claim it’s “unnecessary” and “burdensome.” But here’s what eliminating this rule really means:
New federally funded buildings could be built without ramps, elevators, accessible bathrooms, or doors.
There would be no enforceable standards for accessibility in construction or major renovations.
It weakens the civil rights protections guaranteed by Section 504 of the Rehabilitation Act.

This rule will take effect July 15 unless the public pushes back. We have until Monday, June 16 to submit comments.

👉 Take a minute now and submit comments.

📧 You can Email your comments to: DOEGeneralCounsel@hq.doe.gov

Your email comment doesn’t need to be long. Just say why you oppose removing accessibility protections and why they matter to you or your community.

And/or you can use these forms from the National Association of Councils on Developmental Disabilities (which I suspect will also get you on their mailing list):

➡️ Public comment #1 https://nacdd.quorum.us/campaign/128333/

➡️ Public Comment #2 https://nacdd.quorum.us/campaign/128336/

Please speak up—and share this widely. We cannot let accessibility be rolled back without a fight.
Thank you.

#Accessibility
#Disability #USpol

URGENT: Accessibility for disabled people is about to be removed from federal buildings —unless we act by MONDAY.
Taking action will require only three minutes of your time.

The U.S. Department of Energy (DOE) has issued a "direct final rule" that would eliminate the long-standing requirement that new buildings constructed with federal funds must be accessible to people with disabilities.
They claim it’s “unnecessary” and “burdensome.” But here’s what eliminating this rule really means:
New federally funded buildings could be built without ramps, elevators, accessible bathrooms, or doors.
There would be no enforceable standards for accessibility in construction or major renovations.
It weakens the civil rights protections guaranteed by Section 504 of the Rehabilitation Act.

This rule will take effect July 15 unless the public pushes back. We have until Monday, June 16 to submit comments.

👉 Take a minute now and submit comments.

📧 You can Email your comments to: DOEGeneralCounsel@hq.doe.gov

Your email comment doesn’t need to be long. Just say why you oppose removing accessibility protections and why they matter to you or your community.

And/or you can use these forms from the National Association of Councils on Developmental Disabilities (which I suspect will also get you on their mailing list):

➡️ Public comment #1 https://nacdd.quorum.us/campaign/128333/

➡️ Public Comment #2 https://nacdd.quorum.us/campaign/128336/

Please speak up—and share this widely. We cannot let accessibility be rolled back without a fight.
Thank you.

#Accessibility
#Disability #USpol

This felt too valuable not to share. Braille-labeled maps of washrooms to help people find and use facilities in the washroom. Everyone deserves to get in, do their business, wash their hands, and get out in peace and safety.

This seems valuable for all public spaces.

#Blind #Accessibility

if you are under 30 years old and picking a font size for something other people need to read, not just yourself: that’s too small. still too small. A LITTLE BIGGER

#accessibility #ux #typography

if you are under 30 years old and picking a font size for something other people need to read, not just yourself: that’s too small. still too small. A LITTLE BIGGER

#accessibility #ux #typography

This felt too valuable not to share. Braille-labeled maps of washrooms to help people find and use facilities in the washroom. Everyone deserves to get in, do their business, wash their hands, and get out in peace and safety.

This seems valuable for all public spaces.

#Blind #Accessibility

This felt too valuable not to share. Braille-labeled maps of washrooms to help people find and use facilities in the washroom. Everyone deserves to get in, do their business, wash their hands, and get out in peace and safety.

This seems valuable for all public spaces.

#Blind #Accessibility

URGENT: Accessibility for disabled people is about to be removed from federal buildings —unless we act by MONDAY.
Taking action will require only three minutes of your time.

The U.S. Department of Energy (DOE) has issued a "direct final rule" that would eliminate the long-standing requirement that new buildings constructed with federal funds must be accessible to people with disabilities.
They claim it’s “unnecessary” and “burdensome.” But here’s what eliminating this rule really means:
New federally funded buildings could be built without ramps, elevators, accessible bathrooms, or doors.
There would be no enforceable standards for accessibility in construction or major renovations.
It weakens the civil rights protections guaranteed by Section 504 of the Rehabilitation Act.

This rule will take effect July 15 unless the public pushes back. We have until Monday, June 16 to submit comments.

👉 Take a minute now and submit comments.

📧 You can Email your comments to: DOEGeneralCounsel@hq.doe.gov

Your email comment doesn’t need to be long. Just say why you oppose removing accessibility protections and why they matter to you or your community.

And/or you can use these forms from the National Association of Councils on Developmental Disabilities (which I suspect will also get you on their mailing list):

➡️ Public comment #1 https://nacdd.quorum.us/campaign/128333/

➡️ Public Comment #2 https://nacdd.quorum.us/campaign/128336/

Please speak up—and share this widely. We cannot let accessibility be rolled back without a fight.
Thank you.

#Accessibility
#Disability #USpol

if you are under 30 years old and picking a font size for something other people need to read, not just yourself: that’s too small. still too small. A LITTLE BIGGER

#accessibility #ux #typography

Adaptive Keyboards & Writing Technologies for One-Handed Users - After having been involved in an accident, [Kurt Kohlstedt] suffered peripheral ne... - https://hackaday.com/2025/06/15/adaptive-keyboards-writing-technologies-for-one-handed-users/ #physicaldisability #peripheralshacks #keyboardlayouts #computerhacks #accessibility

This felt too valuable not to share. Braille-labeled maps of washrooms to help people find and use facilities in the washroom. Everyone deserves to get in, do their business, wash their hands, and get out in peace and safety.

This seems valuable for all public spaces.

#Blind #Accessibility

We need urgent community action to stop this incredibly ableist plan from moving forward.

The DOE has ruled that new federal buildings don’t have to meet accessibility standards.

That will mean many disabled people won’t be able to work in or access these places.

They’re literally excluding us from as many facets of life as possible, because they have a eugenics plan.

Call, email, speak out!

Accessibility is not a “nice to have”. It’s a legal right. It’s necessary for our survival.

https://www.federalregister.gov/documents/2025/05/16/2025-08535/rescinding-new-construction-requirements-related-to-nondiscrimination-in-federally-assisted-programs

#uspol #fascism #disability #chronicillness #ableism #accessibility #doe

We need urgent community action to stop this incredibly ableist plan from moving forward.

The DOE has ruled that new federal buildings don’t have to meet accessibility standards.

That will mean many disabled people won’t be able to work in or access these places.

They’re literally excluding us from as many facets of life as possible, because they have a eugenics plan.

Call, email, speak out!

Accessibility is not a “nice to have”. It’s a legal right. It’s necessary for our survival.

https://www.federalregister.gov/documents/2025/05/16/2025-08535/rescinding-new-construction-requirements-related-to-nondiscrimination-in-federally-assisted-programs

#uspol #fascism #disability #chronicillness #ableism #accessibility #doe

During the @w3c meeting in April 2025, Shadi Abou-Zhara discussed the relationship between #accessibility standards and regulations, particularly focusing on W3C's Web Content Accessibility Guidelines (#WCAG).

He urged recognizing policymakers as key stakeholders and called for a more granular approach in standards to better guide regulations and reflect the needs of people with #disabilities.

🎬 Watch "Accessibility and regulations": https://youtu.be/M7-u2UUR-wI

💚 With support from @nlnet , we've addressed a tonne of tech debt (including #editor redo), and we're improving #dokieli's #UI, #accessibility, annotations, #security, and #offline support. But we have more work to do! See our roadmap: https://dokie.li/docs#roadmap

We are planning to implement collaborative editing, encryption, and develop #credibility features to combat #misinformation on the web, in collaboration with Fundacion Cibervoluntarios: https://www.cibervoluntarios.org/es/actualidad/post/dokieli-y-fundacion-cibervoluntarios-unidos-en-la-creacion-de-una-herramienta-que-permite-a-la-ciudadania-un-uso-reflexivo-de-la-informacion-y-el-control-de-sus-datos

💚 With support from @nlnet , we've addressed a tonne of tech debt (including #editor redo), and we're improving #dokieli's #UI, #accessibility, annotations, #security, and #offline support. But we have more work to do! See our roadmap: https://dokie.li/docs#roadmap

We are planning to implement collaborative editing, encryption, and develop #credibility features to combat #misinformation on the web, in collaboration with Fundacion Cibervoluntarios: https://www.cibervoluntarios.org/es/actualidad/post/dokieli-y-fundacion-cibervoluntarios-unidos-en-la-creacion-de-una-herramienta-que-permite-a-la-ciudadania-un-uso-reflexivo-de-la-informacion-y-el-control-de-sus-datos

Apple’s ‘liquid glass’ contrast hilarity is now a bullet on my post “I Don’t Care What Google or Apple or Whoever Did”
https://adrianroselli.com/2020/03/i-dont-care-what-google-or-apple-or-whomever-did.html

Please please PLEASE do not copy Aero, er, Glass in your Figmas.

#accessibility #a11y #UX

During the @w3c meeting in April 2025, Shadi Abou-Zhara discussed the relationship between #accessibility standards and regulations, particularly focusing on W3C's Web Content Accessibility Guidelines (#WCAG).

He urged recognizing policymakers as key stakeholders and called for a more granular approach in standards to better guide regulations and reflect the needs of people with #disabilities.

🎬 Watch "Accessibility and regulations": https://youtu.be/M7-u2UUR-wI

I see obvious issues from a contrast perspective, but also: "Liquid Glass" looks absolutely horrendous from an ADHD perspective. Yes, let's have the static part of the UI literally flash and draw attention as it remains still!

These Apple press demos are wildly distracting to my eye; I'm happy I don't use any Apple products, but don't look forward to everyone trying to copy the worst parts of this gaudy aesthetic.

#accessibility #a11y #LiquidGlass #apple #wwdc #wwdc25 #wwdc2025

Oh, look. Accessibility horrors beyond comprehension from a company with so much money the human mind boggles to comprehend it.

Accessibility horrors so blatant it takes one glance to identify many of the more offensive failings.

Accessibility horrors that are so inaccessible that even the completely able struggle.

Accessibility horrors that are covered in the very first class of any UI/UX design or front-end development education.

Accessibility horrors that you have to force through because even the worst testers are screaming at you.

#WWDC #WWDC25 #Apple #a11y #Accessibility

Oh, look. Accessibility horrors beyond comprehension from a company with so much money the human mind boggles to comprehend it.

Accessibility horrors so blatant it takes one glance to identify many of the more offensive failings.

Accessibility horrors that are so inaccessible that even the completely able struggle.

Accessibility horrors that are covered in the very first class of any UI/UX design or front-end development education.

Accessibility horrors that you have to force through because even the worst testers are screaming at you.

#WWDC #WWDC25 #Apple #a11y #Accessibility

Just 12 settings in the Mastodon official Android client.
Not one of them deals with Accessibility.

After so much resources and attention, still failing basic equalities is unconscionable.
#Mastodon #Accessibility

Tried out #GoogleAssistant, which claims it can function while you are offline, because I miss #Bixby (which #Samsung disabled in Japan).

But it didn't work at all offline. Even asking it to tell me the time just yielded a message telling me that I'd need to enable Wi-Fi to get the answer.

Tried the Voice Assistant in the #accessibility settings as well, and it really didn't work very well.

People who need this functionality for accessibility reasons must be so frustrated. How is this okay?

Fun! So the tech bros are already whining about this. Add reminder when about to post without alt text in web UI (#33760 and #33784 by Gargron)

Cry harder. My sympathy is at zero.

From https://github.com/mastodon/mastodon/releases/tag/v4.4.0-beta.1 #AltText #Accessibility #Mastodon #Fediverse

I’m having some availability opening up for dataviz/web accessibility reviews, consulting, talks and training from October onwards.

And as a fun aside, the work will be done from an island a little bit above 70°N in the Norwegian arctic, under the northern lights (or midnight sun in summer), surrounded by whales, rich birdlife, and a whole lot of weather 🤩

Interested? 👉🏻 Direct message or collab@fossheim.io

More info 👇🏻
https://fossheim.io/work/

#accessibility #a11y

I’m having some availability opening up for dataviz/web accessibility reviews, consulting, talks and training from October onwards.

And as a fun aside, the work will be done from an island a little bit above 70°N in the Norwegian arctic, under the northern lights (or midnight sun in summer), surrounded by whales, rich birdlife, and a whole lot of weather 🤩

Interested? 👉🏻 Direct message or collab@fossheim.io

More info 👇🏻
https://fossheim.io/work/

#accessibility #a11y

Fellow disabled players! 👋
For research: What were the most toxic comments you had to experience when talking about game accessibility on social media? Please feel free to DM me or flag your response with a CW, so that others don't have to read it and become retraumatised.
#GameDev #Accessibility #Disability

I'm looking for a markdown editor for Windows that’s accessible with JAWS. I currently use iA Writer but not sure how well it works with a screen reader. I also need the ability to export to Word. Any recommendations? Thanks. #BlindTech #JAWS #Markdown #Accessibility #WindowsApps #ScreenReader #WordExport

Color blindness simulator: Takes an image and shows what it looks like with varying vision. This one has academic citations for the simulation filters
https://daltonlens.org/colorblindness-simulator
#colorblindness #accessibility #colorblind #images #color #web #+

Color blindness simulator: Takes an image and shows what it looks like with varying vision. This one has academic citations for the simulation filters
https://daltonlens.org/colorblindness-simulator
#colorblindness #accessibility #colorblind #images #color #web #+

Fellow disabled players! 👋
For research: What were the most toxic comments you had to experience when talking about game accessibility on social media? Please feel free to DM me or flag your response with a CW, so that others don't have to read it and become retraumatised.
#GameDev #Accessibility #Disability

I’ve published Part 3 of “I Want to Love Linux. It Doesn’t Love Me Back.”

This one’s about the so-called universal interface: the console. The raw, non-GUI, text-mode TTY. The place where sighted Linux users fall back when the desktop breaks, and where blind users are supposed to do the same. Except — we can’t. Not reliably. Not safely. Not without building the entire stack ourselves.

This post covers Speakup, BRLTTY, Fenrir, and the audio subsystem hell that makes screen reading in the console a game of chance. It dives into why session-locked audio breaks espeakup, why BRLTTY fails silently and eats USB ports, why the console can be a full environment — and why it’s still unusable out of the box. And yes, it calls out the fact that if you’re deafblind, and BRLTTY doesn’t start, you’re just locked out of the machine entirely. No speech. No visuals. Just a dead black box.

There are workarounds. Scripts. Hacks. Weird client.conf magic that you run once as root, once as a user, and pray to PipeWire that it sticks. Some of this I learned from a reader of post 1. None of it is documented. None of it is standard. And none of it should be required.

This is a long one. Technical, and very real. Because the console should be the one place Linux accessibility never breaks. And it’s the one place that’s been left to rot.

Link to the post: https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-3-speakup-brltty-and-the-forgotten-infrastructure-of-console-access/

#Linux #Accessibility #BlindTech #BRLTTY #Speakup #Fenrir #TTY #PipeWire #ScreenReader #DisabilityTech #ConsoleComputing #LinuxAccessibility #FOSS

I’ve published Part 3 of “I Want to Love Linux. It Doesn’t Love Me Back.”

This one’s about the so-called universal interface: the console. The raw, non-GUI, text-mode TTY. The place where sighted Linux users fall back when the desktop breaks, and where blind users are supposed to do the same. Except — we can’t. Not reliably. Not safely. Not without building the entire stack ourselves.

This post covers Speakup, BRLTTY, Fenrir, and the audio subsystem hell that makes screen reading in the console a game of chance. It dives into why session-locked audio breaks espeakup, why BRLTTY fails silently and eats USB ports, why the console can be a full environment — and why it’s still unusable out of the box. And yes, it calls out the fact that if you’re deafblind, and BRLTTY doesn’t start, you’re just locked out of the machine entirely. No speech. No visuals. Just a dead black box.

There are workarounds. Scripts. Hacks. Weird client.conf magic that you run once as root, once as a user, and pray to PipeWire that it sticks. Some of this I learned from a reader of post 1. None of it is documented. None of it is standard. And none of it should be required.

This is a long one. Technical, and very real. Because the console should be the one place Linux accessibility never breaks. And it’s the one place that’s been left to rot.

Link to the post: https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-3-speakup-brltty-and-the-forgotten-infrastructure-of-console-access/

#Linux #Accessibility #BlindTech #BRLTTY #Speakup #Fenrir #TTY #PipeWire #ScreenReader #DisabilityTech #ConsoleComputing #LinuxAccessibility #FOSS

Just published a blog post tearing into hCaptcha’s so-called “accessibility” mode.

It’s not accessibility. It’s a cookie. And to get that cookie, you now have to submit your email and send a code via SMS to an U.S. phone number. It fails silently. It doesn’t confirm anything. You click “Confirm Code” and get “An error has occurred.” No cookie. No fallback. No support. And if you somehow get it? It’s a third-party cookie your browser probably blocks, and it expires. Then you get to do it all again.

Meanwhile, hCaptcha’s text-based challenge — the only mode that might actually work with a screen reader — isn’t tied to the cookie at all. It only shows up if the website owner specifically enables it. Most don’t. So even if you’re blind, even if you’re using assistive tech, you get the same unusable image grid as everyone else.

This isn’t accessibility. It’s exclusion wrapped in PR.

The blog post breaks it all down: how the cookie flow works (or doesn’t), why the system is broken by design, how developers got misled, and what real alternatives look like. If you care about accessible design or just want to understand how bad this gets, read it.

Link: https://fireborn.mataroa.blog/blog/hellcaptcha-accessibility-theater-at-its-worst/

#Accessibility #a11y #BlindTech #hCaptcha #HellCaptcha #UX #WebDev #ScreenReaders #Disability #TechRant #DevTools #Ableism #Privacy #FOSS #Inclusion

Just published a blog post tearing into hCaptcha’s so-called “accessibility” mode.

It’s not accessibility. It’s a cookie. And to get that cookie, you now have to submit your email and send a code via SMS to an U.S. phone number. It fails silently. It doesn’t confirm anything. You click “Confirm Code” and get “An error has occurred.” No cookie. No fallback. No support. And if you somehow get it? It’s a third-party cookie your browser probably blocks, and it expires. Then you get to do it all again.

Meanwhile, hCaptcha’s text-based challenge — the only mode that might actually work with a screen reader — isn’t tied to the cookie at all. It only shows up if the website owner specifically enables it. Most don’t. So even if you’re blind, even if you’re using assistive tech, you get the same unusable image grid as everyone else.

This isn’t accessibility. It’s exclusion wrapped in PR.

The blog post breaks it all down: how the cookie flow works (or doesn’t), why the system is broken by design, how developers got misled, and what real alternatives look like. If you care about accessible design or just want to understand how bad this gets, read it.

Link: https://fireborn.mataroa.blog/blog/hellcaptcha-accessibility-theater-at-its-worst/

#Accessibility #a11y #BlindTech #hCaptcha #HellCaptcha #UX #WebDev #ScreenReaders #Disability #TechRant #DevTools #Ableism #Privacy #FOSS #Inclusion

Time is short — submit to #ID24 today (or tomorrow, or I guess maybe Saturday):
https://inclusivedesign24.org/2025/

Submission window closes 31 May.

Then block out your calendar for ID24 on 25 September 2025 (or maybe block it out _before_ you submit).

Also, follow @inclusivedesign24.

#accessibility #a11y

Time is short — submit to #ID24 today (or tomorrow, or I guess maybe Saturday):
https://inclusivedesign24.org/2025/

Submission window closes 31 May.

Then block out your calendar for ID24 on 25 September 2025 (or maybe block it out _before_ you submit).

Also, follow @inclusivedesign24.

#accessibility #a11y

After a lot of reflection, I’ve left the Master of Educational Neuroscience. A few things pushed the decision. Poor admin was a factor, but more importantly, I realised I hate doing research and I’ve had to face some fears I’ve avoided for a long time. I’ve gone back to the Master of Counselling I started a few years ago.

The neuroscience knowledge is still incredibly valuable and will shape how I practise, but I need something that gives me practical skills to work with people now. I’m not sure a PhD is something I want to pursue, and I don’t want to put all my eggs in one basket.

Now I have to decide where to finish the course. I’m enrolled at a private counselling college that has offered me a partial scholarship. They specialise in counselling, which is a strength, but classes run from 5:30 to 9 pm twice a week, which is when I function least well. The other option is returning to the same university where I started. I’ve already completed two units there, and while there’s no scholarship, the structure might suit me better.

Decision fatigue is real.

#neurodivergent #audhd #academiclife #counselling #careerchange #chronicfatigue #realworldskills #neuroscience #highered #wellbeing #accessibility #actuallyautistic

After a lot of reflection, I’ve left the Master of Educational Neuroscience. A few things pushed the decision. Poor admin was a factor, but more importantly, I realised I hate doing research and I’ve had to face some fears I’ve avoided for a long time. I’ve gone back to the Master of Counselling I started a few years ago.

The neuroscience knowledge is still incredibly valuable and will shape how I practise, but I need something that gives me practical skills to work with people now. I’m not sure a PhD is something I want to pursue, and I don’t want to put all my eggs in one basket.

Now I have to decide where to finish the course. I’m enrolled at a private counselling college that has offered me a partial scholarship. They specialise in counselling, which is a strength, but classes run from 5:30 to 9 pm twice a week, which is when I function least well. The other option is returning to the same university where I started. I’ve already completed two units there, and while there’s no scholarship, the structure might suit me better.

Decision fatigue is real.

#neurodivergent #audhd #academiclife #counselling #careerchange #chronicfatigue #realworldskills #neuroscience #highered #wellbeing #accessibility #actuallyautistic

I have a low-vision student who is learning to code JavaScript. She needs a better code editor to work with, and/or some plugins to make it work better with her screen readers. What do the accessible developers recommend? **#accessibility** **#screenreader #javascript**

I have a low-vision student who is learning to code JavaScript. She needs a better code editor to work with, and/or some plugins to make it work better with her screen readers. What do the accessible developers recommend? **#accessibility** **#screenreader #javascript**

TODAY!

#WearRed. Make a Pledge. Support #Canadians living with #disabilities.

Join #EasterSeals in the movement for #accessibility , #inclusion , and #equity ! Take part in #RedShirtDay on Wednesday, May 28, 2025 by wearing red, making a pledge, and supporting Canadians living with disabilities.

Established by Easter Seals #Canada in 2019, this annual event takes place on the Wednesday of National #AccessAbility Week each year. 

Red Shirt Day® is more than just wearing red; it’s also about making a commitment to remove physical, attitudinal, and #SystemicBarriers to accessibility and inclusion in your school, workplace, or community.

https://redshirtday.org/

#PeopleWithDisabilities #DisabledPeople #Disability #Solidarity #SupportTheDisabled #Inclusiveness #AccessForAll

TODAY!

#WearRed. Make a Pledge. Support #Canadians living with #disabilities.

Join #EasterSeals in the movement for #accessibility , #inclusion , and #equity ! Take part in #RedShirtDay on Wednesday, May 28, 2025 by wearing red, making a pledge, and supporting Canadians living with disabilities.

Established by Easter Seals #Canada in 2019, this annual event takes place on the Wednesday of National #AccessAbility Week each year. 

Red Shirt Day® is more than just wearing red; it’s also about making a commitment to remove physical, attitudinal, and #SystemicBarriers to accessibility and inclusion in your school, workplace, or community.

https://redshirtday.org/

#PeopleWithDisabilities #DisabledPeople #Disability #Solidarity #SupportTheDisabled #Inclusiveness #AccessForAll

#a11y people!

Let’s say I have a navigation on a page that can’t be used with a keyboard at all. Do you open it with a mouse and test how it would work if you could open it?

And if it had a video inside that can’t be started with a keyboard, do you test how the player behaved if you could start it?

How deep do you go with “what if”?

#Accessibility

📣 "Bridging Accessibility Barriers"
with Lukáš Tyrychtr ( @tyrylu ) at #GUADEC2025
📅 24 July 🕒 09:00 CEST 📍 Brescia

🧑‍🦯Making screen readers work on modern GNOME (Wayland + GTK 4) and pushing toward real accessibility.

🔗 https://events.gnome.org/event/259/contributions/1213/

#Linux #GTK4 #Accessibility

📣 "Bridging Accessibility Barriers"
with Lukáš Tyrychtr ( @tyrylu ) at #GUADEC2025
📅 24 July 🕒 09:00 CEST 📍 Brescia

🧑‍🦯Making screen readers work on modern GNOME (Wayland + GTK 4) and pushing toward real accessibility.

🔗 https://events.gnome.org/event/259/contributions/1213/

#Linux #GTK4 #Accessibility

A discussion with one of Apple’s accessibility team, Sara Herrlinger.The interviewer, Ramal, covers tech and relies on low vision accessibility features.

https://youtu.be/7y9gQUR3I_0

#accessibility

GrapheneOS: Where Licenses Matter More Than People

I chose to write this.
Link removed
#GrapheneOS #Accessibility #FOSS #Blind #DisabilityTech #Inclusion #GPLv3 #espeak #a11y #Security #FreeSoftware #DisabilityRights #Android #Rant #TechShame

**update**: If you are using this post as some kind of call-to-action to harass and attack the GOS developers, please don't.

That damages everyone. You, them, and myself. It's not helpful.

**Update two**. I have made the decision to pull this post. It is not a good starting-point for a discussion, and just encourages defensiveness on both sides – when there really aren't sides here at all.

As a FOSS contributor, I am deeply ashamed at the way I approached this out of frustration.

GrapheneOS: Where Licenses Matter More Than People

I chose to write this.
Link removed
#GrapheneOS #Accessibility #FOSS #Blind #DisabilityTech #Inclusion #GPLv3 #espeak #a11y #Security #FreeSoftware #DisabilityRights #Android #Rant #TechShame

**update**: If you are using this post as some kind of call-to-action to harass and attack the GOS developers, please don't.

That damages everyone. You, them, and myself. It's not helpful.

**Update two**. I have made the decision to pull this post. It is not a good starting-point for a discussion, and just encourages defensiveness on both sides – when there really aren't sides here at all.

As a FOSS contributor, I am deeply ashamed at the way I approached this out of frustration.

There Is No Spoon, by @tink (@btconf):

https://www.youtube.com/watch?v=fyRxd072JrA

#videos #ai #accessibility

As we are making good progress on #accessibility for GNOME Calendar lately (big thanks to @TheEvilSkeleton there) I have now rewritten and updated the description of this meta ticket to reflect the current status: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1036

15 of 28 checklist items completed as of May 22nd, 2025, based on what issues I've been able to find so far.

#a11y #GNOMECalendar #GNOME #keyboardnavigation #screenreaders #Linux

As we are making good progress on #accessibility for GNOME Calendar lately (big thanks to @TheEvilSkeleton there) I have now rewritten and updated the description of this meta ticket to reflect the current status: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1036

15 of 28 checklist items completed as of May 22nd, 2025, based on what issues I've been able to find so far.

#a11y #GNOMECalendar #GNOME #keyboardnavigation #screenreaders #Linux

Can anyone recommend a software - preferably #FOSS - that is good at creating #video captions even if you are not a native speaker of English?

I want to create English-language videos for captions for #accessibility reasons, but I fear automated captions will have a difficult time coping with my thick German accent. So ideally I could use something I could train to understand my voice.

EDIT: I should mention that I use Windows at home.

#streaming

Для тех кто генерирует много alt текстов и кого достала тупость поведения Gemini по умолчанию, вот мой промпт-настройка:

When asked to create alt text, do not use the phrases like 'the image shows'. Do not make any guesses, only describe what you see. Do not make descriptions too long. Output English and Russian descriptions at the same time. Wrap descriptions in
```\n
Your description goes here
```
blocks.

#Gemini #Accessibility #AltText

A picture may say a thousand words, but a few well-chosen words of alt-text can make that picture accessible to a broader community.

As well as including people with visual impairments, alt-text can clarify the bit of the image which was important to the person who tooted it, and can explain what the image conveys.

It also makes the content accessible to people in low bandwidth or small data bundle situations, as well as those accessing via a text-mode browser.

#accessibility #alttext

Eurovision - how do you convey those songs, full of attitude, emotions, and sexual innuendo...through sign language?

https://www.dailymail.co.uk/tvshowbiz/article-14724159/Eurovisions-BSL-interpreter-steals-iconic-brilliant-performance-fans-beg-represent-UK-year-didnt-realise-sign-language-graphic.html

https://universeodon.com/@FlohEinstein@chaos.social/114524470081345061

#eurovisión #BSL #SignLanguage #Disability #Accessibility #barrierefreiheit #Linguistics #Deaf #ASL

Eurovision - how do you convey those songs, full of attitude, emotions, and sexual innuendo...through sign language?

https://www.dailymail.co.uk/tvshowbiz/article-14724159/Eurovisions-BSL-interpreter-steals-iconic-brilliant-performance-fans-beg-represent-UK-year-didnt-realise-sign-language-graphic.html

https://universeodon.com/@FlohEinstein@chaos.social/114524470081345061

#eurovisión #BSL #SignLanguage #Disability #Accessibility #barrierefreiheit #Linguistics #Deaf #ASL

Access for All Scheme Funds New Lifts at Greater Manchester Railway Station http://dlvr.it/TKr8yl #AccessforAll #accessibility #Bryn #DaisyHill

The Hidden Gold of Web Accessibility: Everything About ARIA Labels
Code & development

Dive into ARIA labels for web accessibility and enhance your skill set. Unveil their potential, discover best practices, and how to avoid pitfalls.

✏️ https://www.a11y-collective.com/blog/aria-labels/

#webdev #aria #frontend #a11y #web #css #html #label #accessibility #code

A picture may say a thousand words, but a few well-chosen words of alt-text can make that picture accessible to a broader community.

As well as including people with visual impairments, alt-text can clarify the bit of the image which was important to the person who tooted it, and can explain what the image conveys.

It also makes the content accessible to people in low bandwidth or small data bundle situations, as well as those accessing via a text-mode browser.

#accessibility #alttext

A picture may say a thousand words, but a few well-chosen words of alt-text can make that picture accessible to a broader community.

As well as including people with visual impairments, alt-text can clarify the bit of the image which was important to the person who tooted it, and can explain what the image conveys.

It also makes the content accessible to people in low bandwidth or small data bundle situations, as well as those accessing via a text-mode browser.

#accessibility #alttext

I made a similar tool for Mastodon (and a few other platforms), for those interested to give it a try!

https://data.stefanbohacek.com/projects/fediverse-post-accessibility

#AltText #accessibility #ImageDescription

This is pretty neat!

@pixelfed now lets you find all the images you uploaded without an alt text. Nice way to celebrate the recent #GlobalAccessibilityAwarenessDay.

https://mastodon.social/@pixelfed/114513837442236052

#accessibility #AltText

Which #accessibility testing browser extension has the worst #UI?

Accessibility folks, how good/bad for web accessibility is WordPress out of the box, with a default theme, no plugins?

#accessibility #a11y

Accessibility folks, how good/bad for web accessibility is WordPress out of the box, with a default theme, no plugins?

#accessibility #a11y

Apparently 86% of websites have “Low Contrast Text”, making it the most common #accessibility issue (even more than missing alt text). I’m quite surprised by this, as I thought most websites still have white background with black type. Maybe it’s a font size thing in many cases…Anybody have more info on this issue? https://accessibility.day/

For Global Accessibility Awareness Day we are launching a new settings page that lists all of your media without alt text, so you can easily update any missing alt text in a single, easy to remember place.

You can also enable the Require Media Descriptions setting in Settings -> Media.

#accessibility #gaad

For Global Accessibility Awareness Day we are launching a new settings page that lists all of your media without alt text, so you can easily update any missing alt text in a single, easy to remember place.

You can also enable the Require Media Descriptions setting in Settings -> Media.

#accessibility #gaad

For Global Accessibility Awareness Day we are launching a new settings page that lists all of your media without alt text, so you can easily update any missing alt text in a single, easy to remember place.

You can also enable the Require Media Descriptions setting in Settings -> Media.

#accessibility #gaad

@luke thankfully my website has no text contrast issues. I did discover, however, that there is an alert for "Redundant alternative text", which I didn't even know was a thing. Seems a bit odd to recommend no alt text, but I will bear it in mind going forward. #accessibility

Today is Global #accessibility awareness day and I think I speak for a lot of people in the community when I say I'm tired. Particularly over the last few months, the overall climate towards accessibility and #diversity hasn't been super welcoming and while I have a good support network that can remind me that I am, in fact, human and worth existing, many do not. If you receive a request to make something #accessible, from anyone, keep in mind that may very well be the 5th, 10th or even 100th attempt this person has made today at screaming into the void hoping to be seen as a person rather than a potential drain on resources. Rather tna big companies showing off #AI gizmos that mean we've offloaded a problem we didn't want to deal with onto a fallible set of algorithms, maybe #gaad should be about being aware of how ridiculous it is that accessibility professionals and consumers need to fight to even be seen as human these days, because make no mistake, we do.

The internet’s first screen reader was released in 1989. I was 2-year old. It’s been a journey since then! #accessibility #a11y

Did you know? Today is the 14th Global Accessibility Awareness Day 💙
https://accessibility.day/

#gaad
#accessibility

Today is Global #accessibility awareness day and I think I speak for a lot of people in the community when I say I'm tired. Particularly over the last few months, the overall climate towards accessibility and #diversity hasn't been super welcoming and while I have a good support network that can remind me that I am, in fact, human and worth existing, many do not. If you receive a request to make something #accessible, from anyone, keep in mind that may very well be the 5th, 10th or even 100th attempt this person has made today at screaming into the void hoping to be seen as a person rather than a potential drain on resources. Rather tna big companies showing off #AI gizmos that mean we've offloaded a problem we didn't want to deal with onto a fallible set of algorithms, maybe #gaad should be about being aware of how ridiculous it is that accessibility professionals and consumers need to fight to even be seen as human these days, because make no mistake, we do.

Apparently 86% of websites have “Low Contrast Text”, making it the most common #accessibility issue (even more than missing alt text). I’m quite surprised by this, as I thought most websites still have white background with black type. Maybe it’s a font size thing in many cases…Anybody have more info on this issue? https://accessibility.day/

Apparently 86% of websites have “Low Contrast Text”, making it the most common #accessibility issue (even more than missing alt text). I’m quite surprised by this, as I thought most websites still have white background with black type. Maybe it’s a font size thing in many cases…Anybody have more info on this issue? https://accessibility.day/

今天是全球无障碍宣传日。
Today is Global Accessibility Awareness Day

https://accessibility.day

#WebDev #a11y #Accessibility

We're looking for an Associate Accessibility Specialist to join the @TetraLogical team:
https://www.linkedin.com/jobs/view/4229804620

Also here if Linkedin is not your thing:
https://misc.tetralogical.com/careers/2025-05-associate-accessibility-specialist/

Closing date is Wednesday 21 May.

#accessibility #a11y #UK

We're looking for an Associate Accessibility Specialist to join the @TetraLogical team:
https://www.linkedin.com/jobs/view/4229804620

Also here if Linkedin is not your thing:
https://misc.tetralogical.com/careers/2025-05-associate-accessibility-specialist/

Closing date is Wednesday 21 May.

#accessibility #a11y #UK

👉🏽 We are looking for 2 new people to join the @tetralogical.com team as Associate Accessibility Specialists

#a11y #accessibility #jobs

https://www.linkedin.com/jobs/view/4229804620/

👉🏽 We are looking for 2 new people to join the @tetralogical.com team as Associate Accessibility Specialists

#a11y #accessibility #jobs

https://www.linkedin.com/jobs/view/4229804620/

Join me at @devconf_cz this summer in Brno, Czech Republic.

#WebComponents are a widespread and proven technology for developing browser-native UIs. A number of new and upcoming features like import attributes, reference targets, and declarative custom elements make web components even more attractive as a part of your front end stack. In this talk we'll explore some of those new APIs from a web development, #accessibility, and architectural perspective and see how they help your community, #OpenSource project, or organization improve performance and accessibility, reduce development time, avoid costly technical debt, and boost engineering talent. If you are a developer, project manager, or technology recruiter, this talk will inform you about the state of the art in front-end web technologies.

pretalx.devconf.info/devconf-cz-2025/talk/YAETPC/

Join me at @devconf_cz this summer in Brno, Czech Republic.

#WebComponents are a widespread and proven technology for developing browser-native UIs. A number of new and upcoming features like import attributes, reference targets, and declarative custom elements make web components even more attractive as a part of your front end stack. In this talk we'll explore some of those new APIs from a web development, #accessibility, and architectural perspective and see how they help your community, #OpenSource project, or organization improve performance and accessibility, reduce development time, avoid costly technical debt, and boost engineering talent. If you are a developer, project manager, or technology recruiter, this talk will inform you about the state of the art in front-end web technologies.

pretalx.devconf.info/devconf-cz-2025/talk/YAETPC/

Matthias posted an update on the current state of Accessibility in GTK and GNOME on the development blog: https://blog.gtk.org/2025/05/12/an-accessibility-update/

#gtk #gnome #accessibility #a11y

Matthias posted an update on the current state of Accessibility in GTK and GNOME on the development blog: https://blog.gtk.org/2025/05/12/an-accessibility-update/

#gtk #gnome #accessibility #a11y

Woohoo! So far, we have 62 people pledging 269 hours towards improving accessibility in WordPress this Thursday for Global Accessibility Awareness Day! 🙌 Join us in spending a day working on accessibility issues in WordPress core, plugins, or on your own website!

https://equalizedigital.com/gaad2025/ #WordPress #GAAD #GAAD2025 #accessibility #a11y

Woohoo! So far, we have 62 people pledging 269 hours towards improving accessibility in WordPress this Thursday for Global Accessibility Awareness Day! 🙌 Join us in spending a day working on accessibility issues in WordPress core, plugins, or on your own website!

https://equalizedigital.com/gaad2025/ #WordPress #GAAD #GAAD2025 #accessibility #a11y

Here it is. Post 2 in my series on #Linux #accessibility. This time, I'm digitally screaming about the audio stack.
As always, feedback is encouraged and welcomed, and subscribe via rss or email to receive plane-text versions of what I write, the day after publishing at 10 am UTC
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-2-the-audio-stack-is-a-crime-scene/
#a11y #linuxAudio #linuxAccessibility

Posted my first Hireup job.

It's a simple transport to and from the optometrist.

Hireup is a bit like doordash but for support workers.

Let's see how this goes.

#accessibility #disability #GigEconomy

Posted my first Hireup job.

It's a simple transport to and from the optometrist.

Hireup is a bit like doordash but for support workers.

Let's see how this goes.

#accessibility #disability #GigEconomy

I think first step of making websites accessible is to care about accessibility. If you're working with Web, I strongly encourage you to read through these user stories about "How People with Disabilities Use the Web" published on W3C website. I guarantee you your mindset will be different after reading these user stories.

https://www.w3.org/WAI/people-use-web/user-stories/

#webdev #accessibility #a11y

I really liked this tactile exhibit at Mammoth Cave National Park. It shows cave life to scale with a penny, and the models are really well done in 3D. The penny was sized to make the critter model display well, so even the tiny amphipod is tactically interesting even though the penny is mega-oversized (pennies are also in 3D for tactile pleasure).

#cave #life #nature #display #education #science #communication #accessibility

I really liked this tactile exhibit at Mammoth Cave National Park. It shows cave life to scale with a penny, and the models are really well done in 3D. The penny was sized to make the critter model display well, so even the tiny amphipod is tactically interesting even though the penny is mega-oversized (pennies are also in 3D for tactile pleasure).

#cave #life #nature #display #education #science #communication #accessibility

As of today, my computer can __nicely__ read aloud for me !

I'm lazy, i read slowly, so i don't like reading, i skip a lot of articles

I have been looking for a solution for several months

#Accessibility #A11y #Orca #WebBrowser #ZenBrowser #Firefox #Piper #Pied #SpeechAI #AI #Nix #NixOS

Wow.

An excellent post from a blind screen reader user, on how bad accessibility is on Linux (edit: the poster is on Mastodon as well: @fireborn)
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/

It is a fucking shame. And it is pure neglect, as pointed out in the blog post.

Hot take: a new version of open source software should not release before accessibility is fixed. It should be treated as a show stopper, because it actually is for people with a disability.

1/3

#accessibility #a11y #OpenSource #Linux

https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/

»Linux “just works”—if you can see.

If you’re blind?
You boot into a live image and get nothing.
No speech. No braille. No login prompt feedback. Maybe Orca starts, maybe not.
Maybe you know the shortcut (Alt+Super+S?) but does that even work in this session type?
Is it Wayland? Is it X11? Is the screen reader bound to a key combo that doesn’t exist on your keyboard?

You open the installer?

“Next. Button. Button. Button. Button.” That’s all Orca says.

Ubuntu MATE 12.04 had a working, labeled, navigable installer.
Ubuntu MATE 24.04? It’s garbage.

No headings. No structure. No sense of where you are. Just unlabeled buttons and blank space.

This isn’t a bug.
This is neglect.«

Thanks for writing this article, @fireborn

#Accessibility #a11y

https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/

»Linux “just works”—if you can see.

If you’re blind?
You boot into a live image and get nothing.
No speech. No braille. No login prompt feedback. Maybe Orca starts, maybe not.
Maybe you know the shortcut (Alt+Super+S?) but does that even work in this session type?
Is it Wayland? Is it X11? Is the screen reader bound to a key combo that doesn’t exist on your keyboard?

You open the installer?

“Next. Button. Button. Button. Button.” That’s all Orca says.

Ubuntu MATE 12.04 had a working, labeled, navigable installer.
Ubuntu MATE 24.04? It’s garbage.

No headings. No structure. No sense of where you are. Just unlabeled buttons and blank space.

This isn’t a bug.
This is neglect.«

Thanks for writing this article, @fireborn

#Accessibility #a11y

To all #OpenSource and #Linux warriors, to all saying "Ditch windows, install Linux", to everyone and every single person: please, spend several minutes and read this. I want you all to read this so you really understand the problem (if you want to understand, of course). And a huge, huge thanks to Aaron @fireborn for starting this post series. https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/ #Accessibility

To all #OpenSource and #Linux warriors, to all saying "Ditch windows, install Linux", to everyone and every single person: please, spend several minutes and read this. I want you all to read this so you really understand the problem (if you want to understand, of course). And a huge, huge thanks to Aaron @fireborn for starting this post series. https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/ #Accessibility

https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/

»Linux “just works”—if you can see.

If you’re blind?
You boot into a live image and get nothing.
No speech. No braille. No login prompt feedback. Maybe Orca starts, maybe not.
Maybe you know the shortcut (Alt+Super+S?) but does that even work in this session type?
Is it Wayland? Is it X11? Is the screen reader bound to a key combo that doesn’t exist on your keyboard?

You open the installer?

“Next. Button. Button. Button. Button.” That’s all Orca says.

Ubuntu MATE 12.04 had a working, labeled, navigable installer.
Ubuntu MATE 24.04? It’s garbage.

No headings. No structure. No sense of where you are. Just unlabeled buttons and blank space.

This isn’t a bug.
This is neglect.«

Thanks for writing this article, @fireborn

#Accessibility #a11y

https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/

I am quoting the article here with some light editing for clarity and brevity. But please read the whole article, it has some interesting details.

(Begin quote.)

This isn’t a rant from someone who gave Linux a shot and bounced off. This is from someone who’s used Linux full-time for years as a blind user — someone who knows the system inside out, who has made it work through manual configuration, scripting, rebuilding broken packages, and sheer force of will. And still? I’m exhausted. Because Linux doesn’t fail at the margins. It fails at the very first step. Before you open a terminal. Before you write a line of code.

Linux “just works” — if you can see. If you’re blind? You boot into a live image and get nothing. No speech. No braille. No login prompt feedback. Maybe Orca starts, maybe not. Maybe you know the shortcut (Alt+Super+S?) but does that even work in this session type? Is it Wayland? Is it X11? Is the screen reader bound to a key combo that doesn’t exist on your keyboard?

Let’s say Orca does start. Now the audio stack kicks in. Is it PipeWire? PulseAudio? Is ALSA enabled? Is the correct fallback sink selected? Is the audio device owned by root? Is the socket exposed to your session? Want to debug it? You can’t — because you can’t hear anything. So you grab your phone, take a picture of the screen, feed it to an image captioning AI, and hope it tells you whether the error dialog says “Audio device unavailable” or “Session startup failed.” This is normal now.

And the Worst Part? I Can’t Even Recommend It. My partner wants to switch to Linux. She’s frustrated with Windows. She wants something leaner, faster — something she can actually control. She asked me: should I do it? And I didn’t know what to say. Because if I say yes, I’m lying. If I say no, I’m gatekeeping. And if I tell her the truth — that she’ll need to patch PipeWire configs to get audio on a second TTY, that Orca might not speak after login unless she scripts it, that even emoji might get read as “up up up” if Speech Dispatcher pulls the wrong build — I’ll sound insane.

And let me be clear: This post is not an attack on the people who maintain Linux accessibility. I have huge respect for every single person who’s ever written a patch to Orca, BRLTTY, speech-dispatcher, AT-SPI, or any of the dozens of tools that make it possible to use Linux without sight. They are often doing it for free, in their spare time, while fighting upstream changes, toolkit breakage, and general apathy from distros and desktop makers. They are heroes for making it work despite all that.

#tech #software #accessibility #FOSS

https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/

I am quoting the article here with some light editing for clarity and brevity. But please read the whole article, it has some interesting details.

(Begin quote.)

This isn’t a rant from someone who gave Linux a shot and bounced off. This is from someone who’s used Linux full-time for years as a blind user — someone who knows the system inside out, who has made it work through manual configuration, scripting, rebuilding broken packages, and sheer force of will. And still? I’m exhausted. Because Linux doesn’t fail at the margins. It fails at the very first step. Before you open a terminal. Before you write a line of code.

Linux “just works” — if you can see. If you’re blind? You boot into a live image and get nothing. No speech. No braille. No login prompt feedback. Maybe Orca starts, maybe not. Maybe you know the shortcut (Alt+Super+S?) but does that even work in this session type? Is it Wayland? Is it X11? Is the screen reader bound to a key combo that doesn’t exist on your keyboard?

Let’s say Orca does start. Now the audio stack kicks in. Is it PipeWire? PulseAudio? Is ALSA enabled? Is the correct fallback sink selected? Is the audio device owned by root? Is the socket exposed to your session? Want to debug it? You can’t — because you can’t hear anything. So you grab your phone, take a picture of the screen, feed it to an image captioning AI, and hope it tells you whether the error dialog says “Audio device unavailable” or “Session startup failed.” This is normal now.

And the Worst Part? I Can’t Even Recommend It. My partner wants to switch to Linux. She’s frustrated with Windows. She wants something leaner, faster — something she can actually control. She asked me: should I do it? And I didn’t know what to say. Because if I say yes, I’m lying. If I say no, I’m gatekeeping. And if I tell her the truth — that she’ll need to patch PipeWire configs to get audio on a second TTY, that Orca might not speak after login unless she scripts it, that even emoji might get read as “up up up” if Speech Dispatcher pulls the wrong build — I’ll sound insane.

And let me be clear: This post is not an attack on the people who maintain Linux accessibility. I have huge respect for every single person who’s ever written a patch to Orca, BRLTTY, speech-dispatcher, AT-SPI, or any of the dozens of tools that make it possible to use Linux without sight. They are often doing it for free, in their spare time, while fighting upstream changes, toolkit breakage, and general apathy from distros and desktop makers. They are heroes for making it work despite all that.

#tech #software #accessibility #FOSS

To all #OpenSource and #Linux warriors, to all saying "Ditch windows, install Linux", to everyone and every single person: please, spend several minutes and read this. I want you all to read this so you really understand the problem (if you want to understand, of course). And a huge, huge thanks to Aaron @fireborn for starting this post series. https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/ #Accessibility

@servo I can’t find anything on #accessibility in your roadmap and I wouldn’t be able to use “window empty,” so I won’t be investing in this.
Let me know if I missed something though.

The abbreviation #a11y itself is not very accessible. #accessibility

The abbreviation #a11y itself is not very accessible. #accessibility

The abbreviation #a11y itself is not very accessible. #accessibility

The abbreviation #a11y itself is not very accessible. #accessibility

The abbreviation #a11y itself is not very accessible. #accessibility

The abbreviation #a11y itself is not very accessible. #accessibility

The abbreviation #a11y itself is not very accessible. #accessibility

“Do Not Publish Your Designs on the Web with Figma Sites…”
https://adrianroselli.com/2025/05/do-not-publish-your-designs-on-the-web-with-figma-sites.html

Figma announced Figma Sites, letting you publish your Figma designs directly to the web like it’s 1997.

#accessibility #a11y

I see #Figma has decided to reincarnate FrontPage, but worse:
https://www.figma.com/blog/introducing-figma-sites/

Sample 1, with 269 axe issues:
https://www.config.new/

Sample 2, with only 184 axe issues:
https://www.practice-type.com/

No mention of #accessibility in the announcement, so I guess none expected?

Anyway, get ahead of this, folks. We’re going back to 1999!

#a11y

I see #Figma has decided to reincarnate FrontPage, but worse:
https://www.figma.com/blog/introducing-figma-sites/

Sample 1, with 269 axe issues:
https://www.config.new/

Sample 2, with only 184 axe issues:
https://www.practice-type.com/

No mention of #accessibility in the announcement, so I guess none expected?

Anyway, get ahead of this, folks. We’re going back to 1999!

#a11y

It legitimately angers me that Google claim any sort of robust #accessibility support in their half-baked #Flutter UI toolkit. From the need for users to manually enable an accessible mode in web apps, to the use of accessible names to convey role information on mobile, to a borderline unusable keyboard experience on Windows, it is a rotten mess throughout.

Following today's post on the Microsoft Edge blog, I've started a page of ARIA Notify examples that currently only function in Edge Canary:

https://jscholes.github.io/ariaNotify.html

The blog post:

https://blogs.windows.com/msedgedev/2025/05/05/creating-a-more-accessible-web-with-aria-notify/

#accessibility #screenReader #screenReaders

Hey, if you struggle with writing good alt text for your images, you might enjoy following @alttexthalloffame, an account I run, for some inspiration, and occasional tips!

#AltText #accessibility

Following today's post on the Microsoft Edge blog, I've started a page of ARIA Notify examples that currently only function in Edge Canary:

https://jscholes.github.io/ariaNotify.html

The blog post:

https://blogs.windows.com/msedgedev/2025/05/05/creating-a-more-accessible-web-with-aria-notify/

#accessibility #screenReader #screenReaders

When you’re scripting for a screen reader, then you’re scripting for the browser, with exactly the same level of JavaScript support.

However complications can arise with event handling, because screen readers intercept events and don't always pass them on to the browser, and even then, keyboard actions might fire mouse events.

https://www.tpgi.com/event-handling-in-jaws-and-nvda/

#accessibility #a11y #javascript

Hey, if you struggle with writing good alt text for your images, you might enjoy following @alttexthalloffame, an account I run, for some inspiration, and occasional tips!

#AltText #accessibility

@signalapp

a checkbox to turn animations off isn't asking too much if there was time to introduce them with pomp and circumstance?

#accessibility is more important than ... whatever this is (not even novelty).

As part of our volunteer-driven accessibility initiative in GNOME Calendar, and for the first time in the 10+ years of Calendar's existence, we finally completed and merged the first step needed to have a working calendar app for people who rely on keyboard navigation. This merge request in particular makes the event widgets focusable with navigation keys (arrow left/up/right/down) and activatable with space/enter. This will be available in GNOME 49.

Most of GNOME Calendar's layout and widgets consist of custom widgets and complex calculations, both independently and according to other factors (window size, height and width of each cell, number of events, positioning, etc.), so these widgets need to be minimal to have as little overhead as possible. This means that these widgets also need to have the necessary accessibility features reimplemented or even rethought, including and starting with the event widgets.

We also hope to get other parts of GNOME Calendar accessible before GNOME 49, but I can't promise anything at the moment. We did start working with making the month view accessible: https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/564

#GNOME #Calendar #GNOMECalendar #GTK4 #GTK #Libadwaita #Accessibility #a11y #Linux

As part of our volunteer-driven accessibility initiative in GNOME Calendar, and for the first time in the 10+ years of Calendar's existence, we finally completed and merged the first step needed to have a working calendar app for people who rely on keyboard navigation. This merge request in particular makes the event widgets focusable with navigation keys (arrow left/up/right/down) and activatable with space/enter. This will be available in GNOME 49.

Most of GNOME Calendar's layout and widgets consist of custom widgets and complex calculations, both independently and according to other factors (window size, height and width of each cell, number of events, positioning, etc.), so these widgets need to be minimal to have as little overhead as possible. This means that these widgets also need to have the necessary accessibility features reimplemented or even rethought, including and starting with the event widgets.

We also hope to get other parts of GNOME Calendar accessible before GNOME 49, but I can't promise anything at the moment. We did start working with making the month view accessible: https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/564

#GNOME #Calendar #GNOMECalendar #GTK4 #GTK #Libadwaita #Accessibility #a11y #Linux

Firefox 138 Now Available for Download, Here’s What’s New

｢ It’s worth noting also that Mozilla’s accessibility team has rededicated the former color-theme preferences into a unified “Contrast Control” setting. The move simplifies the mental model for users who rely on high-contrast palettes and aligns with WCAG guidance ｣

https://linuxiac.com/firefox-138-now-available-for-download/

#firefox #accessibility #opensource

Firefox 138 Now Available for Download, Here’s What’s New

｢ It’s worth noting also that Mozilla’s accessibility team has rededicated the former color-theme preferences into a unified “Contrast Control” setting. The move simplifies the mental model for users who rely on high-contrast palettes and aligns with WCAG guidance ｣

https://linuxiac.com/firefox-138-now-available-for-download/

#firefox #accessibility #opensource

The 2025 edition of Inclusive Design 24 (#id24) will take place on the 25 September 2025.

Got an idea for a talk? Our call for presentations is still open until the end of the month (31 May 2025).

https://inclusivedesign24.org/2025/

#a11y #accessibility #inclusion #inclusiveDesign

The 2025 edition of Inclusive Design 24 (#id24) will take place on the 25 September 2025.

Got an idea for a talk? Our call for presentations is still open until the end of the month (31 May 2025).

https://inclusivedesign24.org/2025/

#a11y #accessibility #inclusion #inclusiveDesign

I had an interesting question on colour filter overlays from a librarian today.

A dyslexic student wants to read some original documents, not scans or reproductions, and they'd like to put some colour filter overlays on them.

The librarians are concerned that the documents might get damaged. They want to know if a hand-held colour filter, or something on the light source, would work just as well.

I don't know much about the science of colour filters for dyslexia except I've heard the data on efficacy is mixed, but assuming we want this to happen: is there any strong reason to have the colour filter directly on the document?

I don't know any hashtags that archives people would be watching, so please recommend one if you know one!

#accessibility #dyslexia

When you’re scripting for a screen reader, then you’re scripting for the browser, with exactly the same level of JavaScript support.

However complications can arise with event handling, because screen readers intercept events and don't always pass them on to the browser, and even then, keyboard actions might fire mouse events.

https://www.tpgi.com/event-handling-in-jaws-and-nvda/

#accessibility #a11y #javascript

I had an interesting question on colour filter overlays from a librarian today.

A dyslexic student wants to read some original documents, not scans or reproductions, and they'd like to put some colour filter overlays on them.

The librarians are concerned that the documents might get damaged. They want to know if a hand-held colour filter, or something on the light source, would work just as well.

I don't know much about the science of colour filters for dyslexia except I've heard the data on efficacy is mixed, but assuming we want this to happen: is there any strong reason to have the colour filter directly on the document?

I don't know any hashtags that archives people would be watching, so please recommend one if you know one!

#accessibility #dyslexia

The post-download open button in Chrome now receives a checked state when pressed, even though it's just a regular push-button and not a checkbox.

And like, this has zero screen reader impact beyond hearing the word "checked", but how does this even happen? How does someone look at a simple, single-purpose button and go, "You know what this needs? A temporary checked state when it's activated!"

Was this written by a human at all? If so, what was the thought process?

#accessibility

Looking to make an assistive device.

Want it to have on the control panel:

A. a combined on/off start/stop toggle switch.

B. A green LED to show it is switched on or not.

C. A volume knob.

It is to play a single audio file on Loop.

I have the case and speaker. (See below.)

Anyone know how others have got similar things working?

Advice welcomed.

Know of off-the-shelf units that have that very simple control setup?
#Accessibility

Well isn't this just going to be a day. Firstly the submit order at #Walgreens.com is broken with NVDA and Jaws For Windows in Google Chrome. It won't activate for love nor money. And then I just encountered the switch to the new #Outlook because we really, really, really, really want you to do it now! message. Anyone know how to make that not bother us any more? #Accessibility Welcome to Saturday friends.

The final talk from #SotB2025
Oliver Schöndorfer - Typographer vs. Accessibility
Is now available for your viewing pleasure.
https://2025.stateofthebrowser.com/speaker/oliver-schondorfer/
#Fonts #Typography #a11y #Accessibility

The final talk from #SotB2025
Oliver Schöndorfer - Typographer vs. Accessibility
Is now available for your viewing pleasure.
https://2025.stateofthebrowser.com/speaker/oliver-schondorfer/
#Fonts #Typography #a11y #Accessibility

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

#fedidev

🚶‍♂️ Work in progress!

I’m exploring modular illustrations as visual aids to support #OpenStreetMap contributors and documentation. The modules can be mixed and matched to visualize diverse scenarios for sidewalks, curbs, and crossings.

Early test below. Feedback welcome!

#OSM #Accessibility #Mapping #Design #Artwork #Illustration

🚶‍♂️ Work in progress!

I’m exploring modular illustrations as visual aids to support #OpenStreetMap contributors and documentation. The modules can be mixed and matched to visualize diverse scenarios for sidewalks, curbs, and crossings.

Early test below. Feedback welcome!

#OSM #Accessibility #Mapping #Design #Artwork #Illustration

Thank you @fmarini for the original photo and inspiration! #accessibility

I like this! #accessibility

I'm searching for groups that advocate for the mobility challenged – for neighborhood infrastructure improvements.

A friend and I have been discussing neighborhood sidewalks and the challenges some face in places in our city.

Are there organizations that advocate for the mobility challenged so that they can receive neighborhood improvements? Maybe they can give us advice as to legal precedents, tell us about positive trends of municipal action that led to improving things in older neighborhoods that tend to have poorer sidewalks?

Our neighborhood group can engage with City Hall and elected officials better if we have more knowledge and advice.

Are there organizations that offer matching grants for municipalities if they make infrastructure improvements? Are there organizations that conduct surveys and studies to identify recommended actions?

Thanks in advance, and greetings from southern New Mexico.

Tom

#Disability
#DisabilityRights
#Accessibility
#Ableism
#DisabilityJustice

I'm searching for groups that advocate for the mobility challenged – for neighborhood infrastructure improvements.

A friend and I have been discussing neighborhood sidewalks and the challenges some face in places in our city.

Are there organizations that advocate for the mobility challenged so that they can receive neighborhood improvements? Maybe they can give us advice as to legal precedents, tell us about positive trends of municipal action that led to improving things in older neighborhoods that tend to have poorer sidewalks?

Our neighborhood group can engage with City Hall and elected officials better if we have more knowledge and advice.

Are there organizations that offer matching grants for municipalities if they make infrastructure improvements? Are there organizations that conduct surveys and studies to identify recommended actions?

Thanks in advance, and greetings from southern New Mexico.

Tom

#Disability
#DisabilityRights
#Accessibility
#Ableism
#DisabilityJustice

Reposting this amazing guide on how to write helpful alt text from https://www.perkins.org/resource/how-write-alt-text-and-image-descriptions-visually-impaired/, originally posted by @karengregory (including her original image description) so that I can pin it.

#AltText #ImageDescription #accessibility #a11y

In terms of #email #accessibility is it still necessary to add role=presentation to every table, tr and td element, as adding it to the table element alone is not enough, especially for #ScreenReaders and old email clients? 🤔

Ubisoft open sourced Chroma, their colourblind simulation tool https://www.gamingonlinux.com/2025/04/ubisoft-open-sourced-chroma-their-colourblind-simulation-tool/

#Ubisoft #OpenSource #Accessibility #Gaming #GameDev

Ubisoft open sourced Chroma, their colourblind simulation tool https://www.gamingonlinux.com/2025/04/ubisoft-open-sourced-chroma-their-colourblind-simulation-tool/

#Ubisoft #OpenSource #Accessibility #Gaming #GameDev

Ubisoft open sourced Chroma, their colourblind simulation tool https://www.gamingonlinux.com/2025/04/ubisoft-open-sourced-chroma-their-colourblind-simulation-tool/

#Ubisoft #OpenSource #Accessibility #Gaming #GameDev

In terms of #email #accessibility is it still necessary to add role=presentation to every table, tr and td element, as adding it to the table element alone is not enough, especially for #ScreenReaders and old email clients? 🤔

Anyone who is blind, or who has worked with the blind, knows how expensive our technology can be. This couldn't be more true with relation to braille displays. Even the cheapest costs at least $799, and it's already behind the newest in that line, at $899. This is the Orbit Reader 20 and 20+. Now, a student in India wants to change that by creating a display that is truly affordable (under $50)! Please pass this on, so that we can give him greater recognition within the blind community. Even if it costs a bit more than he initially suspected it would, there is no excuse for the $2,000 to $5,000 average price of such technology when cheaper alternatives can be designed! He is determined to bring this to market, so let's help him do it and show our appreciation for his hard work on this life-changing project!

forbes.com/sites/kevinanderton…

#access #ACB #accessibility #affordability #blind #braille #BrailleDisplays #children #education #employment #independence #India #learning #NFB #ocr #parent #reading #science #school #students #teachers #technology #work #writing

Wondering what is the best way to style visited links? Using color alone clearly is not enough.

#html #accessibility

Anyone who is blind, or who has worked with the blind, knows how expensive our technology can be. This couldn't be more true with relation to braille displays. Even the cheapest costs at least $799, and it's already behind the newest in that line, at $899. This is the Orbit Reader 20 and 20+. Now, a student in India wants to change that by creating a display that is truly affordable (under $50)! Please pass this on, so that we can give him greater recognition within the blind community. Even if it costs a bit more than he initially suspected it would, there is no excuse for the $2,000 to $5,000 average price of such technology when cheaper alternatives can be designed! He is determined to bring this to market, so let's help him do it and show our appreciation for his hard work on this life-changing project!

forbes.com/sites/kevinanderton…

#access #ACB #accessibility #affordability #blind #braille #BrailleDisplays #children #education #employment #independence #India #learning #NFB #ocr #parent #reading #science #school #students #teachers #technology #work #writing

Anyone who is blind, or who has worked with the blind, knows how expensive our technology can be. This couldn't be more true with relation to braille displays. Even the cheapest costs at least $799, and it's already behind the newest in that line, at $899. This is the Orbit Reader 20 and 20+. Now, a student in India wants to change that by creating a display that is truly affordable (under $50)! Please pass this on, so that we can give him greater recognition within the blind community. Even if it costs a bit more than he initially suspected it would, there is no excuse for the $2,000 to $5,000 average price of such technology when cheaper alternatives can be designed! He is determined to bring this to market, so let's help him do it and show our appreciation for his hard work on this life-changing project!

forbes.com/sites/kevinanderton…

#access #ACB #accessibility #affordability #blind #braille #BrailleDisplays #children #education #employment #independence #India #learning #NFB #ocr #parent #reading #science #school #students #teachers #technology #work #writing

The following CSS seems to work on the Mastodon desktop website to hide posts with images without alt text:

#mastodon div.status:has(img:not([alt])),
#mastodon div.detailed-status:has(img:not([alt])) {
display:none !important;
}

It's a bit tedious to set up if you haven't done it before though. There are plenty of articles on the web on setting up a browser personal stylesheet so I won't go through the details since they vary by browser and operating system.

#accessibility

Been thinking about folks' desire to not show posts with images missing alt text. I think it's doable using CSS if you're using a browser such as Firefox that lets you have a personal style sheet (with some configuration finagling). But if the post is urgent, as with a public safety agency, you would miss the post. (Of course, if the urgent post was only an image, you would miss it anyway, if you are personally dependent on alt text.)

¿Thoughts?

#accessibility

So #Amazon have outdone themselves again, my 2021 #Kindle Paperwhite SE is unusable with #Voiceview because the TTS is garbled compressed electronic sounding crap apparently due to the 5.18.1 update that I did not even know it was receiving. I have reported it but doubt they'll do shit about it. #Accessibility #Blind #ScreenReader

Mały kalendarzyk naukowy #PJM

-----
📆 24 maja 2025 r.
#Warszawa, #UniwersytetWarszawski
🚏 MŁODA LINGWISTYKA MIGOWA II. Ogólnopolska konferencja naukowa
📍 Aula 0.410, Wydział Lingwistyki Stosowanej Uniwersytetu Warszawskiego (ul. Dobra 55)
🔗 https://www.facebook.com/events/543671152078422/?acontext=%7B%22event_action_history%22%3A%5B%7B%22mechanism%22%3A%22attachment%22%2C%22surface%22%3A%22newsfeed%22%7D%5D%2C%22ref_notif_type%22%3Anull%7D

📆 24 maja 2025 r.
#Kraków, #UniwersytetJagielloński
🚏 Panel dyskusyjny o dostępności badań naukowych dla osób g/Głuchych
📍 Katedra Anatomii UJ CM, sala wykładowa im prof. L. Teichmanna, ul. Kopernika 12, 31-034 Kraków
🔗 https://bioetyka.wnz.cm.uj.edu.pl/pl/2696-2/

📆 18–19 września 2025 r.
#Warszawa, #UniwersytetWarszawski
🚏 Sign CAFÉ 3 (Workshop on Cognitive and Functional Explorations in Sign Language Linguistics – Warsztaty Badań Kognitywnych i Funkcjonalnych nad Lingwistyką Migową)
📍 Uniwersytet Warszawski, Kampus Główny, Budynek dawnej Biblioteki Uniwersyteckiej, ul. Krakowskie Przedmieście, 26/28, 00-927 Warszawa
🔗 http://sign.uw.edu.pl/en/sign-cafe-3/
-----

#disability #accessibility #Głusi #polskijezykmigowy

Good day everyone! Join me tomorrow, Thursday April 10th at 1200 Eastern / UTC -4 with my #special #guest @WeirdWriter, Robert Kingett.

Robert is a #writer that has done #fiction, #nonfiction, and #technical writing. He is an #accessibility #specialist. He's helped bring #disability access improvements to the #Fediverse and worked with #Bookwyrm.

Catch the #Owncast powered #livestream: https://stream.firesidefedi.live
#Peertube #VOD afterwards: https://video.firesidefedi.live
#Castopod #Fedicast #Podcast: https://audio.firesidefedi.live

Hey #a11y folks, suppose I have a form with a button that opens a mini-form in a popover or dialog. Does it make sense to stick things like `aria-required` or `aria-invalid` on that button if things in the mini-form are required / invalid?

On one hand, this feels semantically wrong? The button itself is just a trigger and can't really be "invalid" in anyway. On the other, since the actual invalid elements are in the popover or dialog, there's no other indication of this state (apart from manual descriptions).

#aria #web #weba11y #accessibility

Hey #a11y folks, suppose I have a form with a button that opens a mini-form in a popover or dialog. Does it make sense to stick things like `aria-required` or `aria-invalid` on that button if things in the mini-form are required / invalid?

On one hand, this feels semantically wrong? The button itself is just a trigger and can't really be "invalid" in anyway. On the other, since the actual invalid elements are in the popover or dialog, there's no other indication of this state (apart from manual descriptions).

#aria #web #weba11y #accessibility

Good day everyone! Join me tomorrow, Thursday April 10th at 1200 Eastern / UTC -4 with my #special #guest @WeirdWriter, Robert Kingett.

Robert is a #writer that has done #fiction, #nonfiction, and #technical writing. He is an #accessibility #specialist. He's helped bring #disability access improvements to the #Fediverse and worked with #Bookwyrm.

Catch the #Owncast powered #livestream: https://stream.firesidefedi.live
#Peertube #VOD afterwards: https://video.firesidefedi.live
#Castopod #Fedicast #Podcast: https://audio.firesidefedi.live

Targeting an `<iframe>` element is an interesting technique for progressive enhancement (e.g. showing search results in the iframe that updates when the user submits a filter form), however, the lack of feedback for screen readers when the frame navigates makes me think it should be avoided. #ProgressiveEnhancement #accessibility #a11y

Naive accessibility question: How does your screen reader render emojis? Are they accessible?

Are mastodon extended emojis like rendered differently from unicode emojis like 😀?

#accessibility #a11y #ScreenReaders

I figured I should make this into a poster. A4 size, but can easily be scaled to fit onto Letter size, for you non-standard Americans out there.

Reuse encouraged, public domain!

#AltText #Accessibility

Question for you #webdev peeps:

I've made a site and it's totally in dark mode. How I like it 😊

But some people mentioned that I should offer a light mode toggle because "some people are not used to dark mode and won't like it".

Do you think that's valid?

(Someone else said that there's also potentially an accessibility issue with dark mode - is that true?)

#websitedesign #html #accessibility #darkmode #lightmode #webdesign #mastodev

Right. Enough suspense.

This merge request makes it official. https://invent.kde.org/websites/ev-kde-org/-/merge_requests/145

I've joined up with @kde as an Accessibility Engineer.

You know *exactly* what that means, and yes - the coffee and C++ muscle memory is ready.

Hello, #KDE community :)

#accessibility

Nintendo is going to show off mouse controls on Switch 2 with a game about wheelchair sport! 👏 The two mouse controllers operate each wheel independently.

Cc @nintendo

#Accessibility #Wheelchairs #Nintendo #Switch2

Right. Enough suspense.

This merge request makes it official. https://invent.kde.org/websites/ev-kde-org/-/merge_requests/145

I've joined up with @kde as an Accessibility Engineer.

You know *exactly* what that means, and yes - the coffee and C++ muscle memory is ready.

Hello, #KDE community :)

#accessibility

Kudos to @dankeck for the first non-me contribution to @badgefed ! That deserves a badge, as soon as I deploy the #alttext #accessibility changes that Dan contributed I will issue a new one.

https://github.com/tryvocalcat/badgefed/pull/1

Kudos!

#activitypub

Is alt text useful? Should you describe colors in images? Find answers to these questions, and more, with these polls and insights.

https://stefanbohacek.com/blog/polls-about-alt-text-on-social-media/

#AltText #accessibility #ImageDescription

Is alt text useful? Should you describe colors in images? Find answers to these questions, and more, with these polls and insights.

https://stefanbohacek.com/blog/polls-about-alt-text-on-social-media/

#AltText #accessibility #ImageDescription

Anyone know of a good #accessible e-book-reader for IOS and IPadOS, which can load books and documents other than apple-books?
I'd like to use my braille-display in combination with my IPad for reading books and documents in braille.
#accessibility #blind #braille

Anyone know of a good #accessible e-book-reader for IOS and IPadOS, which can load books and documents other than apple-books?
I'd like to use my braille-display in combination with my IPad for reading books and documents in braille.
#accessibility #blind #braille

🎉 Off to State of the Browser #SOTB tomorrow the #WebStandards conference organized by @dletorey and @webstandards team. Excited to learn from @sarajw and @matuzo amongst others.

#accessibility #HTML #CSS

If you are attending come say 👋

@MastodonEngineering Thank you for emphasizing #accessibility.

If you need any pointers for people with Parkinson's or age-related or medication related dyskinesia, which is very common, feel free to reach out to the #a11y community. I have a few suggestions.😉

Was laid off a month ago from my #accessibility lead position. I've only gotten one callback in that month so far. Trying #getfedihired (#fedihire ?) - been working fulltime in accessibility since 2016, experienced with cross-team collaborations, & had input on design systems and component libraries in addition. #UX is also something I'm familiar with, as that's the closest field aside from accessibility. I'm US based, speak EN but learning JP & beginning FR. Remote/ teletravail please!

Was laid off a month ago from my #accessibility lead position. I've only gotten one callback in that month so far. Trying #getfedihired (#fedihire ?) - been working fulltime in accessibility since 2016, experienced with cross-team collaborations, & had input on design systems and component libraries in addition. #UX is also something I'm familiar with, as that's the closest field aside from accessibility. I'm US based, speak EN but learning JP & beginning FR. Remote/ teletravail please!

Was laid off a month ago from my #accessibility lead position. I've only gotten one callback in that month so far. Trying #getfedihired (#fedihire ?) - been working fulltime in accessibility since 2016, experienced with cross-team collaborations, & had input on design systems and component libraries in addition. #UX is also something I'm familiar with, as that's the closest field aside from accessibility. I'm US based, speak EN but learning JP & beginning FR. Remote/ teletravail please!

Was laid off a month ago from my #accessibility lead position. I've only gotten one callback in that month so far. Trying #getfedihired (#fedihire ?) - been working fulltime in accessibility since 2016, experienced with cross-team collaborations, & had input on design systems and component libraries in addition. #UX is also something I'm familiar with, as that's the closest field aside from accessibility. I'm US based, speak EN but learning JP & beginning FR. Remote/ teletravail please!

Was laid off a month ago from my #accessibility lead position. I've only gotten one callback in that month so far. Trying #getfedihired (#fedihire ?) - been working fulltime in accessibility since 2016, experienced with cross-team collaborations, & had input on design systems and component libraries in addition. #UX is also something I'm familiar with, as that's the closest field aside from accessibility. I'm US based, speak EN but learning JP & beginning FR. Remote/ teletravail please!

Probably TMI but here's a draft flowchart of what goes through my brain when I'm considering whether to boost an image. Not included but of course important: (1) Is image made by a human? (2) Is there something in the body of the text that's mildly interesting? (3) Is account an actual person active on the platform? (4) Are number of hashtags in Goldilocks zone? #boosts #AltText #copyright #photography #accessibility #boosting #CreativeCommons

Probably TMI but here's a draft flowchart of what goes through my brain when I'm considering whether to boost an image. Not included but of course important: (1) Is image made by a human? (2) Is there something in the body of the text that's mildly interesting? (3) Is account an actual person active on the platform? (4) Are number of hashtags in Goldilocks zone? #boosts #AltText #copyright #photography #accessibility #boosting #CreativeCommons

Ever wanted to style HTML form controls with custom CSS? A new @w3c #CSS specification is underway: "CSS Form Control Styling Level 1" #FPWD #timetogiveinput
▶️ https://www.w3.org/TR/css-forms-1/

This spec. aims to standardize form styling, improving design consistency and #accessibility while giving web #designers more control.
Feedback welcome! https://github.com/w3c/csswg-drafts/labels/css-forms-1

Need a demo? Check this one by @argyleink! https://nerdy.dev/customize-a-select

WCAG (Web Content Accessibility Guidelines) Techniques: show a warning on links that are opening in a new window or tab.

#accessibility #a11y #webdev

https://www.w3.org/WAI/WCAG21/Techniques/general/G201

Affinity Publisher 2.6 added a reading order panel:
https://affinity.serif.com/en-us/whats-new/#2-6-reading-order-panel

Makes the PDF output easier to control. No, I have not tested it yet.

You know, for those of you who still are looking to ditch Adobe.

#a11y #accessibility

»The anatomy of visually-hidden«
by James Edwards

This article really is the absolutely best explanation of the declarations used in the visually-hidden hack.

Found the link in the phantastic »Web Accessiblity Cookbook« written by @matuzo.

Thanx a million to both for writing and publishing this.

#Web #HTML #CSS #Accessibility #A11Y

https://www.tpgi.com/the-anatomy-of-visually-hidden/

Nice tips document on how to write accessible app UIs, or debug accessibility when it doesn’t seem to be working quite right: https://gitlab.gnome.org/GNOME/orca/-/blob/main/README-APPLICATION-DEVELOPERS.md

#GNOME #accessibility

#Blind users, users that rely heavily on #keyboardNavigation or anyone else with a preference on that matter (please indicate what applies in the comments):

Do you have a preference for or comments on the format of URLs? During user research, we have learned that URLs that are easy to handle are a good thing.

We are currently considering to introduce URLs that do not need more reserved usernames in #Forgejo, such as https://codeberg.org/-/something/ or https://codeberg.org/_something/.

#a11y #accessibility

We're hiring for a new PHP Developer to join the team at Studio 24. We're passionate about building a web that works for everyone. We design and build accessible websites and complex web applications and focus on projects with impact for public sector & non-profit clients.

If you'd like to work with a friendly and supportive team on projects for clients such as @w3c, RNIB, UK Parliament, CBM and other fantastic clients please see https://www.studio24.net/careers/php-developer/ #jobs #PHP #accessibility

We're hiring for a new PHP Developer to join the team at Studio 24. We're passionate about building a web that works for everyone. We design and build accessible websites and complex web applications and focus on projects with impact for public sector & non-profit clients.

If you'd like to work with a friendly and supportive team on projects for clients such as @w3c, RNIB, UK Parliament, CBM and other fantastic clients please see https://www.studio24.net/careers/php-developer/ #jobs #PHP #accessibility

We're hiring for a new PHP Developer to join the team at Studio 24. We're passionate about building a web that works for everyone. We design and build accessible websites and complex web applications and focus on projects with impact for public sector & non-profit clients.

If you'd like to work with a friendly and supportive team on projects for clients such as @w3c, RNIB, UK Parliament, CBM and other fantastic clients please see https://www.studio24.net/careers/php-developer/ #jobs #PHP #accessibility

I guess that "bare minimum" alt-text is better than no alt-text.

But giving people who can't view images high quality alt-text - a chance to enjoy an image properly - is (to me) just part of treating people kindly.

It takes but a few seconds to type an extra sentence or two.

Bad alt text: "Cat"

Good alt text: "A tabby cat sitting on a windowsill, looking out the window with its tail curled around its body."

https://www.rnib.org.uk/campaign-with-us/alt-text-campaign/how-can-i-write-alt-text/

#accessibility #kindness #alttext

I guess that "bare minimum" alt-text is better than no alt-text.

But giving people who can't view images high quality alt-text - a chance to enjoy an image properly - is (to me) just part of treating people kindly.

It takes but a few seconds to type an extra sentence or two.

Bad alt text: "Cat"

Good alt text: "A tabby cat sitting on a windowsill, looking out the window with its tail curled around its body."

https://www.rnib.org.uk/campaign-with-us/alt-text-campaign/how-can-i-write-alt-text/

#accessibility #kindness #alttext

I was thinking of starting a collection of #accessible patterns for the web. Such resources exist already. A million of them. All saying different things.

I think I need a collection of answers to common questions and patterns for common problems that is written in easier language and closer to the real world and patterns you could copy.

Before I start my own list of things, I’d love to know which of the existing ones are worth contributing? #a11y #Accessibility

Mark your calendars: the 2025 edition of Inclusive Design 24 (#id24) will take place on the 25 September 2025! We've just opened our call for presentations (closing date 31 May 2025) - looking forward to your exciting submissions! https://inclusivedesign24.org/2025/ #a11y #accessibility #inclusion #inclusiveDesign

Affinity Publisher 2.6 added a reading order panel:
https://affinity.serif.com/en-us/whats-new/#2-6-reading-order-panel

Makes the PDF output easier to control. No, I have not tested it yet.

You know, for those of you who still are looking to ditch Adobe.

#a11y #accessibility

I was thinking of starting a collection of #accessible patterns for the web. Such resources exist already. A million of them. All saying different things.

I think I need a collection of answers to common questions and patterns for common problems that is written in easier language and closer to the real world and patterns you could copy.

Before I start my own list of things, I’d love to know which of the existing ones are worth contributing? #a11y #Accessibility

Mark your calendars: the 2025 edition of Inclusive Design 24 (#id24) will take place on the 25 September 2025! We've just opened our call for presentations (closing date 31 May 2025) - looking forward to your exciting submissions! https://inclusivedesign24.org/2025/ #a11y #accessibility #inclusion #inclusiveDesign

That's the dadgum truth, right there.

#disabled #disability #disabilityawareness #spoonie #accessibility #mentalhealth

Since this got so much attention, I'd like to use this moment of sunshine to invite you all to read with us next week:

https://inkican.com/gsbcw

That's the dadgum truth, right there.

#disabled #disability #disabilityawareness #spoonie #accessibility #mentalhealth

Since this got so much attention, I'd like to use this moment of sunshine to invite you all to read with us next week:

https://inkican.com/gsbcw

📣 Announcing Altbot 2.0: The Privacy & Green Update 🔒💚

Exciting news! After months of development, Altbot 2.0 is officially launching with major improvements to privacy, efficiency, and description quality.

What's new in Altbot 2.0:

• 100% local AI processing for true privacy - unlike Google Gemini which saves data for training, Altbot 2.0 retains ZERO information about you or your images using the powerful Ovis2:8B model running on my custom AltTron server equipped with an A5500 GPU and expansion capacity for two additional GPUs
• Full GDPR compliance with clear informed consent - I've implemented comprehensive privacy measures including transparent data handling policies, user rights protection, and minimal data collection practices that exceed GDPR requirements
• Better quality descriptions across all 11 supported languages thanks to a newly developed translation layer specifically optimized for local LLM models
• Significantly more energy efficient with a new feature that shows you exactly how much energy was used for each request! This efficiency comes from using a server-grade GPU optimized for lower power consumption, and 36% of the energy consumed is from clean sources mainly nuclear power (thanks to being based in Georgia)

The only data Altbot 2.0 records:

• That a request happened
• How long it took to complete
• What type of media it was (image, video, or audio)
• What language was used

No images, no content, no personal data saved - ever.

For those who don't know, Altbot has been helping make the Fediverse more accessible by automatically generating alt-text descriptions for images. The project has grown beyond anything I imagined, now serving thousands of users across the network.

Support Altbot's Future 💝

To bring these privacy and efficiency improvements to life, I had to invest in a more powerful server than initially planned. The server costs exceeded my budget by around $900, which I've covered out of pocket. Who woulda thought that competing with a $1.98 trillion dystopian mega corporation would be expensive? Shocking, I know.

I've set up a Ko-fi fundraising goal to help recover these costs and support ongoing development: Ko-fi.com/micr0byte

Your contributions will help ensure Altbot remains:

• Free for everyone
• Continuously improved
• Sustainably maintained

Even small donations make a huge difference and motivate me to keep enhancing accessibility across the Fediverse!

This milestone represents a commitment to ensuring accessibility doesn't come at the cost of privacy or environmental impact. I'm incredibly proud of what we've built together.

As Altbot continues to grow, I'm open to sharing more about this journey with anyone interested in accessibility, ethical AI, or Fediverse projects.

For press inquiries: inquiries@micr0.dev

Feel free to boost or reach out!

#Accessibility #Fediverse #AltText #EthicalAI #OpenSource #Privacy #Altbot

📣 Announcing Altbot 2.0: The Privacy & Green Update 🔒💚

Exciting news! After months of development, Altbot 2.0 is officially launching with major improvements to privacy, efficiency, and description quality.

What's new in Altbot 2.0:

• 100% local AI processing for true privacy - unlike Google Gemini which saves data for training, Altbot 2.0 retains ZERO information about you or your images using the powerful Ovis2:8B model running on my custom AltTron server equipped with an A5500 GPU and expansion capacity for two additional GPUs
• Full GDPR compliance with clear informed consent - I've implemented comprehensive privacy measures including transparent data handling policies, user rights protection, and minimal data collection practices that exceed GDPR requirements
• Better quality descriptions across all 11 supported languages thanks to a newly developed translation layer specifically optimized for local LLM models
• Significantly more energy efficient with a new feature that shows you exactly how much energy was used for each request! This efficiency comes from using a server-grade GPU optimized for lower power consumption, and 36% of the energy consumed is from clean sources mainly nuclear power (thanks to being based in Georgia)

The only data Altbot 2.0 records:

• That a request happened
• How long it took to complete
• What type of media it was (image, video, or audio)
• What language was used

No images, no content, no personal data saved - ever.

For those who don't know, Altbot has been helping make the Fediverse more accessible by automatically generating alt-text descriptions for images. The project has grown beyond anything I imagined, now serving thousands of users across the network.

Support Altbot's Future 💝

To bring these privacy and efficiency improvements to life, I had to invest in a more powerful server than initially planned. The server costs exceeded my budget by around $900, which I've covered out of pocket. Who woulda thought that competing with a $1.98 trillion dystopian mega corporation would be expensive? Shocking, I know.

I've set up a Ko-fi fundraising goal to help recover these costs and support ongoing development: Ko-fi.com/micr0byte

Your contributions will help ensure Altbot remains:

• Free for everyone
• Continuously improved
• Sustainably maintained

Even small donations make a huge difference and motivate me to keep enhancing accessibility across the Fediverse!

This milestone represents a commitment to ensuring accessibility doesn't come at the cost of privacy or environmental impact. I'm incredibly proud of what we've built together.

As Altbot continues to grow, I'm open to sharing more about this journey with anyone interested in accessibility, ethical AI, or Fediverse projects.

For press inquiries: inquiries@micr0.dev

Feel free to boost or reach out!

#Accessibility #Fediverse #AltText #EthicalAI #OpenSource #Privacy #Altbot

📣 Announcing Altbot 2.0: The Privacy & Green Update 🔒💚

Exciting news! After months of development, Altbot 2.0 is officially launching with major improvements to privacy, efficiency, and description quality.

What's new in Altbot 2.0:

• 100% local AI processing for true privacy - unlike Google Gemini which saves data for training, Altbot 2.0 retains ZERO information about you or your images using the powerful Ovis2:8B model running on my custom AltTron server equipped with an A5500 GPU and expansion capacity for two additional GPUs
• Full GDPR compliance with clear informed consent - I've implemented comprehensive privacy measures including transparent data handling policies, user rights protection, and minimal data collection practices that exceed GDPR requirements
• Better quality descriptions across all 11 supported languages thanks to a newly developed translation layer specifically optimized for local LLM models
• Significantly more energy efficient with a new feature that shows you exactly how much energy was used for each request! This efficiency comes from using a server-grade GPU optimized for lower power consumption, and 36% of the energy consumed is from clean sources mainly nuclear power (thanks to being based in Georgia)

The only data Altbot 2.0 records:

• That a request happened
• How long it took to complete
• What type of media it was (image, video, or audio)
• What language was used

No images, no content, no personal data saved - ever.

For those who don't know, Altbot has been helping make the Fediverse more accessible by automatically generating alt-text descriptions for images. The project has grown beyond anything I imagined, now serving thousands of users across the network.

Support Altbot's Future 💝

To bring these privacy and efficiency improvements to life, I had to invest in a more powerful server than initially planned. The server costs exceeded my budget by around $900, which I've covered out of pocket. Who woulda thought that competing with a $1.98 trillion dystopian mega corporation would be expensive? Shocking, I know.

I've set up a Ko-fi fundraising goal to help recover these costs and support ongoing development: Ko-fi.com/micr0byte

Your contributions will help ensure Altbot remains:

• Free for everyone
• Continuously improved
• Sustainably maintained

Even small donations make a huge difference and motivate me to keep enhancing accessibility across the Fediverse!

This milestone represents a commitment to ensuring accessibility doesn't come at the cost of privacy or environmental impact. I'm incredibly proud of what we've built together.

As Altbot continues to grow, I'm open to sharing more about this journey with anyone interested in accessibility, ethical AI, or Fediverse projects.

For press inquiries: inquiries@micr0.dev

Feel free to boost or reach out!

#Accessibility #Fediverse #AltText #EthicalAI #OpenSource #Privacy #Altbot

Saying "No-one using our service has accessibility needs" is a bit like saying "We don't need a ramp, no-one in a wheelchair has ever come up the stairs".

#accessibility #A11y

Hey #webdev bubble - can any of y'all recommend resources to learn about accessibility?

I'm aware of the WCAG guidelines as the "golden standard", but I'm looking for something more bite sized / approachable than 75 pages of raw paragraphs and rules

Boosts welcome!

#wcag #accessibility #html

Hey #webdev bubble - can any of y'all recommend resources to learn about accessibility?

I'm aware of the WCAG guidelines as the "golden standard", but I'm looking for something more bite sized / approachable than 75 pages of raw paragraphs and rules

Boosts welcome!

#wcag #accessibility #html

After spending half an hour changing the fonts on a platform that lacks accessibility or customization options, I want to suggest a browser plug-in called Stylebot. It’s like Stylus, but much easier to use.

https://stylebot.dev/

#Accessibility

After spending half an hour changing the fonts on a platform that lacks accessibility or customization options, I want to suggest a browser plug-in called Stylebot. It’s like Stylus, but much easier to use.

https://stylebot.dev/

#Accessibility

A first draft of the "Accessibility Roles and Responsibilities Mapping (ARRM)" document has been published!

https://www.w3.org/WAI/planning/arrm/

This resource helps "[…] defining roles, tasks, and responsibilities for meeting Web Content Accessibility Guidelines […]".

Worth a read!

#web #digital #accessibility #product #design #development #a11y

The Web #Accessibility Slack community attracts an unfortunate share of asks that go something like:

"I have an interview/have been tasked with giving a presentation/have been promoted to a role and need to become an expert in accessibility by tomorrow, but I know nothing. Can you please send me free resources?"

And like... it's up to every community member whether or not to respond to these, and I'm all for encouragement. But does accessibility really need people who aren't willing to pay for materials, have unrealistic expectations of how much there is to learn, and may have even lied their way into a position they clearly don't want?

I think not, personally.

Sharing some cursors. I modified the Hackneyed cursors to be high contrast and disable the animation, available as monochrome or multicolour. They use the Windows 10 and 11 default cursor colours. You can also pick any colours you want if you build from source (Codeberg).

You can download directly from my website or OpenDesktop.org.

https://futurehorizondesign.net.au/portfolio/hackneyedhighcontraststaticcursors.html

#cursor #linux #foss #opensource #windows #accessibility #a11y #accessible #ui #uidesign #retrocomputing #retro #xfce #kde #freesoftware

Hello “Mast”ers,
Is there way for users to setup translation for posts to preferred language in Mastodon?. In my case, my preferred language is English and I would like for an option at the bottom or in the ellipsis to translate it on request. This way we would have access to more streams of thoughts and perspectives without the confines of the language. Is it just about tweesecake enabling it?
Translation is accessibility too.
#translation #accessibility #TweeseCakeSocial #mastodonengineering

Ever since I saw @klemensstrasser have support for the OpenDyslexic font in @studysnacksapp I’ve been meaning to do the same.

I was really worried about breaking the layout of some Views.

Seeing @hidde do it made me decide to just start.

Making good progress!

#accessibility #a11y #OpenDyslexic

Ever since I saw @klemensstrasser have support for the OpenDyslexic font in @studysnacksapp I’ve been meaning to do the same.

I was really worried about breaking the layout of some Views.

Seeing @hidde do it made me decide to just start.

Making good progress!

#accessibility #a11y #OpenDyslexic

#introduction
Hi! I'm Michael, or Fubsepude.
I'm a #blind #autistic music and tech-enthusiast from Denmark.
I love listening to and creating music, computers and just hanging out and meeting new people.
#accessibility
#audio
#blind
#autistic
#music
#tech

just under TWO WEEKS until the submission deadline for Good Internet magazine: march 15, 2025!

☂️ Good Internet launches in May 2025. it's a volunteer-run, not-for-profit print and digital quarterly magazine for personal website owners and those interested in using the internet as a means of self-expression, art, and recreation.

🔎 we're looking for 1,500 to 4,000 word articles about anything for that audience!

👉 this means #webdev hobbyists, digital (and traditional) #artists, #internet culture enthusiasts, #technology nerds, #socialmedia expatriates, & anyone who wants to unplug from the corporate-owned #web.

topics could be:

* internet history
* personal websites & blogs
* #accessibility on the #indieweb
* finding inspiration for a #blog
* #webdesign trends (current or old)
* running from the #enshittification of the web
* lessons or post-mortems from web projects
* news or overviews of #opensource projects
* #privacy on the indieweb

🔍 also looking for any #art submissions centered around the web, coding, internet culture, and digital art!

if it relates to hobbies on "this side of the web," we probably want to run it!

✨ you can have your article submitted as text and images only OR you can code a whole webpage that helps tell your story!

🌊 if you're interested in learning more, sign up for our email list or check out the submission guidelines @ https://goodinternetmagazine.com!

🙏 (please boost if you can! <3 getting the word out helps so much!)

#writing #publishing #magazine #html #css #tech #css #javascript #rss #mastodon #google #facebook #amazon #resist

Last night I started writing a blog post about why LLMs don't generate good #accessible markup, mainly to get some thoughts out of my head. Now that I've sunk two thousand words into it I feel like it's tipped the scales into "deserves to be finished" territory. #accessibility

We are thrilled to announce that the Solarpunk Conference is now officially a nonprofit organization!

This conference is created and produced by dedicated volunteers and puts community, accessibility, and a better future at the forefront of its mission.

#solarpunk #SolarpunkConference2025 #accessibility #sustainability #nonprofitorganization

Dear Lovely Peeps:

An (re?) #Introduction might be in order. I have decided it is time to stop wandering & settle down in a nice sunny garden. 😊

I've been around since 2016, and wherever I am, I try to create a wee gentle eddy of peace & whimsy in my corner of the Fediverse. 😇

I have a #hope-full perspective. Am strongly influenced by #DoctorWho. 😄 Believe in a #SolarPunk / #HopePunk future. Manage to find small good things to celebrate every day. 🎉

Am interested in #FOSS, #travel, #photography, #sustainability, #accessibility, #reading, #writing, being #outside, #LowTech / #NoTech solutions, and a whole lot more.

(I have a neuro-spicy brain so 'a whole lot more' really is a LOT! 😄 )

Come in, have a scroll, and maybe breathe a little easier. I hope you enjoy your time here. 💛

Nice tips document on how to write accessible app UIs, or debug accessibility when it doesn’t seem to be working quite right: https://gitlab.gnome.org/GNOME/orca/-/blob/main/README-APPLICATION-DEVELOPERS.md

#GNOME #accessibility

https://itch.io/b/2850/rpgs-for-accessible-gaming

An itch.io bundle hosted by jesthehuman with content from 109 creators.

Buy 247 items for $10 Regularly ~$729 Save 98%!

Ends in 16 days

#itchio #gamebundle #accessibility

https://itch.io/b/2850/rpgs-for-accessible-gaming

An itch.io bundle hosted by jesthehuman with content from 109 creators.

Buy 247 items for $10 Regularly ~$729 Save 98%!

Ends in 16 days

#itchio #gamebundle #accessibility

Nice tips document on how to write accessible app UIs, or debug accessibility when it doesn’t seem to be working quite right: https://gitlab.gnome.org/GNOME/orca/-/blob/main/README-APPLICATION-DEVELOPERS.md

#GNOME #accessibility

I made the thread into a post so you can share it with your social media manager or your mom or whatever:

“Don’t Use Fake Bold or Italic in Social Media”
https://adrianroselli.com/2025/03/dont-use-fake-bold-or-italic-in-social-media.html

#a11y #accessibility

Nice tips document on how to write accessible app UIs, or debug accessibility when it doesn’t seem to be working quite right: https://gitlab.gnome.org/GNOME/orca/-/blob/main/README-APPLICATION-DEVELOPERS.md

#GNOME #accessibility

Nice tips document on how to write accessible app UIs, or debug accessibility when it doesn’t seem to be working quite right: https://gitlab.gnome.org/GNOME/orca/-/blob/main/README-APPLICATION-DEVELOPERS.md

#GNOME #accessibility

Imagine your local government sends this:

𝑇𝑠𝑢𝑛𝑎𝑚𝑖 𝑤𝑎𝑟𝑛𝑖𝑛𝑔: 𝗠𝗼𝘃𝗲 𝘁𝗼 𝗵𝗶𝗴𝗵𝗲𝗿 𝗴𝗿𝗼𝘂𝗻𝗱 𝗶𝗺𝗺𝗲𝗱𝗶𝗮𝘁𝗲𝗹𝘆. Updates to come in the next hour. Stay calm.

Now imagine the impact on screen reader users.

End of thread.

#a11y #accessibility

Gemini is definitely helpful, but when using Talkback, it can be very frustrating!

(Yes, you can toggle speech as a workaround, but it can be frustrating to have to do this repeatedly when those not using talkback don't have to.)

https://youtube.com/shorts/Zlke-Z5hzMQ

#Accessibility #A11y

just under TWO WEEKS until the submission deadline for Good Internet magazine: march 15, 2025!

☂️ Good Internet launches in May 2025. it's a volunteer-run, not-for-profit print and digital quarterly magazine for personal website owners and those interested in using the internet as a means of self-expression, art, and recreation.

🔎 we're looking for 1,500 to 4,000 word articles about anything for that audience!

👉 this means #webdev hobbyists, digital (and traditional) #artists, #internet culture enthusiasts, #technology nerds, #socialmedia expatriates, & anyone who wants to unplug from the corporate-owned #web.

topics could be:

* internet history
* personal websites & blogs
* #accessibility on the #indieweb
* finding inspiration for a #blog
* #webdesign trends (current or old)
* running from the #enshittification of the web
* lessons or post-mortems from web projects
* news or overviews of #opensource projects
* #privacy on the indieweb

🔍 also looking for any #art submissions centered around the web, coding, internet culture, and digital art!

if it relates to hobbies on "this side of the web," we probably want to run it!

✨ you can have your article submitted as text and images only OR you can code a whole webpage that helps tell your story!

🌊 if you're interested in learning more, sign up for our email list or check out the submission guidelines @ https://goodinternetmagazine.com!

🙏 (please boost if you can! <3 getting the word out helps so much!)

#writing #publishing #magazine #html #css #tech #css #javascript #rss #mastodon #google #facebook #amazon #resist

Gemini is definitely helpful, but when using Talkback, it can be very frustrating!

(Yes, you can toggle speech as a workaround, but it can be frustrating to have to do this repeatedly when those not using talkback don't have to.)

https://youtube.com/shorts/Zlke-Z5hzMQ

#Accessibility #A11y

🤑 Let’s face it. The #accessibility industry is about profit not accessibility 🖖🏼

🤑 Let’s face it. The #accessibility industry is about profit not accessibility 🖖🏼

today is officially *THREE* weeks until the submission deadline for Good Internet magazine!

Good Internet launches in May 2025. it's a volunteer-run, not-for-profit print and digital quarterly magazine for personal website owners and those interested in using the internet as a means of self-expression, art, and recreation.

🔍 we're looking for 1,500-4,000 word articles about anything related to that!

you could write about:

* #internet history
* personal #websites
* #accessibility on the #indieweb
* finding inspiration for a #blog
* #webdesign trends
* running from the #enshittification of the #web
* lessons or post-mortems from #webdev projects
* news or overviews of #opensource projects

if it relates to hobbies on "this side of the web," whether you call it the #smallweb or indieweb, we probably want to run it!

you can have your article as low-media (meaning only text and images) or interactive, where you code an entire webpage to help tell your story.

if you're interested in learning more, you can sign up for our email list for when we launch or you can check the submission guidelines @ https://goodinternetmagazine.com!

(please boost if you can! <3)

@librewolf @Stealthy So, time for the all important question, at least for me and other blind folks. Does LibreWolf have the same level of accessibility for screen readers as FireFox? If not, why? I have to ask, as I’d rather not waste my time on an inaccessible web browser, and I imagine other screen reader users like myself would agree. #A11Y #Accessibility #Blind #ScreenReader

NVDA 2024.4.2 / Firefox 135.

Doesn’t announce the fake bold nor fake italic.

#a11y #accessibility

Those two videos account for ~78% of primary screen reader use (https://webaim.org/projects/screenreadersurvey10/#primary) so I’m stopping there for today.

Anyway, this is not new information: https://adrianroselli.com/2018/01/improving-your-tweet-accessibility.html#Unicode