Search

Items tagged with: accessibility

So rblind.com didn't go down, and it isn't anymore broken today than it usually is. Cloudflare breaks #accessibility. It always has, and it always will. Now the rest of you know how it feels to be locked out because you don't run JavaScript and can't solve a captcha. Will you stop using #cloudflare? No, of course not! If it blocks #AI, you're completely fine with denying that blind users might be human at all. As AI becomes more and more capable, the definition of "human" is going to become more and more restrictive, until everyone who isn't completely able bodied and doesn't have absolutely perfect vision, hearing, and cognition is completely excluded.
#Accessibility #AI #cloudflare

#a11y #Accessibility #wcag

J'ai lu que le ministère de l'éducation est « intéressé » à faire passer les écoles à Linux.
si cela est fait, l'éducation des non-et malvoyants en France sera complétement foutue. L'accessibilité de Linux est inacceptable pour en faire une plateforme d'éducation des enfants.
vous voulez passer à Linux ? Soit. Je suis pas d'accord, mais soit. Dans ce cas-ci, il faut *d'abord* investir en accessibilité de cette plateforme, et puis « s'intéresser » à quoi que ce soit.
J'espère bien qu'il y aura des appels à la justice. L'Acte Européen d'Accessibilité est en vigueur, et si l'état même s'en fout, comment peut-on exiger l'accessibilité aux autres ?
#Accessibilité #Linux #OpenSource #Accessibility
#Accessibility #linux #opensource #accessibilité

#a11y #Accessibility #ecommerce #etail

I've read that #Firefox users want "just to use a sturdy browser". I don't know, maybe something is wrong with me, but whenever I tried using Firefox (I don't like its #Accessibility anyway — it's accessible, don't get me wrong, but it's just… other way), it crashed far, far more often than Chrome and Edge together.
#Accessibility #firefox

So last night, I tried Fedora 43. Fedora-Workstation-Live-43-1.6.x86_64.iso. The installer is now web based, making it really nice to use, even with just Tab and Shift + Tab. I was able to install it with no problem.

Now, first time setup had just one big issue, the timezone selector. It's keyboard accessible, and works like this: you start typing a city name, like Chicago, and then down arrow through suggestions and press Enter on the one you want. But Orca doesn't speak that there are suggestions available, and does not read which suggestion you select until you press Enter.

Other than that, Gnome desktop looks pretty good these days! The settings are much better, and that's about all I had time to test so far. Orca starts if you hit Alt Windows S at the installer and first setup, then starts after first setup is complete. The overview panel where you type to search doesn't read when it opens, but basically you just hit the Windows key and start typing what you want, and Orca reads what you hand on, and you can arrow through results. Notifications read too, and I'm thankful Gnome supports notifications.

#accessibility #blind #fedora #linux #foss @fedora

#Accessibility #linux #foss #blind #fedora @Fedora Project (F43 is OUT)

I’m surrounded by boxes. We’ve finally finished all the modifications, and we can move into our dream home tomorrow.
I’m sitting here looking at the house’s own website where we can control everything from, and the iOS app, and I’m awe struck by what we’ve built. I just hope it’ll be a very long time before we move again because I’m not sure we’ll ever do this so well again.
We got so lucky with the company I picked for this project. He wasn’t super knowledgable about #accessibility when we started working together, but he took me seriously and got into the challenge of finding the best options. I’m sure there will be shortcomings we identify once we actually live there, but we have the fundamentals right and the infrastructure, so it’ll be fun to tweak it and watch it grow.
I told Bonnie to say goodbye to the house when she left it this afternoon. It responded by turning off the Sonos, turning off the TV, and after sixty seconds it locked the door and set the alarm.
The visual descriptions it gives over all the Sonos’s of who is at the door, when it doesn’t recognize the person by name, are so detailed and vidid. And on and on and on. I’m really thrilled by what we’ve ended up with.
But there is one final thing I would say about this. It’s been a fun project, but even if we were moving into a tin shack, it would be a palace as long as Bonnie is there too.
#Accessibility

I am happy to announce this book that i wrote a chapter in. My chapter looks at the ethics of #accessibility #sustainability and #OpenSource so touches on many threads. It is amazing to have contributed a small part of this first work of accessibility ethics. routledge.com/Digital-Accessib…

Digital Accessibility Ethics: Disability Inclusion in All Things Tech

Digital Accessibility Ethics is a practical guide with an urgent goal: to help end tech exclusion of 1.3 billion people across the world with disabilities.
Routledge & CRC Press
#Accessibility #opensource #sustainability

