A great introduction

It is not a must, but better with it!

Yes I agree too. Somewhat not on my nerves.

aria-label and aria-labelledby aren’t permitted on these elements. They are intended for interactive elements (buttons, links, form controls) and landmark regions.

The author provides the HTML elements that are not allowed to have an aria-label or aria-labelledby.

VoiceOver generally announce the contents of the aria-label. That aria-label “works” on generic elements in VoiceOver is a nonstandard remediation of noncompliant code, not an endorsement of a technique working as intended.

The author provides multiple HTML patterns to avoid the use of aria-label in the first place! Great!

• Was the Label Addressing a Problem Worth Solving in the First Place?
• Use visible text
• Use Visually-Hidden Text
• Use More Semantically Applicable Elements
• Add an Applicable Role

Les entreprises ITSM-NG avec XWiki et
ITSM-NG, en lient avec Opensource Experts.

Un audit d'accessibilité peut être réalisé avec l'outil Ara

Basé sur la dernière version du référentiel général d’amélioration de l’accessibilité (RGAA 4.1), avec Ara vous pouvez :
– Faire un état des lieux (audit partiel de 25 ou 50 critères)
– Faire un audit complet, dit de conformité (106 critères)
– Générer votre rapport d’audit et votre déclaration d’accessibilité

Are hCaptcha not accessible to screen readers?

What is accessible for an accessible button.

L'accessibilité au clavier de base 😄

C'est un challenge

It reflects ARIA presses state with CSS. Isn't it already built-in ?

I am using it for aria-current.

How to create accessible spoilers without JS? Well it's a tradeoff.

What are the 80% quickwins?

• alt texts or attributes for images are missing
• Contrats
• everything usable with a mouse should be touchable on smartphones or actionable through the keyboard
• provide metadata in HTML markup for documents or informations

The 20% left is ARIA.

Another idea for the ‘problematic 20%’ would be to get (paid) help from those affected and/or specialised teams. But both groups would be happy if the organisation booking them already knew the basics, went 80% of the way to accessibility and thus came into the project as specialists for the remaining, more difficult accessibility or UX headaches (a.k.a the 20%).

An argumentation against accessibility overlays.

94 % de sites non accessibles

Raisons? Stéphane Deschamps (via https://piaille.fr/@notabene/113327840519217866) dénonce que l'accessibilité soit hautement technique; alors que la technique de base ne l'est déjà pas.

Cependant le top 3 des problèmes constatés concernent des contrastes insuffisant, des intitulés de liens et noms accessible d'images manquants. Ces erreurs sont techniquement facilement corrigeable!

Le site de l'assemblée nationale inaccessible selon le RGAA.

Another example of accessibility statement I have found so far

One good example of accessibility statement I have found so far