Skip to main content

ATAG Part A Keyboard Accessibility

ATAG 2.0 Part A addresses the accessibility of authoring-tool user interfaces for authors with disabilities. OpenKeyNav provides reusable keyboard-operation mechanisms for three criteria in web-based content management systems, learning management systems, rich-text and visual editors, site builders, and other tools used to create web content.

OpenKeyNav
Provides direct target selection, configured movement, navigation, documented mode exits, and application command hooks.
You
Map those mechanisms to authoring functions, supply semantic editor controls and feedback, and verify every required workflow.

ResultAuthors can complete the required authoring tasks through a keyboard interface.

Authoring tools in scope​

ATAG uses authoring tool for software that creates or modifies web content for other people. Relevant web-based examples include:

  • content management and learning management systems;
  • rich-text, source-code, page-layout, and visual editors;
  • website and no-code builders;
  • collaborative publishing and social-content interfaces; and
  • tools that generate web content from templates or structured inputs.

Identify the authoring views, controls, dialogs, property panels, content canvases, preview surfaces, and publishing workflows that authors operate. Map Click Mode to detected actions, Move Mode to endpoint workflows, and application commands to authoring-specific operations.

Keyboard access minimum​

ATAG A.3.1.1 Keyboard Access (Minimum) requires all authoring-tool functionality to be operable through a keyboard interface, apart from functions whose underlying purpose depends on a continuous movement path.

OpenKeyNav supplies several keyboard paths:

  • Click Mode gives authors direct keyboard access to detected visible targets.
  • Move Mode lets an author choose configured source and destination endpoints for rearranging, assigning, sorting, or placement workflows.
  • Navigation commands provide faster routes through headings, scroll regions, and the structure exposed by the page.
  • Application-supplied commands and callbacks connect authoring-specific operations to the tool's content model and state.

Establish coverage by inventorying every authoring outcome, including creating, selecting, formatting, moving, saving, previewing, publishing, undoing, and recovering from validation errors. Confirm a keyboard path for each outcome in every relevant application state.

Connect these paths to the semantics, focus behavior, accessible names, roles, states, and event handling of the authoring tool. Preserve native editor and composite-widget keyboard conventions while adding OpenKeyNav routes.

No keyboard traps​

ATAG A.3.1.2 No Keyboard Traps requires authors to be able to move keyboard focus away from components. When an exit requires more than standard navigation keys, the tool must advise authors how to leave.

OpenKeyNav provides documented exit commands for its temporary interaction modes and Structural Navigation. Verify keyboard exits throughout the complete authoring tool, including:

  • editing canvases and embedded editors;
  • toolbars, menus, trees, grids, and property panels;
  • dialogs, popovers, previews, and full-screen modes;
  • embedded frames and shadow-root components; and
  • validation, upload, and publishing workflows.

Keep exit instructions available in the interface and documentation. Test the complete focus route into, through, and away from each authoring component.

Efficient keyboard access​

ATAG A.3.1.3 Efficient Keyboard Access calls for mechanisms that are more efficient than sequential keyboard access alone.

OpenKeyNav's direct labels jump authors from the current context to a detected action. Heading, scroll-region, and Structural Navigation commands shorten routes across long or densely structured authoring interfaces. Applications can bind authoring-specific commands to make frequent editor functions directly reachable.

Validate the efficiency gain with representative authoring tasks and keyboard users. Confirm that added commands reduce navigation effort while remaining discoverable, predictable, and compatible with the editor's native key handling.

Configurable and presented commands​

Two Level AAA criteria provide additional implementation guidance:

  • For authoring tools with keyboard commands, A.3.1.5 Customize Keyboard Access calls for command customization. OpenKeyNav lets applications configure its commands to align with the host tool's key map.
  • A.3.1.6 Present Keyboard Commands requires authors to be able to determine the commands associated with interface components. Present OpenKeyNav's configured commands through its shortcut interface, and document the complete command set and any context-dependent behavior alongside it.

Check command choices against browser, operating-system, editor, and assistive-technology conventions. Honor the established commands of text fields and composite widgets.

Navigation within the content being edited​

ATAG A.3.4.1 Navigate By Structure concerns selecting and moving between markup elements in the web content being edited. Use OpenKeyNav Structural Navigation for the surrounding authoring interface. For navigation within the content being edited, connect application-supplied OpenKeyNav commands to the tool's content model, selection model, and structural-editing operations. Verify those workflows in every supported editing view.

Verification checklist​

  1. Inventory every function available in each authoring role and view.
  2. Complete representative create, edit, move, validate, save, preview, and publish workflows with a keyboard.
  3. Confirm that Click Mode detects every target assigned to it in each application state.
  4. Verify each configured movement source, destination, completion callback, and status message.
  5. Enter and leave every mode, editor, dialog, panel, frame, and composite widget from the keyboard.
  6. Confirm that direct commands improve common authoring tasks beyond sequential focus traversal.
  7. Check accessible names, roles, values, states, focus order, visible focus, and programmatic status feedback.
  8. Test supported browsers and assistive technologies, including native editor and widget commands.
  9. Conduct task-based evaluation with disabled authors who use keyboards and keyboard interfaces.
  10. Record the OpenKeyNav routes and application techniques used for each applicable ATAG criterion.