Page Functionality with Keyboard
It would seem logical that if the log-in page is inaccessible one should stop checking any further, but because this was an evaluation of interactive user participatory web services and sites, it was felt important to check other aspects of navigation and functionality within the site. (W3C WCAG 2.0 2.1, W3C WCAG 2.0 2.4, W3C WCAG 2.0 1.1 and W3C WCAG 2.0 3.2).
Testing Techniques
These techniques may be used to perform the test.
Method
Manual tabbing. FAE functionality checks, WeBBIE and Thunder for read order or NVDA screen reader.
Criteria for this Test
 |
Critical features on the page require mouse use. |
|---|---|
 |
Full navigation but inaccessible controls for accessing embedded content - media players etc. |
 |
Non-critical features on the page require mouse use. Maybe browser dependent i.e. works with one browser but not another. |
 |
Fully navigable within all browsers. |
