A11y

The four principles of WCAG 2.2

• Principle 1 17 criteria

  Perceivable

  Information and UI components must be presented in ways users can perceive.

• Principle 2 20 criteria

  Operable

  User interface components and navigation must be operable.

• Principle 3 13 criteria

  Understandable

  Information and the operation of UI must be understandable.

• Principle 4 2 criteria

  Robust

  Content must be robust enough to be reliably interpreted by a wide variety of user agents, including assistive technologies.

WAI-ARIA 1.2

A specification that defines roles, states, and properties so assistive technologies can correctly interpret web content.

• Roles

  4 items

  Landmark, widget, document structure, and live region roles.

• States & Properties

  3 items

  Global, widget, and relationship attributes.

• APG Patterns

  6 items

  Implementation patterns for accordion, dialog, tabs, menu, and more.

ATAG 2.0

Guidelines covering both the accessibility of authoring tools (CMS, editors, etc.) themselves and how those tools support producing accessible content.

• Part A: Tool Accessibility

  Authoring tools themselves should be accessible to people with disabilities.

• Part B: Content Support

  Tools should support the production of accessible content.

Other standards

Related W3C/WAI specifications and tools.

• UAAG 2.0

  Accessibility for browsers and other user agents.

• WCAG 3.0

  Next-generation guideline (draft).

• WCAG-EM

  Methodology for evaluating accessibility conformance.

• ACT Rules

  Common ruleset for automated accessibility testing.

• WAI-Adapt

  Adapting UI to user needs and preferences.