Web checklist

Checkpoint 4.2a: Text-only pages

If accessibility cannot be accomplished in any other way, an alternative text-only page with equivalent information or functionality is provided.


Rationale

An alternative text-only page should only be used if compliance with the Web checklist cannot be achieved any other way. Alternative text-only pages are used as a last resort because they must be maintained and kept in sync with the primary page.

For additional information regarding the difficulties of maintaining alternative text-only sites, read the article from AccEase: Five Key Difficulties of Text Only Sites (links reside outside of ibm.com).

Required development and unit test techniques


To comply with this checkpoint, you must meet all of the following techniques.

  1. Links: Making the link to the text-only page easy to find.
  2. Text-only page: Keeping content on the text-only page in sync.

Note: The examples presented in the techniques are not exhaustive. They are meant to illustrate the spirit of this checkpoint.

General examples

  1. Links: Making the link to the text-only page easy to find.

    To comply with this technique, you must implement the following example.

    General example 1

    In order to keep the equivalent information and functionality for the primary Web page and the text-only page, publish both versions at the same time. Provide the link at the top of the page in a location that is easy to identify.

    Required unit tests for general development technique 1

    Manually perform the following unit test:

    • Verify that the link is keyboard accessible and the target is the appropriate text only page.
 

Copyright 2011,2013 IBM Corporation

Last updated May 1, 2011.

W3C Recommendation 11 December 2008: http://www.w3.org/TR/WCAG20/ (link resides outside of ibm.com)
Consortium for Informatics and Mathematics, Keio University), All Rights Reserved.