(via https://a11y.info/@WebAxe/112880703997755323)

Specific resources. They seems qualitative

Didn't read, but it can be useful someday

• Alternative characters are not always searchable
• Alternative characters are not accessible for everyone

Quelques commandes devraient pouvoir être plus accessible. Alsace Réseau Neutre en a réalisé une liste

Why we should avoid it? Because it can go wrong in so many way. The post describes different cases.

A HTML validator aiming to be better than the current W3C HTML validator.

There is a descriptive page: https://validator.w3.org/nu/about.html

The mansory layouts is broken for tabbing and keyboard accessibility

Nice resources about accessibility on the web

I find it difficult to answer the question “is [blank] accessible?” Because usually there’s like 10 levels of explanation required to actually answer the question.

Things like accessibility compliance, inclusive usability, accessibility for different people and needs, all affect the answer.

1. Utiliser le camelcase
2. Positionner ces hashtags à la fin de la publication pour éviter d’alourdir leur restitution par les lecteurs d’écran.
3. Utiliser les accents afin que ces mots soient correctement lues

Les exemples données sont aussi en fichiers audio.

Accessibility issues is not only permanent but also temporary and situational.

Another font made for readability and accessibility.

Make the logo bigger? Nope.
Delete the logo and make the font size bigger.

The challenges of creating accessible products often lead to innovative solutions that benefit all users, pushing the boundaries of what's possible in design.

Simply run these scripts on the web page to trigger some actions.

• Validate HTML
• Calculate carbon
• WAVE
• PageSpeed
• SSL Report
• Security Headers