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
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)))
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?
Should I use ::after pseudo-element to add a sort order indicator?
It feels like it's not very accessible because the semantic HTML content doesn't actual contain the sort indicator... but the way I'm conditionally adding it is by reading the aria-sort attribute so maybe that's the accessible part of things and the ::after content doesn't need to be SR-friendly 🤷
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).
I am once again a bronze supporter of Inclusive Design 24.
I want to see all of you presenting cool stuff (and making me look good as a result), but you won’t get that chance if you don’t submit before 7 June. https://inclusivedesign24.org/2024/
Prior years are up there if you want to see the range of talks that have been accepted in the past.
During her presentation at @DeepDishSwift my jaw hit the floor when Kim Arnett said that not supporting landscape in your app could be an accessibility problem.
I started taking some baby steps towards supporting landscape mode in Please Don't Rain.
Edit: Fixed the background color not extending fully to the left and right by adding .edgesIgnoringSafeArea(.all) to the Color in my .background modifier.
I was curious about what percentage of people visiting my site had set preferences for light/dark mode, reduced motion, or increased contrast. I also wanted to know what percentage had HDR support.
I figured out how to do that custom tracking with @plausible and wrote a tutorial.
Access for All: Two friends helping change opportunities for blind people with an open-source screen reader for all. Now on Microsoft Unlocked: https://unlocked.microsoft.com/nvda/
[Nouvelle BD rendue accessible] Dites adieu aux kilos en trop
Bon alors, pour en finir avec cette question : dans 1 ko, il y a 1000 octets ou 1024 octets ? Eh bah… c'est un peu compliqué. Je vous explique tout ça.
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.)
For those of you who demanded that #Sonos make their app more #A11Y friendly, you got your wish. There's a new update out for it today. Please feel free to boost for those who don't already know. You're welcome. Smiley