Testing keyboard accessibility
Check whether every interactive element can be reached, identified, and operated with a keyboard in a logical sequence.
Testing methods
Use these reference guides to learn how to perform specific accessibility testing techniques.
Foundations
Broad techniques that commonly form the beginning of an accessibility review.
Testing visual accessibility
Review contrast, color-dependent information, text readability, and visible interaction states systematically.
Testing with automated tools
Run a reproducible accessibility scan, verify every result in context, and identify what still requires manual testing.
Display and adaptation
Test how content responds to presentation settings, input conditions, and user preferences.
Testing text spacing and user overrides
Apply the complete text-spacing condition and check whether content and functionality remain available.
Testing forced colors and high contrast
Check whether information, controls, states, and focus remain perceivable when a browser applies forced colors.
Testing motion, animation, and flashing
Check whether moving and animated content can be controlled and whether a page respects reduced-motion preferences safely.
Testing mobile touch and orientation
Check target size and spacing, orientation support, gesture alternatives, and pointer cancellation on touch interfaces.
Testing zoom and reflow
Check whether content and functionality remain available when text is enlarged and the page reflows into a narrow CSS viewport.
Content and structure
Test whether information is represented and communicated accessibly.
Testing media accessibility
Check prerecorded captions, transcripts, visual description, autoplay, and essential player operation across media alternatives.
Testing page structure and links with a screen reader
Check whether a page title, landmarks, and headings communicate useful structure and links make sense outside their surrounding text.
Testing data tables with a screen reader
Check whether a data table exposes a useful name, dimensions, navigation, and row-and-column relationships.
Testing image alternative text
Decide what each image contributes in context and test whether its alternative communicates the same relevant purpose.
Testing icons and SVGs with a screen reader
Determine whether meaningful graphics have useful names and decorative graphics remain silent.
Testing language changes with a screen reader
Check whether content in another language triggers appropriate pronunciation without redundant language markup.
Interaction and tasks
Test controls and workflows that users must operate or complete.
Testing controls with a screen reader
Check whether common controls expose useful names, roles, states, values, keyboard behavior, and changes after interaction.
Testing forms and validation
Check whether people can understand, complete, correct, and successfully submit a form.
Testing status messages and live updates
Check whether dynamic updates are communicated at the right time and priority without unnecessarily moving focus or interrupting a task.
Testing time limits and interruptions
Check whether people have enough time, receive useful warnings, can extend a session, and can recover their work after interruption.
Testing authentication and verification
Check whether people can sign in and complete verification without unsupported memory, transcription, or recovery barriers.
Testing modal dialogs
Test modal names, initial focus, keyboard containment, background inertness, closing behavior, and focus restoration.