Focus: HTML, ARIA, keyboard navigation, interactive elements, and error handling.
Responsibilities
- Implement semantic HTML structure that reflects the intended design hierarchy.
- Make sure all interactive components function fully with keyboard-only input.
- Provide ARIA attributes only when necessary and ensure they’re valid.
- Check that error messages, alerts, and status updates are announced to screen readers.
- Test responsive behavior and reflow across various screen sizes and zoom levels.
- Test keyboard-only navigation and ensure there are no traps or dead ends.
- Confirm meaningful focus order and visible focus indicators.
- Validate that interactive components (dialogs, menus, modals) announce correctly.
- Log defects with clear descriptions and remediation steps.

Relevant WCAG 2.1 new success criteria
The success criteria states that content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
Note: Examples where a particular display orientation may be essential are a bank check, a piano application, slides for a projector or television, or virtual reality content where content is not necessarily restricted to landscape or portrait display orientation.
Key takeaway: Content must not lock orientation. CSS, JavaScript, or embedded viewer settings must allow both orientations to function fully.
Sufficient techniques
How it applies to development
- Utilize the show/hide controls to allow access to content in different orientations.
- Use CSS to set the orientation to allow both landscape and portrait modes.
- If content does not rotate, check for a control within the user face to change the orientation.
Orientation failure and success

The success criteria states that the purpose of each input field collecting information about the user can be programmatically determined when:
- The input field serves a purpose identified in the Input Purposes for user interface components section; and
- The content is implemented using technologies with support for identifying the expected meaning for form input data.
Key takeaway: Input fields must expose standardized purposes (autocomplete types) that browsers and assistive technology can understand. Developers must use semantic, standards-based autocomplete attributes.
Sufficient techniques
How it applies to development
- Apply proper autocomplete attributes such as:
- autocomplete=”name”
- autocomplete=”email”
- autocomplete=”address-line1”
- Avoid custom widgets that mask fields or block user agents from detecting field purpose.
Tools
- Test using Dev Tools within your browser (right-click and select inspect).
The success criteria states that content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:
- Vertical scrolling content at a width equivalent to 320 CSS pixels;
- Horizontal scrolling content at a height equivalent to 256 CSS pixels.
Except for parts of the content which require two-dimensional layout for usage or meaning.
Key takeaway: Developers must build responsive layouts via CSS with no fixed-width containers to provide optimized layouts for different screen sizes, zoom levels, etc.
Sufficient techniques
- Using media queries and grid CSS to reflow columns
- Using CSS Flexbox to reflow content
- Allowing for reflow with long URLs and strings of text
- Using CSS width, max-width and flexbox to fit labels and inputs
- Calculating size and position in a way that scales with text size
How it applies to development
- Ensure charts, tables, panels, and controls adapt via CSS grid, flexbox, or responsive breakpoints.
- Avoid fixed pixel widths for chart canvases or dashboard panels.
- Make legends and filters wrap when space is constrained.
- Use scalable containers and percentage-based dimensions.
Reflow failure (horizontal scrolling required)

Reflow success (no horizontal scrolling)

Tools
- Manually test by using browser zoom to 400%.
The success criteria states that the visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
- User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
- Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
Key takeaway: Non-text elements (such as icons, charts, graphs, diagrams, data points) must be visually recognizable. Poor contrast can make datasets unreadable for low-vision users.
Sufficient techniques
- For user interface components:
- For graphical content:
How it applies to development
- When selecting color palettes, ensure that each data series meets the 3:1 contrast ratio relative to its background and adjacent elements.
Icon color contrast failure and success
![]()
Tools
Exceptions
- If a graphic contains text that is embedded or overlayed and conveys the same information. An example would be the labels and values on a bar graph.
- The graphic does not convey any meaningful information and is for decorative purposes only.
- The information is available in another form.
- The graphic is part of a logo or brand name.
The success criteria states that in content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:
- Line height (line spacing) to at least 1.5 times the font size;
- Spacing following paragraphs to at least 2 times the font size;
- Letter spacing (tracking) to at least 0.12 times the font size;
- Word spacing to at least 0.16 times the font size.
Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.
Key takeaway: Developers must use flexible CSS that accommodates increased spacing without breaking the layout.
Sufficient techniques
How it applies to development
- Avoid using absolute positioned components that cannot resize.
- Avoid CSS that forces fixed line heights.
- Test increased spacing by injecting test CSS:
- line-height: 1.5
- letter-spacing: 0.12em
- paragraph-spacing: 2em
Text spacing failure

Text spacing success

The success criteria states where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:
- Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
- Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
- Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.
Key takeaway: When additional content appears on hover or focus, it must remain visible when the pointer is over it, not disappear immediately when moving to the tooltip, and be dismissible.
Sufficient techniques
How it applies to development
- How to test that the user can properly interact with the information on hover:
- ARIA: Using role=”tooltip”
- CSS: Using hover and focus pseudo classes
Content on hover failure

Content on hover success

