RAWeb 1: Testing methodology

This document has been drawn up as part of the resources to accompany the introduction of version 1 of the Web Accessibility Assessment Framework (RAWeb).

It is intended for anyone wishing to check that web content complies with the RAWeb. It is a test methodology that documents the steps involved in checking whether or not a RAWeb criterion is met. This methodology is therefore to be used in addition to the RAWeb technical framework and cannot be used on its own. It does not replace a thorough reading of the technical framework, nor does it replace a RAWeb training.

For each of the tests of a criterion, there is a corresponding test procedure. The implementation of this procedure may sometimes require the use of specific tools, otherwise a browser is sufficient to perform most of the tests. A list of tools is also provided to assist in carrying out the tests. They have been selected both because they are frequently used by experts in the field and because they make it easier to find certain results.

The test methodology is now available for each test on the criteria and tests page.

Tools

The most useful tool is the code inspector available in every browser. It makes it easy to find the elements and attributes required for an accessibility test. Nowadays, development tools also offer features for accessing the properties of the accessibility tree exposed by the browser. However, this information does not replace the need for technical assistance when a criterion or test requires it.

The assistive technologies listed in the chosen test environment constitute a second set of essential tools (see the section Testing environment). They are required to ensure that accessible content (alternatives to images, link headings, table titles, etc.) is rendered correctly, particularly in cases where examining the code alone would not suffice.

Other tools are available to help search for content elements. They are often presented as browser extensions and can be used to explore one or more aspects of an accessibility test.

The following toolbars are browser extensions that make it easier to visually locate certain elements in a document:

In addition to the simple toolbar, other tools provide a complete analysis of the document by visually highlighting accessibility errors on the page or, conversely, beneficial elements. Filters are then often used to display only some of these aspects. This is what Wave offers, a solution available both online (http://wave.webaim.org) and as a browser extension (https://wave.webaim.org/extension/).

Although it is no longer necessary to check the validity of the source code, it can be useful to use the HTML validator to search for anomalies. Validation of the source code of an HTML document uses the W3C online validator (https://validator.w3.org/nu/). Note that to validate the source code generated by the browser, use the "Text input" option in the "Check by" listbox and copy the HTML source available from the browser's code inspector into the multiline input box. Browser extensions are also available, but you need to be careful, as the validation algorithms of these extensions are not necessarily up to date with the W3C validator and the results obtained may therefore be different.

Various tools are available for checking colour contrasts:

A very useful extension is available for checking the document tree structure and headings hierarchy:

Various tools can be used to analyse office files, depending on the file format:

Finally, an old but still useful program for assessing the potential of certain web content to cause epileptic seizures: PEAT (Photosensitive Epilepsy Analysis Tool) for Windows.