So about the #Mona app. Given that version 7 is going to be a massive app rewrite and refactoring, I have many issues. The first is the paying. This app is a huge rewrite. All that time and effort? That deserves money. Where I put my foot down is you making a whole new app to get around all of the people, including me, that paid for lifetime subscription. That seems wildly underhanded to me. And you’re releasing it as a new app? Rather than a app upgrade? To make sure that we’re kind of forced to pay for the new app? Hard no from me. I read every single reply in that thread. There is a test flight link. Even though it is in beta, it is relying way too heavily on LLM’s for me to want to try it. I read in the thread that choosing a post language is no longer an option, and that the app relies on an LLM to guess what that language is. Even in a beta, that clearly signals what you started developing direction wise and I’m just not interested. I keep thinking about the question I asked the developer long before Mastodon had it’s moment. The developer told me no Mastodon app would be made. Fine. But this looks like cash cow development to fund whatever LLM you stuck in the app. I’m not happy. The accessibility of the app is unmatched, especially for VoiceOver users, but I fund honest, even agressive, donation requests. I will happily pay a subscription to support development but not like this. Is there another app with as much care and VoiceOver love? #Fediverse #Mastodon #Accessibility #A11y
#a11y #Accessibility #fediverse #Mastodon #mona

Question for those of you who host a LLM by themselfs with Ollama, llama.cpp and use it for example for generating alt texts for images.
What LLM do you recommend? Which one generates a good description for screen reader users with the least amount of computing?

Whats your experience with that? Bonus points for LLM's which perform really good in CPU only situations.

#selfhosting @homelab @homelab_de #llm #accessibility

#Accessibility #selfhosting #llm @Run your own homelab @Homelab Deutschland

#a11y #Accessibility @Alice Boxhall

It is impossible to overstate the contribution Glen Gordon has made to the #accessibility industry. More important even than that, his meticulous attention to detail and his understanding that something must be more than accessible, it must be efficient, has helped countless people to be productive at work, at school, and just when living life.
Glen devised many concepts that are now just thought of as the way things are done in a graphical user interface.
On top of all that, he is one of the nicest, most humble people I’ve ever met and worked with. I have heard from several young people following the National Federation of the Blind’s National Convention, at which we honored Glen with the prestigious Kenneth Jernigan award and he offered some wise advice, that Glen inspired them.
You are a legend, Glen. And although the words seem ridiculously inadequate, all I can say in conclusion is, thank you so much for all you have done.
I am pasting Glen’s LinkedIn post for those who are not over there.
Glen Gordon, Screen reading for the blind software pioneer, 24 minutes ago • Visible to anyone on or off LinkedIn, 1st
Today is a very sad day for me, since after nearly 32 years, it’s the first day that I’m no longer working on the JAWS screen reader.
I’ve voluntarily resigned my position at Freedom Scientific/Vispero because I found myself unable to continue working for a company that’s changing in ways that are moving away from my personal values.
As recently as the 2025 NFB convention, I was thinking that I’d be working on JAWS far into the future. Much to my surprise, a recent influx of new Executive leaders and customer facing product related changes convinced me that it was time to leave.
I leave behind a group of smart and passionate colleagues, and products which are the best in class. It’s been a great journey, and I thank all of you who have been users of Freedom Scientific software for some or all that time.
Yes, I’m retiring, in the sense that I’m of retirement age and not actively seeking another job. But I’m resigning in the sense that I felt I needed to take a principled stand.
I will continue doing my part to improve the state of accessibility. What that will look like will evolve over time.
#Accessibility

Web Developers & Designers

This is your friendly reminder that low vision users exist. We need font sizes that are dramatically larger than yours.

Many of us use the “minimum font size" NOT zoom, because we need bigger text, not bigger images.

I'm on the very low end of low vision needs, but my 20pt minimum font size breaks SO MANY web sites.

This pic shows how big fonts are on my screen (thumb & ruler for context).
#accessibility #webdesign

A photograph of a screen with a text editor. In front of it is a thumb holding a ruler with metric and imperial measurements. 5 lines of text are just under two inches, or five centimeters tall.
#Accessibility #webdesign

I've said it before, but it's disappointing when small things let down the #accessibility of an otherwise good interface.

For instance, I've told many people that the Tailscale web UI is actually quite good with a #screenReader. Unfortunately, the first thing an NVDA user hears after authenticating is a bunch of nonsense caused by an unlabelled SVG, and it doesn't create the best first impression:

"
banner landmark visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
visited link graphic graphic
"

#Accessibility #screenreader

#a11y #Accessibility #workplace

I usually use either #ChatGPT (for everyday tasks) or #Claude (for coding), but I found #GitHub #Copilot extremely useful when a CI job fails. There is a button that opens a menu, and one of the items is "Explain the error". It spawns a chat with a premade prompt, so no need to frentically sift through logs, first finding the failing job with a screen reader, then trying to find the error in question. It can be done of course, but afterwards, if Copilot's explanations are not good enough. #AI #AITip #Accessibility
#Accessibility #github #AI #copilot #chatgpt #Claude #aitip

