Follow #a11y from Mastodon or any other Fediverse app and its public posts arrive in your timeline. No vutuv account needed.
@a11y@tags.vutuv.de
Steve Frenzel Frontend developer @ GFE Media GmbH
Lara Dufour Développeuse front-end @ PROWEBCE
35 posts
iOS 27 : de nouvelles fonctions d’accessibilité mais aussi de nouveaux bugs.
Apple a notamment enrichi VoiceOver et Loupe avec Apple Intelligence pour proposer des descriptions plus précises et interactives.
Cependant, la mise à jour a aussi introduit des bugs qui peuvent compliquer le quotidien des personnes aveugles, malvoyantes et malentendantes.
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”.
New blog post in my series about using the HumanWare BrailleNote Apex with #FreeBSD! This time, I explore USB communication in USB Client mode.
Le sous-titrage des vidéos sur le web est indispensable pour les personnes sourdes et malentendantes. Mais tous les sous-titres ne se valent pas !
Sophie Schuermans partage les bonnes pratiques à suivre et des outils pour créer des sous-titres accessibles plus facilement.
So whoever needs to hear this:
The latest “AI” frontier models do NOT generate #accessible web pages.
They will not automate #accessibility testing, cannot take the role of a manual tester, will not magically fix all #accessibility issues on your website and cannot catch accessibility issues for you no matter how strictly you frown at them. What they will do is give you dramatically verbose, overengineered solutions to problems that don’t actually exist.
I just tested this today. You still need a human in the loop who knows what they’re doing. i’m one of those, happy to help if you pay me tokens. And by tokens I mean fair wages.
Don’t get me wrong, I do use #AI for my own projects at times. They just really aren’t good at this.
En novembre, montez en compétences sur l’accessibilité numérique ! 🗓️
Quelques places encore disponibles dans nos prochaines sessions :
Pourquoi certains critères WCAG sont en A, AA ou AAA ?
@alastc@toot.cafe explique les arbitrages derrière les différents niveaux de WCAG, et plus largement ce qui entre ou non dans la norme.
Une approche fondée sur le compromis : concilier les besoins des utilisateurs, la faisabilité pour les organisations et l’acceptation du standard par le plus grand nombre.
(en anglais) a42.fr/wcag-leveling-process
Vous débutez en accessibilité ? Le sujet vous semble vaste et complexe ?
Access42 vous propose une entrée en douceur avec son parcours e-learning « Découvrir et prendre en compte l’accessibilité numérique ».
Au programme : 10 h de contenus, avec des ressources écrites et audio, des quiz et des exercices, pour avancer à votre rythme.
Sur le blog, notre collègue Kathy Casalino, ingénieure pédagogique, revient sur la création de ce parcours :
My company just made a sizable contribution to @lolaodelola@mastodon.social’s Accessible Compat Data project. I think a project of this complexity needs to be well-funded and as the big companies don’t care about accessibility enough, this is up to us.
I call on all accessibility companies to help fund this research and data project.
opencollective.com/lolas-lab/…
See @eric@social.ericwbailey.website’s article why this is so important: ericwbailey.website/published/…
Comment les lecteurs d’écran restituent-ils une page web ?
@craigabbott@a11y.info de @TetraLogical@indieweb.social explique que les lecteurs d’écran s’appuient sur l’arbre d’accessibilité (« accessibility tree » en anglais), c’est-à-dire une version filtrée et traduite du DOM construite par le navigateur web à partir du HTML, du CSS et du JavaScript :
(en anglais) a42.fr/accessibility-tree
Comment se préparer au RGAA 5 ?
Signalement des points bloquants, téléservice de dépôt des déclarations d’accessibilité, nouveau modèle de schéma pluriannuel, rôle de l’Arcom…
Notre collègue @luce@mastodon.design analyse les annonces de la DINUM présentées lors de la 21e édition de Paris Web.
À lire sur notre blog :
a42.fr/pw2026-cr
Here it is - I have created Issue 776 on WriteFreely’s github for a serious accessibility issue I am meeting with screen readers. Yes, many things should be improved but this one is the most urgent because it’s blocking me.
cc @writefreely@mastodon.uno @write_as@writing.exchange @matt@writing.exchange
Mentioning also @michael@theatl.social who forked WriteFreely as far as I can remember.
Here’s the issue’s link:
Formez-vous à l’accessibilité numérique en novembre 🗓️
Trois formations à distance pour améliorer la conformité de vos services numériques :
I’m leaving WordPress platform very, very soon.
Mullenweg must give clear, transparent answers on what he wants, because we are thousand of people with disability, left behind.
An Open Letter to Matt Mullenweg on Accessibility in WordPress – Blind Access Journal blindaccessjournal.com/2026/…
New post: Outside the Scope of Our Support
Google Disability Support’s final answer on the touch exploration bug: broken accessibility features are in scope, but my report wasn’t. They sent me to a forum. The issue I filed myself on the public tracker reached an engineer in 102 minutes.
And if a blind user who isn’t a developer had reported it? They’d get a cache to clear and a reboot. They should never have to file the bug themselves.
I’m going to get straight to the point with this one.
I am in a room named #a11y:gnome.org. It’s on Matrix, you can access it yourself, anyone can due to it’s public nature.
During the latest conversation, Matthias Clasen is quoted as saying: “one thing to keep in mind is that the w3c stuff is just somebody writing down some made-up rules”
This is after a Ubuntu developer requested an improvement to gtk, highlighting some inconsistencies with combo boxes and other things. The conversation is far too long to post here, but you can easily read it yourself.
Regardless of the conversation, or agreements or disagreements, this is an utterly unacceptable thing to say, particularly if this individual is endorsed by Gnome.
It’s unacceptable for three important reasons: It completely invalidates the accessibility work that is being conducted to improve the Gnome desktop (discarding the hard work of other devs who contribute their efforts towards these supposedly nonsensical guidelines).
It is extremely disrespectful to blind and visually impaired people and others with disabilities who, at the end of the day, just want to use open source software like anyone else. I have definitely witnessed disagreements regarding the w3c and respect that it can’t be implemented to the letter. I have never ever before heard anyone dismiss it entirely, as if it were nothing more than a spec of dirt.
Finally, it makes constructive conversation extremely difficult, how is someone supposed to work with a developer on accessibility, when they possess such an unconstructive attitude?
I feel obligated to call this out, even though I do worry that it may cast doubt on other Gnome developers, but no, too much is too much.
I would like to thank those who are striving to make Gnome and it’s applications more accessible and those who choose collaboration over ignorance.
I’d appreciate if people could make an effort to keep replies constructive, I am doing this as advocacy and challenging what I believe to be a harmful attitude. Linux accessibility won’t improve while people like this are in control of it’s components.
Edit: I have just determined through research that Matthias is actually a manager of Red Hat’s desktop team, making his statement even more damaging.
@gnome@floss.social
@redhat@mastodon.social
Sensitive. Show the picture.
Cover it again
Genuinely starting to feel the burnout so many of my friends and colleagues in the #a11y community have felt over the course of their careers.
This is triggered every time I see someone say “AI has made it so easy to create websites that are accessible”.
I honestly don’t get it. Even if you interrogate an LLM it will tell you that it can’t create ‘accessible code’ that is ‘reliable’ without human oversight and verification.
Either we a11y advocates aren’t doing enough or are simply not heard?
Comment faire une tuile accessible pour votre design system ?
Yves Pol Cabon de Boscop propose une méthode pour créer des tuiles accessibles sans encapsuler tout le contenu dans une balise de lien :
Tomorrow, October 16th, marks Practical Accessibility’s third birthday. 🎂
To celebrate, I am gifting everybody 25% off for the next 48 hours 🎁 Individual and team licenses alike!
The discount is automatically applied during checkout—no code is needed.
👉🏻 practical-accessibility.today
Enjoy! #a11y
New post: Have You Tried Turning TalkBack Off and On Again?
An Android bug can kill touch exploration for every screen reader until you reboot. I traced it to a stuck injected pointer in the input dispatcher and sent Google Disability Support a detailed report. Their answer: turn TalkBack off and on, clear Accessibility Suite’s cache, and reboot. Only then would they consider passing it to an engineer. Their form wouldn’t even accept my logs, only screenshots.
fireborn.mataroa.blog/blog/…
