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).

"Introduction to Web Accessibility" is a free course designed for people of all roles and all experience levels, so regardless of your background, there's something you can learn here.

Les conférences ont certaines barrières d'entrées.

Structurally speaking, then, a paragraph is a group of related inline elements. In this case, inline words, but it could also include any of the items described as “phrasing content"

<hgroup> issu the tag to use for heading with multiple inline content.

A classic image with text in it looks like this: "[image]".

Meanwhile, alt text convey the information: "[description of image including the text]"

Global Accessibility Awareness Day Continues!

How accessibility (screen readers especially) with Linux fails

WCAG 3.0 rebrands to W3C Accessibility guidelines: it will cover applications, tools, connected devices and emerging interfaces like voice interaction and extended reality. It moves from a model of compliance toward a model of effectiveness.

It does not more comply or not comply anymore, but provide a scale to measure each outcome. The conformance will be summarized to Bronze (similar to AA), Silver (broader coverage, higher scores and usability validation from people with disabilities) and Gold. Teams can claim conformance for specific scopes (checkout flow, mobile app or a specific feature).

Tab and enter is the minimum.
There is more than 500 shortcuts.

Shortlist:

• focus indicators
• logical tab order
• skip navigation links
• keyboard-accessible interactive elements
• test them

Ordered list for logical sequences:

• steps in a recipe or instructions
• ranking or priority lists
• chronological events

Unordered collections when the order of items doesn't matter:

• navigation menus
• list of features or benefits
• related links

Description lists <dl>to associate terms with their definitions or descriptions. Examples include:

• Glossaries
• FAQ
• Metadata or key-value pairs

When to avoid lists:

• product cards
• tabular data

A collection of composable, unstyled UI primitives for building accessible web applications.

I help make the Fediverse more inclusive by generating alt-text descriptions for images. Let me assist you!

Special fonts are often not accessible