Saw this in a repo somebody spun up containing source code of Apple's new web-based App Store.

Maybe they're being snarky, but you shouldn't take this advice to heart! Always ship sourcemaps in production! Always!
#WebDev #ViewSource #Accessibility

README Remember: Always disable sourcemaps in production! wink emoji
#Accessibility #webdev #viewsource

So ...there's various situations where .NET UI #accessibility just isn't as automatic as it should be. Loads of times I see perfectly good label texts within buttons, listItems, etc. that for whatever internal reason isn't actually the button's #accessible name. This has been a problem for close to twenty years now and I doubt #microsoft is ever going to fix it, so I had a crack at it. All the disclaimers apply, this is mostly just a thing I wrote for myself and I figured it might be helpful to some: github.com/zersiax/dotnet_fix
If you have to use .NET apps that seemingly have a bunch of unlabeled buttons, but object navigation reveals text inside, this might help some. No guarantees, and if it breaks you get to keep both pieces :P #foss #NVDA #screenReader #blind

GitHub - zersiax/dotnet_fix: NVDA scratchpad script to fix various .NET UI annoyances

NVDA scratchpad script to fix various .NET UI annoyances - zersiax/dotnet_fix
GitHub
#Accessibility #accessible #foss #blind #screenreader #microsoft #nvda

Global Digital Accessibility Salary Survey
gaad.foundation/what-we-do/gda…
#a11y #accessibility #salary #survey

Global Digital Accessibility Salary Survey (GDASS) | GAAD Foundation

The goal of annually collecting and sharing salary data is to inform both organizations investing or ready to invest in accessibility, along with the individuals who make technology and digital products accessible as they start or progress in their c…
Global Digital Accessibility Salary Survey (GDASS) | GAAD Foundation
#a11y #Accessibility #survey #salary

#a11y #Accessibility #podcast #audio #AltText #banner #cover @Castopod @🕹️ Yassine Doghri

does anybody know if #Yunohost management interface is accessible for screen reader users? // Est-ce que quelqu'un sait si l'interface de gestion de Yunohost est accessible aux utilisateurs de lecteurs d'écran ? Merci ! #Accessibility #Accessibilité
#Accessibility #yunohost #accessibilité

Sensitive content

#Accessibility #opensource #screenreader #nvda #jaws

@Elena Brescacin For me there are multiple reasons why to prefer @Delta Chat over other similar apps and platforms.

It's free, open-source, self-hostable, respecting privacy, giving control to users rather than to someone else who might have the whole platform under his control.

However most prominent reason why it's so appealing to me is that screen reader #accessibility is being taken so seriously and actionably from the dev team. They have no contracts, no investors, no one time opportunities pushing for accessibility features and they are working on these features from the bottom of their hearts.

Do you think so called gate keepers would care to implement some of their accessibility if they have not been pushed to do so? Why do you think it takes so long to fix some accessibility related discrepancies in the most popular messaging apps?

I think this invisible message should be warmly understood by the blindness community and other communities where it makes such a significant impact.

Aren't you happy you do have verry accessible messaging app at your disposal you can freely use to its maximum?

XMPP is good however it's not yet screen reader accessible on the major platforms.
Matrix is also good it's even fully accessible technically however it still can be improved in this regard and it's more difficult to adopt. Further accessibility improvements are more difficult to get implemented when I am comparing to delta chat.

There were other attempts at a messaging app such as tox in the past that were verry promising however screen reader accessibility has never been recognized like this.

#Accessibility @Delta Chat @Elena Brescacin

#a11y #Accessibility #aria

#a11y #Accessibility #AI #AIhype

I am looking forward to going to the @w3c 's #TPAC in Kobe Japan. I will be hosting a breakout group on #ARRM — Accessibility Roles and Responsibilities Mapping — November 12th, 16:15 JST w3.org/events/meetings/76eeff8…

More about ARRM here:
w3.org/WAI/planning/arrm/

#W3C #accessibility #roles


Accessibility Roles and Responsibilities Mapping (ARRM)

ARRM helps you assign responsibilities for digital accessibility to appropriate roles (UX designer, content creator, developer) early in projects.
W3C Web Accessibility Initiative (WAI) (Web Accessibility Initiative (WAI))
#Accessibility #w3c #arrm #tpac #roles @World Wide Web Consortium

#a11y #Accessibility #accessible #blind #screenreader

#Accessibility #jaws

Speaking on my behalf only, here are my two cents:

I’ve heard screen readers go at an astonishing number of words a second, much faster than I could read myself or process audibly.

To me, this indicates that it’s easier for a screen reader user to read larger texts than a “regular” reader, and thus can dive into longer threads in the same amount of time.

