Of these techniques are not accessibility supported (i.e. These are WCAG sufficient techniques, and are expected to work,Īnd work in the latest versions of screen readers, but not in older versions marked with WCAG sufficient techniques - reliable in recent versions WCAG 3.1.1 text/html page with mismatching lang and xml:lang on the html element WCAG 3.1.1 Page with lang set on the html and p elements Reliability when used correctly (100% average)ĪRIA16 input type=text with aria-labelledby attribute These work in 100% of the tested screen reader / browser combinations. These are WCAG sufficient techniques, and work reliably across all tested screen readers, Other screen readers don't have enough historical data yet to plot trends. This graph shows reliability over time for WCAG techniques in NVDA, JAWS and Voiceover.

WCAG sufficient techniques - reliability trend While others only have tests for a single version (SaToGo and Dolphin). The average includes all versions, but some browser/AT combinations have tests for multiple versions (NVDA / JAWS / VoiceOver), Partial passes that only work in some interaction modes.Īn example of a partial pass is when form labels are read when tabbing, The solid area in the graph shows percentage of tests that pass missing ALT on an IMG) are not included in the reliability graph. Reliability of WCAG sufficient techniques in different screen reader / browser combinations.Įxpected failures (e.g.

WCAG sufficient techniques - reliability by user agent

Expected to fail - these tests show what happens when accessibility features are used incorrectly (marked with ).

Expected to work - these tests show support when accessibility features are used correctly.

Shows how WCAG sufficient techniques and failures behave in commonly used screen readers.

Accessibility support for Techniques for WCAG 2.0 and WCAG 2.1 Home Login

Accessibility screen reader