Playing with General Techniques for G1.1 L1 #1 - text alternatives for functional non-text content

Description/overview

Success Criterion: For all non-text content that is functional, such as graphical links or buttons, text alternatives serve the same purpose as the non-text content.

When is non-text content "functional?"

Non-text content is "functional" if the end-user can do something that will cause an action to occur (the user performs an action and the non-text content has a reaction). Functional non-text content may include hyperlinks, form fields, interactive images (image maps, flash animations?), etc. Functional non-text content does not include applets, flash animations, etc. Refer to Guideline 4.2 or Guideline 1.3 Success Criterion #y (John's proposal for a new SC) for information about making applets, scripts, and programmatic objects accessible. @@need to discuss this definition. not consensus.

When does a text alternative serve the same purpose as the non-text content?

When the function of the non-text content is perceivable to the end-user (ala Principle 1) and the end-user can interact with the non-text content ala the Success Criteria of Principle 2 - Operable.

Why did the WCAG WG word it this way?

To highlight that text alternatives must clearly indicate the action that will occur if the user activates the function.

How does this differ from the other Level 1 Success Criteria for Guideline 1.1?

There are four types of non-text content identified in Level 1 of Guideline 1.1:

@@explanation of the different types. this explanation would appear in the general guidelines for each of the other 3 success criteria as well. This is intended to help people understand when to apply which criterion.

Other questions that might help the reader properly interpret our intent@@

@@

Examples

@@explanation of examples?

Example 1: An icon as a link.

A navigation bar includes an image of a house that links to the site's home page. The text alternative says "Home" and activating the link takes the user to the home page.

What not to do (bad examples)

Techniques

@@thought it might be helpful to link to the specific techniques from within each example to help people determine which techniques apply to which instances/examples

Example 2: An icon and text as a link.

A news report about a press conferences links to an audio recording of the conference as well as a text transcript of the conference. The link to the audio recording is a common "sound" icon as well as the text, "Listen to the press conference." The text alternative for the icon is, "Audio recording."

User scenarios:

  1. Because of the combination of text and icon, someone who has a learning disability may have an easier time understanding that the link goes to an audio recording. Also, if they are using a speech synthesizer, the text alternative will help clarify the meaning of the image.
  2. Because of the text alternative that is not redundant with the text, ... e.g., a bad example would be, "Listen to the press conference" in the text as well as the text alternative b/c the screen reader user will hear it twice.

Example 3: A graphical button.

A search form includes a button featuring the image of a magnifying glass. The text alternative for the graphic says “Search.”

Example 4: A map of Asia.

A news site includes a map of countries that were struck by the tsunami of December 2004. Each country on the map is a link to information about the tsunami’s impact. Text alternatives for each selectable area give the name of the country.

Techniques

@@even though thought about including techniques up above, though some sort of "index" of all techniques and tests might be helpful here.

Associate functional graphics and buttons with text alternatives that serve the same purpose as the graphic.

Description: @@add something non-technology specific about how writing good text alternatives for functional non-text content?? or, if go with the above format, not need the same "general" techniques here?

General guidelines for writing good text alternatives for functional non-text content

Objective: Associate functional non-text content with text alternatives that serve the same purpose as the non-text content.

Applies: To every delivery unit includes non-text content that provide functionality

Benefits: Text alternatives replace non-text content for people who use screen readers, text-only displays, telephone interfaces, etc. Text alternatives also replace non-text content for people who are temporarily unable to view the screen. Thus when non-text content provides functionality, text alternatives must provide the same functionality.

HTML Techniques and Tests

HTML Techniques are informative examples of how one might satisfy the success criterion using HTML. HTML Tests provide further specifics that may be used to determine if the techniques have been applied correctly and are written at the level that might be most usable by people developing Authoring Tools or Evaluation and Repair Tools.

HTML Techniques HTML Tests
Short text alternatives for img elements ("alt-text")
  • All img elements have an alt attribute.
  • Alt text for all IMG elements is not placeholder text or user has confirmed that the Alt text is appropriate.
Short text alternatives for object elements (future)
  • object must have a text equivalent.
Text for images used as links
Image and text links side by side
  • Alt text for all img elements used as source anchors is different from the link text.
Text links for server side image maps. (deprecated)
  • Server-side image maps are not used except when image map regions cannot be defined using an available geometric shape.
Text alternatives for client-side image maps
  • All area elements have an alt attribute.
  • Alt text for all area elements contains all non decorative text in the image area.
Text and non-text alternatives for object
  • object must have a text equivalent.
  • object user interface must be accessible.
Text alternatives for submit buttons
  • All input elements with a type attribute value of "image" have an alt attribute.
  • Alt text for all input elements with a type attribute value of "image" identifies the purpose or function of the image.
  • Alt text for all input elements with a type attribute value of "image" does not use the words "submit" or "button" (English).
  • Alt text for all input elements with a type attribute value of "image" contains all non decorative text in the image.
scripts and applets (out of scope? depends on defn of non-text content)
  • script must have a noscript section. ?? (depends on baseline discussion)
  • applet must have valid alt attribute.
  • Text equivalents for applet must be updated if applet changes.
  • Text equivalents for object should be updated if object changes.??
  • User interface for script must be accessible.
  • applet user interface must be accessible.

CSS Techniques

CSS Techniques are informative examples of how one might satisfy the success criterion using CSS in combination with another technology such as HTML or SVG.

Questions/Thoughts as we draft this/comments on the process used to create