Digital accessibility job for the state of CA
https://calcareers.ca.gov/CalHrPublic/Jobs/JobPosting.aspx?JobControlId=488564
Guide pour des alts tout beaux
Comment rendre une conférence ou une présentation accessible ? Bonnes pratiques et outils.
Un récapitulatif de tous les points de vigilances à prendre en compte et bonnes pratiques à mettre en œuvre au moment de concevoir puis d'animer une présentation en public, de telle manière que les contenus soient accessibles à toutes et tous.
par @access42
https://access42.net/conference-presentation-accessible-bonnes-pratiques-outils/
New blog post, on why we should probably ditch the term “best practice” when doing accessibility audits.
Big shoutout to everybody that got involved in the originals discussion. I’ve tried to capture all the great points you all raised!
https://www.craigabbott.co.uk/blog/best-practice-is-just-your-opinion/
Most def. Thanks for tagging me in!
https://inclusive-components.design/
https://silviamaggidesign.com/ (@silviamaggi)
https://neurodiversity.design/
https://gerireid.com/blog/wcag-design-checklist/
https://bitsofco.de/the-accessibility-cheatsheet/
https://accessiblenumbers.com/
I’ve also been designing/building accessible interfaces for a very long time. I should write about it more. But I did write a couple of pieces:
https://markwrites.io/build-a-simple-case-for-accessibility-with-these-5-benefits/
Cap ou pas cap ?
Passer une journée (ou plus !) en forçant le soulignement des liens, pour mieux faire tomber les masques de ceux qui se déguisent en boutons, ou des boutons qui se déguisent en liens.
This was fast!
In response to the #a11y issue I filed for the #CSS scroll-target-group property only two days ago, there is now a work-in-progress patch https://chromium-review.googlesource.com/c/chromium/src/+/6853905 to set the aria-current attribute on the active anchor in a group of HTML scroll markers. 
I've updated the blog post noting there is a WIP patch will update the post again when the issue is resolved. 
New on the blog:
“CSS-only scrollspy effect using scroll-marker-group and :target-current”
https://www.sarasoueidan.com/blog/css-scrollspy/
—
A short post about the new #CSS scroll-target-group property, how to use it with :target-current, and important #accessibility considerations to keep in mind. #a11y
Je reste surpris par le rendu par défaut de details-summary des navigateurs.
Aucune « affordance » renforcée, comme celle du lien par exemple (souligné, bleu, avec cursor pointer). Juste une petite flèche noire qui pourrait pratiquement se confondre avec une puce de liste.
Join us for 'Accessibility in Joomla!' on Aug 18, 2025, at 15h CEST. Learn how we're making Joomla accessible for everyone. Info: https://meet.google.com/qst-kbdr-atd Dial: (US) +1 609-736-2891 PIN: 916 429 247# #Accessibility #A11y #Joomla #20YearsJoomla
Access Information News for Monday, August 18, 2025 - Volume 1028
https://accessinformationnews.com/ain2025/08182025/
️ The Week's News in Access Information
A Mind Vault Solutions, Ltd. Publication
#news #accessibility #a11y #disability #blind #deaf #deafblind #ain
Access Information News. The world's #1 online resource for current news and trends in access information.
Subscribers: 40,525 
️ subscribers were sent this issue via email.
Sei #A11y und unterstütze den Zugang zum !@metalab für Menschen mit Sehbehinderung oder Blindheit! Komm zum Do-It-Blind (DIB) Treffen 
am Montag, 18. August, Treffpunkt Ring-Passage, U3-Station Volkstheater um 16:00; Ende 20:00 https://metalab.at/calendar/event/8151/icalendar/ #make #blind #inklusion
Aucards, application dispo sur #fdroid pour afficher clairement sur l'écran du tél. des mots ou séries de caractères, est bien en cas de fatigue, où j'aurais besoin de dire des choses importantes (du genre "où les toilettes svp")
J'ai peut-être pas vu d'autres fonctionnalités, ou c'est peut-être tout ce qu'il y a...
lien : https://apt.izzysoft.de/fdroid/index/apk/vadimerenkov.aucards
Anyway. It's great that you're even thinking about this stuff. Most web developers simply don't. Until they get sued.
Do your best, keep it in mind. If you do that, disabled users will really appreciate it. Because their current experience of the web is overwhelmingly crap.
And if your site is more usable than your competitors' ... that gives you an advantage. You can reliably reach at least 25% more users.
L’interface de ChatGPT n’est pas accessible.
@SteveFaulkner donne quelques exemples d’erreurs sur son blog.
https://html5accessibility.com/stuff/2025/08/15/ai-effluential/
Oh, and I am unconvinced of the wisdom of using a definition list for navigation. That's not what it was intended for, and assistive tech support is patchy.
A simple <ul> or <ol> inside a <nav> landmark is probably a better option.
Also you probably don’t want to use description lists (dl) in this case, they come with additional announcements that are not really suitable to navigation items. A simple nested unordered list (ul) in a navigation element (nav) is sufficient.
#a11y (2/2)
Using aria-current is preferable.
If there is no <a> element, it's not keyboard-focusable. For screenreader users, it would be omitted entirely from tab order, or from a list of links.
For sighted keyboard users, skipping past it in navigation would be strange behaviour.
For this reason, you need to also give a visual indication that this is the current page, they won't have access to aria-current information.
Ambassador 
