Accessibility Testing Scenarios

The following are some accessibility testing scenarios, to illustrate the types of testing needed. Currently they only include "in-browser" testing that is mostly covered in Testing/Requirements, but they should be completed to include all accessibility testing scenarios.

Manual ("self-describing") Tests

The following types of tests are executed manually:

web content (which could include images and multimedia with or without alternatives, or structures such as tables, lists, headings, forms, etc) are presented to the user, and the user is asked to verify that what is presented matches a pre-defined (reference) description

web content (which could include embedded objects or other elements) is presented to the user, and the user is asked if they can navigate through the content using keyboard only

web content is presented to the user, and the user is asked to verify that the browser chrome provides certain functionality, information, or follows certain behavior

Semi-Automated Tests

The following types of tests are executed manually but with some automation support:

font size or zoom level are changed automatically to pre-defined values by the test harness, and the user is asked to verify that the content is still readable and operable

default styles are automatically overridden by the test harness (to animate user style sheets), and the user is asked to verify that the content is still readable and operable

scripting events are triggered by the test harness, and the user is asked to verify that the browser chrome provides certain functionality, information, or follows certain behavior

scripting events are triggered by the test harness, and the user is asked to verify that the corresponding API events are triggered on the operating system (using an additional API tool)

the user does an action such as typing, clicking, or submitting a form, and the events triggered are automatically checked through the test harness scripts

Fully-Automated Tests

The following types of tests could be executed automatically:

scripting events are triggered by the test harness, and the resulting DOM, text, or screen shots (?) are automatically compared against a pre-defined reference