Accessibility in the NewsHow to Build an Audio Description Strategy That Actually Works https://www.3playmedia.com/events/wbnr-03-11-2026-audio-description/ #a11y
Pratik PatelI hate dealing with UIA.
Adrian Roselli, pH0While I think the title is a clear “well, yeah”, I appreciate Sheri gives reasons regardless:
“Why you shouldn’t trust the people who built your inaccessible site to fix it”
https://buttondown.com/access-ability/archive/why-you-shouldn-t-trust-the-people-who-built-your/
If WCAG guarantees aren’t built into the contract, find another vendor.
When Comicon and other fan conventions focus on accessibility, everyone wins https://www.cbc.ca/arts/when-comicon-and-other-fan-conventions-focus-on-accessibility-everyone-wins-9.7133375#:~:text=Arts-,When%20Comicon%20and%20other%20fan%20conventions%20focus%20on%20accessibility%2C%20everyone,more%20meaningful%20experience%20for%20many. #a11y
bugsmith"﷽" U+FDFD: ARABIC LIGATURE BISMILLAH AR-RAHMAN AR-RAHEEM (Unicode Character)
GNOMEThe GNOME 50 release of our Calendar app also brings a very nice accessibility change: it’s now possible to navigate through events via the keyboard! ⌨️
In addition, many accessibility labels have been updated to improve the overall experience with screen readers.
Thanks to @TheEvilSkeleton and @zoeyTheWitch for making this happen!
W3C Developers@w3c recharters its Internationalization #WorkingGroup through March 2029
▶️ https://www.w3.org/International/groups/wg/charter-2026.html
The group's new work includes HTML Ruby Markup Extensions (better support for phonetic annotations), Ruby Text-to-Speech (#a11y support for #ruby annotations) and Message Resources (for easier localization) #i18n @webi18n
📢 If you believe the Web should speak your language, join or rejoin the group!
https://www.w3.org/groups/wg/i18n-core/join/
Access42Nous avons besoin de vous pour relire les nouvelles traductions en français des WCAG 2.1 et 2.2 ! 📣
Répondez à l’appel à commentaires du @w3c par e-mail jusqu'au 6 avril 2026.
La procédure est simple et tout le monde peut y participer :
Commentez les nouvelles traductions candidates en français des WCAG 2.1 et 2.2 jusqu’au 6 avril 2026 – Access42
Après plusieurs mois de travail avec le comité de traduction, le W3C lance l’appel à commentaires publics sur les nouvelles traductions candidates en français des WCAG 2.1 et 2.2. Vous pouvez relire et commenter ces documents jusqu’au 6 avril 2026 inclus. Cet appel à commentaires est ouvert à tout le…
fortrabbit
Silvestar BistrovićIan Lloyd provides a collection of accessibility audit bookmarklets for testing WCAG compliance and identifying accessibility issues.