Regarding last boost, you may recall I have warned people to be wary of any accessibility content in posts at Google’s web•dev.
My simplest example is this 1½-year-old report on an egregiously wrong tool-tips post that its author, and site editors, have chosen to simply ignore: https://issuetracker.google.com/issues/298296173
You may think that QR codes are great for securing your login, or letting users read more online about a product marketed in a news paper ad. But there is a high risk you are creating barriers for people with disabilities, unless you use QR codes correctly.
missive from the swimming pool: while i take a little break before all the stress starts, reminder that the #id24@inclusivedesign24 call for presentations is still open until 7 June https://inclusivedesign24.org/2024/ (and a side note: we pay our speakers for their time and effort, that's what most of our supporter money goes to) #accessibility#inclusiveDesign#a11y
A new report on the Maui Project progress is now out. MauiKit4 fully based on Qt6 and KF6 is almost ready for the stable release and all the Maui Apps have been ported over. Find out more at
I wondered how they ensure that the output is accessible, because in the description I only found "#Accessibility features" under "Ready for production", nothing else.
So I wrote them an email asking to elaborate how they tackled #a11y for their product. Eagerly anticipating their answer!
L'Atelier numérique du ministère de la Culture cherche une ou un designer expert, experte accessibilité pour concevoir une plateforme destinée aux usagers en situation de handicap visuel afin de leur rendre accessible les œuvres cinématographiques via l’audiodescription.
Before designing a website, or even making a small change to an existing one, ask if your design choices consider the needs of people with color blindness. Changing the button color on your website may seem insignificant, but it could make that website inaccessible to nearly 8% of men and 0.4% of women who have color blindness.
I just realized that if you're formatting to an abbreviated weekday then VoiceOver (at least Ava and Zoe Premium) will only fully pronounce some of the days.
I guess it's because the ones that aren't pronounced are actual words with other meanings? 🤔
Text(oneShowDay.formatted(.dateTime.weekday(.abbreviated)))
@uclafa Hi! We'd love to boost this, but it's missing alt text & image description for accessibility to disabled people in the UC community. You can do that in the image editing window that pops up when you first upload the image (or can hit "Edit" on the image when you're in editing mode).
I've just pushed a bunch of #accessibility changes for screen readers to the main branch of FediThready. ( It makes long texts into post sized chunks)
I've run through it with #VoiceOver and it seems ok. HOWEVER it all feels like it's "usable" instead of "good".
If there's a #a11y geek out there who uses screen readers regularly I would REALLY appreciate some suggestions on how to make this actually feel good for folks who rely on screen readers.
It's always so frustrating when all the web accessibility content only talks about text heavy websites and forms. Like yes, I get it, I should have alt text on images. But there's so little information about how to build accessible web apps. What do I do if 80% of my page is a WebGL canvas and the other 20% is all buttons/sliders? How do I structure this if there is basically no "regular text" on the entire page?
Chrome / TalkBack bug I first reported in 2020, and which was fixed for a time (?) appears to be back. Looking for confirmation before I file yet another one.
A named region with a tabindex does not expose its contents. Chrome / TalkBack only announces its accName and role.
I think I have an ugly workaround (“Shawarma” heading).
As expected, the Chromium intake person was unable to reproduce the issue (it may have been kit this time?), so I got 5 people to confirm and added a video: https://issues.chromium.org/issues/342172183
I really do hate how hard it is just to get a bug to get taken up.
Le mode sombre et le mythe de l'accessibilité (titre original "Dark mode & accessibility myth"), un article de @stephaniewalter où elle explique que le mode sombre pose des problèmes d'accessibilité à certaines personnes alors que tout le monde pense que le mode sombre serait mieux pour l'accessibilité…
Hé oui, ce n'est pas le cas pour tout le monde ! Elle sait de quoi elle parle, et moi aussi, parce que lire sur fond sombre est terrible pour nous.
La solution : laisser le choix entre mode clair ou mode sombre !
À noter qu'il est beaucoup plus facile pour les utilisateurices de changer un site qui ne laisse pas le choix en le passant du mode clair vers le mode sombre que l'inverse car les extensions pour passer au mode clair n'existent pas.
Donc si seul le mode sombre existe sur votre site web et que le mode lecture de Firefox n'est pas activable (il est activable sur les articles uniquement et des fois, sur certains articles, ça ne fonctionne même pas), je ferme votre site direct.
(PS : ne venez pas m'expliquer que vous avez besoin du mode sombre à tout prix. Il n'est pas dit ici qu'il ne faut pas avoir de mode sombre.)