This site has been retired. For up to date information, see handbook.gnome.org or gitlab.gnome.org.


[Home] [TitleIndex] [WordIndex

IMPORTANT: This article is being preserved for historical purposes. Current information and documentation about GNOME Accessibility can be found at: the GNOME Accessibility Project


Prev Next


Testing for Accessibility

Automated Testing

This section should describe the use of any automated accessibility compliance tools we provide.

Manual Testing

This section describes a number of tests you can perform manually on an application to test its accessibility. Passing all the tests does not necessarily imply that the application is fully accessible, but if the application fails any of thes tests, then further work may need to be done to improve that aspect of its accessibility.

Keyboard Navigation

The following keyboard operations should be tested. Do not use the mouse in any part of this test.

Graphical Elements

Test the application using a screen reader and confirm that:

Visual Focus Indicator

Fonts and Text

Colour and Contrast

Audio

There should be an option in the application to show audio alerts visually.

Test that the audio is working correctly by enabling sound in the GNOME Control Center and then perform the following actions:

Animation

Verify that an option is available to stop animation and that it is working as designed.

Turn the animation off. Confirm that all information is still conveyed correctly.

Keyboard Focus

Documentation

Test ASCII text documentation with a screen reader to confirm that it is clear and precise and can be read by assistive technologies.

Test HTML applications using a web browser and screen reader to confirm that the documentation is accessible to assistive technologies.

Note: There are web accessibility guidelines available at http://www.w3.org/TR/WAI-WEBCONTENT/.

Confirm the following information is included in the documentation:


Home Prev Next


2024-10-23 10:57