Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. The techniques listed only satisfy the Success Criterion if all of the WCAG 2.0 conformance requirements have been met.
Instructions: Select the situation below that matches your content. Each situation includes techniques or combinations of techniques that are known and documented to be sufficient for that situation.
G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content using a short text alternative technique listed below
G95: Providing short text alternatives that provide a brief description of the non-text content using a short text alternative technique listed below AND one of the following techniques for long description:
G92: Providing long description for non-text content that serves the same purpose and presents the same information using a long text alternative technique listed below
G82: Providing a text alternative that identifies the purpose of the non-text content using a short text alternative technique listed below
H44: Using label elements to associate text labels with form controls (HTML)
H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)
FLASH32: Using auto labeling to associate text labels with form controls (Flash)
FLASH29: Setting the label property for form components (Flash)
FLASH25: Labeling a form control by setting its accessible name (Flash)
FLASH30: Specifying accessible names for image buttons (Flash)
FLASH27: Providing button labels that describe the purpose of a button (Flash)
FLASH6: Creating accessible hotspots using invisible buttons (Flash)
SL18: Providing Text Equivalent for Nontext Silverlight Controls With AutomationProperties.Name (Silverlight)
SL26: Using LabeledBy to Associate Labels and Targets in Silverlight (Silverlight)
SL30: Using Silverlight Control Compositing and AutomationProperties.Name (Silverlight)
Providing a descriptive label using a short text alternative technique listed below
G68: Providing a descriptive labelshort text alternative that describes the purpose of live audio-only and live video-only content using a short text alternative technique listed below
G100: Providing a short text alternative which is the accepted name or a descriptive name of the non-text content using a short text alternative technique listed below
Implementing or marking the non-text content so that it will be ignored by assistive technology using one of the technology-specific techniques listed below
H36: Using alt attributes on images used as submit buttons (HTML)
H2: Combining adjacent image and text links for the same resource (HTML)
FLASH1: Setting the name property for a non-text object (Flash)
PDF1: Applying text alternatives to images with the Alt entry in PDF documents (PDF)
H24: Providing text alternatives for the area elements of image maps (HTML)
H86: Providing text alternatives for ASCII art, emoticons, and leetspeak (HTML)
FLASH28: Providing text alternatives for ASCII art, emoticons, and leetspeak in Flash (Flash)
H30: Providing link text that describes the purpose of a link for anchor elements (HTML)
FLASH5: Combining adjacent image and text buttons for the same resource (Flash)
SL5: Defining a Focusable Image Class for Silverlight (Silverlight)
Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.
Identifying informative non-text content (future link)
Keeping short descriptions short (future link)
Describing images that include text (future link)
Providing a longer description of the non-text content where only a descriptive label is required using a technology-specific technique (for an accessibility-supported content technology) for long description listed above (future link)
Providing different sizes for non-text content when it cannot have an equivalent accessible alternative (future link)
Using server-side scripts to resize images of text (future link)
Linking to textual information that provides comparable information (e.g., for a traffic Webcam, a municipality could provide a link to the text traffic report.) (future link)
Providing more than two modalities of CAPTCHAs (future link)
Providing access to a human customer service representative who can bypass CAPTCHA (future link)
Not requiring CAPTCHAs for authorized users (future link)
Writing for browsers that do not support frame (future link)
Providing alternative content for iframe (future link)
H27: Providing text and non-text alternatives for object (HTML)
Not using long descriptions for iframe (future link)
Providing redundant text links for client-side image maps (future link)
C18: Using CSS margin and padding rules instead of spacer images for layout design (CSS)
Using CSS background, :before or :after rules for decorative images instead of img elements (future link)
Displaying empty table cells (future link)
Using the ARIA presentation role to indicate elements are purely presentational (future link)
Using metadata to associate text transcriptions with a video (future link)
Using metadata to associate text transcriptions with audio-only content (future link)
EXAMPLE: Providing, in metadata, URI(s) that points to an audio description and a text transcript of a video.
EXAMPLE: Providing, in metadata, URI(s) that point to several text transcripts (English, French, Dutch) of an audio file.
The following are common mistakes that are considered failures of Success Criterion 1.1.1 by the WCAG Working Group.