Assistive Tech Matrix
Screen reader support matrix crossing core app flows with four assistive tech pairings, labeled status cells, and an open findings list.
Screen reader support matrix crossing core app flows with four assistive tech pairings, labeled status cells, and an open findings list.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Assistive Tech Matrix is the screen reader test grid for the Acme workspace. Seven core flows sit as rows against four pairings as columns: NVDA with Chrome, JAWS with Edge, VoiceOver with Safari, and TalkBack with Chrome on Android. Every cell shows an icon plus a label for pass, partial, fail, or not run, and the header keeps a running tally. Below the grid, an open findings panel gives each partial or fail cell a row with the pairing and a concrete fix note.
Results live in one Record keyed by a pairing union, so adding a pairing is one column and the compiler flags any flow missing a result. The findings panel is the honest half: a matrix with no notes reads as done, and this one says exactly what is not.
Reach for this block on the accessibility page of a settings or release area, updated after each manual screen reader pass. Treat fail cells as ship blockers and schedule the not run cells before claiming support.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the screen reader support matrix for release sign off. Other matrix shapes:
Tip: date each manual pass; a matrix tested against last year's screen reader versions is a liability dressed up as evidence.