We'd like to set Google Analytics cookies to learn how people use the Knowledge Base, so we can improve it. We set them only if you accept.

Skip to main content
Digital Accessibility Knowledge Base

This section covers accessibility for websites and web applications. It's for developers, QA engineers, and designers who want to understand an issue Evinced reported, or learn how to build accessible web interfaces. Choose an entry from the navigation, or use the search.

  • Web Validations136 entriesOne entry per issue Evinced's web testing can report.
  • UI Patterns26 entriesSemantics, keyboard support, and behavior for common components.

Web Validations

Each entry explains one issue that Evinced's web accessibility testing can report: what causes it, how it affects people, and how to fix it. Entries are named after the rule that reports the issue, such as aria-allowed-attr or focus-trap, so you can go straight from a test result to its explanation.

Every entry follows the same structure, described in How to read an entry. Web entries also include:

  • Pass and fail patterns, usually with HTML code examples.
  • WCAG techniques, when the W3C documents ways to meet or fail the criterion: sufficient techniques that meet it, advisory techniques that go further, and failures that break it.
  • ACT Rules, when a W3C Accessibility Conformance Testing rule checks the same issue.
  • Try It Yourself steps for confirming the issue, for example with a screen reader, the keyboard, or your browser's developer tools.
  • Standards and regulations that include EN 301 549 clause 9 (web content), Section 508, and the Trusted Tester test process, where they apply.

UI Patterns

Accessibility guidance for common UI components, such as buttons, comboboxes, tabs, and modal dialogs. Each pattern describes the semantics, keyboard support, and behavior that make the component accessible.


Can't find what you're looking for? Write to us at knowledge@evinced.com.

Read our blog