I have also noticed on Fedi that blind folks do not divide their texts into paragraphs.

While a screen reader needs no paragraphs, it is hard for (some, most?) visual readers to process a big blob of text without newlines.

As an ADHD person with information processing issues, I rarely even begin reading such walls of text.

Sighted users might also be less focused on retrieving information from text alone, but that is speculation on my part.

Perhaps it comes down to different ways of processing information, leading to various types of threads on Fedi.

#accessibility

#Accessibility

#Accessibility research study wants "to engage a diverse pool of participants." Great!

The same study is limited to "Native English speakers residing in the United States." Not so good.

#Accessibility

#a11y #Accessibility #html #memes

How is the state of PDF #accessibility on macOS for #screenReader users? If I gave someone a PDF that was prepared in a fully #accessible way, what would they use to read it with #VoiceOver, and to what extent would the accessibility be retained?

Note that I'm specifically not interested in applications that strip out all of the text to essentially make a plain version. Those can be useful when you just need to read something and don't care how, but the degree to which accessible semantics like headings, tables, lists, etc. are kept at that point is usually zero.

I'm also not asking about applications that reinvent the accessibility for PDFs and ignore what's already there, as many browsers do.

#Accessibility #accessible #screenreader #voiceover

#a11y #Accessibility #html #css

#Accessibility #linux

RE: mastodon.social/@ebassi/115429…

Got nerdsniped around lunchtime yesterday, and ended up implementing a shared "reduced motion" setting for GNOME and the rest of the xdg stack:

- gitlab.gnome.org/GNOME/gtk/-/m…
- gitlab.gnome.org/GNOME/gsettin…
- github.com/flatpak/xdg-desktop…
- gitlab.gnome.org/GNOME/xdg-des…
- gitlab.gnome.org/GNOME/gnome-c…

#a11y #accessibility #gnome #gtk #xdg #portals


Add a "reduced motion" preference to the settings portal · flatpak xdg-desktop-portal · Discussion #1839

Under GNOME we're currently abusing the boolean "enable animations" toggle, but this poorly maps to the actual accessibility issue of reduced motion. Ideally, we want to map to the same kind of set...
GitHub

Emmanuele Bassi

2025-10-24 14:28:37

mastodon - Link to source

Time for plumbing a whole new accessibility setting from desktop to toolkit: 3 hours

Time for knowing what to plumb: 20 years

Time for bikeshedding on the type of the setting: Positive infinity


#a11y #Accessibility #gnome #gtk #portals #xdg

Interesting, when a modal dialog (nested within a `<main>` element or some sectioning content) opens in Chrome it seems to disregard its context, so elements like `<header>` and `<footer>` will have `banner` and `contentinfo` roles as if they were scoped to `<body>`. When opened non-modally, they have `sectionheader` and `sectionfooter` (new ARIA roles + mapping) which means that it is computing the roles based on the dialog’s context.

Safari and Firefox keep the context is both scenarios (i.e. modal and non-modal). I have no idea what is correct. Need to read more.

Anyway, here’s a playground for the bug: knowler.dev/demos/MR4JmQW

#HTML #ARIA #accessibility

“main+header+footer nested in a dialog nested in main with adjacent header+footer” demo by Nathan Knowler

Demonstrates a browser inconsistency for the computed ARIA roles of header + footer within a modal dialog.
knowler.dev
#Accessibility #html #aria

#Zed editor on #Windows is, as expected, absolutely, one hundred percent inaccessible. I created an issue but, honestly, I'm quite pessimistic. Splendors and miseries of #OpenSource.
github.com/zed-industries/zed/…
#Accessibility

Windows: Screen reader accessibility missing completely

Summary Zed is absolutely inaccessible for screen reader users on Windows. Tested with latest JAWS and NVDA versions. Description Steps to trigger the problem: Install Zed on Windows 11. run Zed wi...
Menelion (GitHub)
#Accessibility #opensource #Windows #zed

I've been using IndentNav for a while to write Python. Recently I installed BrowserNav and now get way more positional info about HTML elements. It took some getting used to, but now the beeps and tones help me get an idea of the physical layout of a site or electron interface.
It's similar to IndentNav, but it has more rules and works with web browsers instead of being focused on code in a text editor. Positioning is one of the pieces of information that I forgot how much I miss from my sighted days. It's especially helpful with API reference docs that rely on positional encoding. Since there's more info in the browser, I only have beeps instead of precise indentation levels to get a general idea of the structure
#blind #nvda #nvaccess #browsernav #indentnav #accessibility #code
#Accessibility #blind #code #nvda #nvaccess #browsernav #indentnav

#Accessibility #drupal #eaa @Drupal Association

#a11y #Accessibility #chatgpt

⇧