Evergreen DokuWiki - accessibility:aria

acc_names

Anonymous (anonymous@undisclosed.example.com) — 2023-07-10T20:55:50+00:00

Creating Unique Accessible Names for Links and Buttons If an element’s accessible name doesn’t contain enough information, it can be supplemented with `aria-describedby` or `aria-description`. A common use case: making unique link titles without changing the visible text. Do not use visually hidden CSS

landmarks

Anonymous (anonymous@undisclosed.example.com) — 2023-07-19T16:09:48+00:00

Headings Headings (

through

) should be used to mark up the titles of each section. Section titles that are made large or bold using CSS will not have any special meaning to screen reader users. Using only one

tag per page is considered best practice. Other headings should create a logical document outline with no skipped levels. This can be tricky to achieve in components that may be inserted anywhere in a page.

live

Anonymous (anonymous@undisclosed.example.com) — 2024-01-22T15:05:59+00:00

ARIA: Dynamic States, Live Regions, and Change Announcements Any change to the user’s page context requires an audible announcement in the screen reader. ARIA dynamic properties should be used when there is a change in the page markup, but the page has not been reloaded. Form validation errors and other announcements to the user should be marked up using ARIA live regions. Search results that refresh automatically should announce their state, both in progress and after the refresh.

roles

Anonymous (anonymous@undisclosed.example.com) — 2023-07-19T15:50:51+00:00

ARIA Roles An HTML element’s role is what makes it fundamentally different from other elements. In most cases, the role is implicit in the tag;

has a role of list item, and has a role of link. An exception is the search role, which does not have a corresponding