Misconceptions:

1. only blind people use screen readers
2. people use screen readers in the same way
3. all screen readers work in the same way
4. building a screen reader specific version of a website or app is a good idea
5. screen reader users don't care about images
6. screen reader users need instructions on all content
7. all content must be focusable to work with screen readers

The overlays for accessibility are often wrong.

One way sighted people can determine what to put in alt text: Imagine you sent the post or article to a friend, and the image didn't load. What would someone need to know to get the equivalent experience and context? This will help you identify the important details.

<output> is currently underused in so many SPAs and apps, because it announces

The lack of tone, diversity of cultures, and the fact that many people using social media in English aren't native speakers make it all harder to detect irony and serious-sounding jokes online.

Please be careful and make sure your jokes don't end up feeding the disinformation machine, even if you feel it's obvious to you. In doubt, at least use the popular markers "/s" (sarcastic) or "/j" (joke) or parentheses at the end to make this clearer.

Make implicit explicit, especially in this age of disinformation and AI slop.

JAWS
NVDA
Narrator
Orca
Talkback
VoiceOVer
*accessibility is not only about screen readers

Now, everyone’s a prize exhibit in the FAANG zoo, because mastering this tangled mess is what opens their gates. Being just a CRUD monkey doesn’t feel fun anymore. If this is what “progress” looks like, I don’t want any part of it.

The technologies to build for 10 years ago dramatically improved!

As mentionned by LeHollandaisVolant, one thing the article doesn't mention is that:

• 1 the pages are more interactive
• 2 the data changes in real time

(via https://sebsauvage.net/links/?IVGhhg)

Seach content in collapsible sections.

That's great!

The inaccessibility cycle is a negative one:

1. Inaccessibility
2. Disabled people unable to participate
3. Disabled people not visible in public
4. Disabled people seen as outlier/rarity
5. "So there's little/no need to consider them."
6. The last fifth creates the first issue to "Inaccessibility", completing the cycle.

The original infographic is by Pacing Pixie, redesigned by Siuman.

À voir comment la directive 2019/882 sera appliquée

TL;DR js solutions is often better for accessibility. At least information is conveyed.

Popover will be more useful than ever.

The tradeoff is currently the <details> tag with two limitations: the element does not announce a navigation menu is exposed; clicking outside or pressing Esc does nothing.

Sauf si certaines options sont activés pour certains lecteurs d'écrans.

DateTimeFormat, NumberFormat, ListFormat, RelativeTimeFormat (!), PluralRules, DisplayNames

👍

Focus2console is a Firefox extension to display the tag and its attributes in the browser console. This can be useful in case of loss of focus (due to CSS or JS).