responsibility: Code
Collection of success criterion where the responsibility falls under technical implementation and developer tasks.
2.5.3 Label in Name
The visible text of a button, link, or form field must also be part of its accessible (programmatic) name.
2.5.4 Motion Actuation
If an action can be triggered by motion (like shaking or tilting the device), it must also work without motion, and be possible to turn off motion-based input.
2.5.6 Concurrent Input Mechanisms
It must be possible to switch between input types (mouse, keyboard, touch, voice) without losing access to any functionality.
2.5.7 Dragging Movements
Actions that require dragging (like reordering) must also be possible using buttons or another method that does not require dragging.
3.1.1 Language of Page
Each page must have a <html lang=""> attribute that matches the main language of the page.
3.2.1 On Focus
No unexpected changes must happen when an element receives focus (like open a popup, move focus, submit a form).
3.2.2 On Input
No unexpected changes must happen when a field value changes (like auto-submit, reload, open new page).
3.2.4 Consistent Identification
Elements with the same function must look, behave, and be labeled the same way across pages.
3.2.5 Change on Request
Major changes (like open dialog, navigate, submit) must only happen when explicitly requested.
3.2.6 Consistent Help
Help options (like contact link, support widget) must appear in the same place across pages.