Tools
- Manually test the component with keyboard navigation (Tab / Shift+Tab)
The success criteria states that if a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
- Turn off: A mechanism is available to turn the shortcut off;
- Remap: A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);
- Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.
Key takeaway: Developers must prevent accidental triggers by users with alternative input methods and no single key shortcuts.
Sufficient techniques
How it applies to development
- Make sure character-only shortcut keys can be turned off/modified using one or more modifier keys.
- Scope shortcuts to focused elements only.
Tools
- If information on shortcut keys is not available, check code for shortcut keys or manually search for them using the keyboard for every character.
The success criteria states that all functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.
Note: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).
Key takeaway: Developers must provide alternative event handlers for charts, maps, dashboards that involve actions requiring complex gestures.
Sufficient techniques
- Providing controls to achieve the same result as path based or multipoint gestures
- Providing single point activation for a control slider
How it applies to development
- Most data visualizations can be accomplished with simple gestures. There are some instances that may require complex actions like pinch, rotate, or two-finger pan that must have a simple pointer alternative.
- Example: A map requires holding down the Control key to make multiple selections using a mouse.
- A solution could be making a pre-set group of points that can be selected with a filter, such as a group of places on a map.
The success criteria states that for functionality that can be operated using a single pointer, at least one of the following is true:
- No Down-Event: The down-event of the pointer is not used to execute any part of the function;
- Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
- Up Reversal: The up-event reverses any outcome of the preceding down-event;
- Essential: Completing the function on the down-event is essential.
Functions that emulate a keyboard or numeric keypad key press are considered essential.
This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).
Key takeaway: Touch interactions must not trigger actions on touch-down, actions must be cancellable.
Sufficient techniques
- Ensuring that drag-and-drop actions can be cancelled
- Using native controls to ensure functionality is triggered on the up-event
How it applies to development
- When using JavaScript, don’t use on mouse down; it will override onclick.
- Make pointer cancellation consistent.
The success criteria states that for user interface components with labels that include text or images of text, the name contains the text that is presented visually.
Note: A best practice is to have the text of the label at the start of the name.
Key takeaway: The visible text label must match the accessible name used by assistive technologies. This includes buttons, toggles, legends, filters, and map tools.
Sufficient techniques
- Including the text of the visible label as part of the accessible name
- Matching the accessible name to the visible label
How it applies to development
- Legends must match their spoken names for people relying on voice recognition software to access and use controls such as buttons, drop-down menus, check boxes, and filters.
- Example: If the visible text on a drop-down menu says “Filter,” the accessible name should also be “Filter” and not “Refine Results.”
- Correct HTML:
- <label for=”filters”>Filters</label>
- <select id=”filters” name=”filters”>
- Incorrect HTML:
- <label for=”filters”>Filters</label>
- <select id=”filters” name=”Refine Results”>
- Correct HTML:
- The accessible name is what assistive technology uses to identify the control for the user. All interactive elements must have a name.
Tools
- Manually test the accessible names match the visible names using a screen reader or inspect the HTML (right-click, inspect).
The success criteria states that functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:
- Supported Interface:The motion is used to operate functionality through an accessibility supported interface;
- Essential:The motion is essential for the function and doing so would invalidate the activity.
Key takeaway: If your application uses device motion for interactions (such as shaking, tilting, rotating, etc.), users must have non-motion alternatives and be able to turn off motion controls.
Sufficient techniques
How it applies to development
- Do not rely on motion gestures for essential actions.
- Always provide standard UI alternatives for the same action:
- Buttons
- Keyboard commands
- Tap/click triggers
- Disable motion detection when the user turns on “Reduce Motion” system settings.
- Provide a toggle or preference setting to disable motion interactions.
- Avoid accidental triggers from unintended movement (e.g., slight shaking).
- Ensure motion events do not override assistive technologies or keyboard focus.
The success criteria states that in content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
Key takeaway: Screen reader users must be notified when meaningful changes happen in dashboards, charts, or map views without losing their keyboard focus.
Sufficient techniques
- If a status message advises on the success or results of an action, or state of an application:
- If a status message conveys a suggestion or warning on the existence of an error:
- Using ARIA role=alert or Live Regions to Identify Errors in combination with any of the following techniques:
- Providing text descriptions to identify required fields that were not completed
- Providing a text description when the user provides information that is not in the list of allowed values
- Providing a text description when user input falls outside the required format or values
- Providing suggested correction text
- Providing spell checking and suggestions for text input
- Using ARIA role=alert or Live Regions to Identify Errors in combination with any of the following techniques:
- If a status message conveys information on the progress of a process:
How it applies to development
- Use aria-live regions for status messages.
- Do not force focus shifts (e.g., moving focus to a dialog unless necessary).
- For dynamic dashboards, announce data refreshes, applied filters, and errors or empty dataset states.
- Use short, meaningful status messages — not paragraphs of text.
- Example: If a login attempt has invalid credentials the status message would be “The username or password is not correct. Please try again.”
Successful status messages

