- Important note: This Wiki page is edited by participants of the User Agent Accessibility Guidelines working group (UAWG). It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

1.2.1

From WAI UA Wiki
Jump to: navigation, search

Return to Tests_for_CR

Status

written 20 October 2014

Author

Jan Richards

Success Criteria

1.2.1 Support Repair by Assistive Technologies: If text alternatives for non-text content are missing or empty then both of the following are true: (Level AA)

  • The user agent doesn't attempt to repair the text alternatives by substituting text values that are also available to assistive technologies.
  • The user agent makes available metadata related to the non-text content available programmatically, but not via fields reserved for text alternatives.

Tests

Test Procedure 1

  1. Identify types of content that can have text alternatives (e.g. images).
  2. Configure the user agent so that any text alternative would be displayed (e.g. turn off the rendering of images)
  3. Open a test document that contains examples of this type of content, but lacks text alternatives (e.g. image with no alt-test or long description).
    Sample HTML test document: Image with no text alternative
    • Check that the user agent does not display a text alternative based on the file name, file type, or generic strings such as "image".

Note: For many user agents you might have to add an extension to gain this ability.

Expected Results 1

  • Check #3 is true

Test Procedure 2

  1. Identify types of content that can have text alternatives (e.g. images).
  2. Open a test document that contains examples of this type of content that also include potentially descriptive metadata (e.g. "Description"(IPTC Core), "Headline"(IPTC Core), "Keywords"(IPTC Core), "Title"(IPTC Core) - see http://www.photometadata.org/meta-resources-field-guide-to-metadata).
    Sample HTML test document: Image with metadata
    • Check (with an accessibility API viewer) that the user agent makes potentially descriptive metadata related to the non-text content available programmatically, but does not make it available via fields reserved for text alternatives (e.g. they are encoded as novel name-value pairs in the accessibility API rather than the "Name" or "Label").

Expected Results 2

  • Check #2 is true

Return to Tests_for_CR