Aria
ARIA roles and attributes: when you need them and when you do not
ARIA is the one technology in web accessibility that lets you make a page actively worse than it was without it. A wrong role tells assistive software something untrue, and the user acts on it.
SC 2.5.3 - What does "Label in Name" mean?
Somebody using voice control looks at your page, sees a button that says “Send”, and says “click Send”. Nothing happens.
SC 4.1.2 - What does "Name, Role, Value" mean?
A screen reader user reaches a control on your page. Three things have to be true for them to use it. They have to know what it is (a button, a checkbox, a tab), what it is called (“Add to basket”), and what state it is in (pressed, expanded, checked). Success criterion 4.1.2 is the rule that guarantees all three: every interactive element exposes a name, a role and, where relevant, a value or state.
SC 4.1.3 - What does "Status Messages" mean?
You add something to your basket. The little number next to the cart icon goes from 2 to 3. Nothing else happens: no page reload, no focus change, no confirmation you have to dismiss.
What is an accessible name?
Turn on a screen reader and move to a button. You hear two or three things: “Add to basket, button”. The word “button” is the role. “Add to basket” is the accessible name.