[DRAFT] WCAG 2.0 Quick Reference

Sufficient Techniques for 1.1.1 (for the technologies you checked above)

Situation A: If a short description can serve the same purpose and present the same information as the non-text content:

1. 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

Situation B: If a short description can not serve the same purpose and present the same information as the non-text content (e.g. a chart or diagram):

1. 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

   • G74: Providing a long description in text near the non-text content, with a reference to the location of the long description in the short description

   • G73: Providing a long description in another location with a link to it that is immediately adjacent to the non-text content

Situation C: If non-text content is a control or accepts user input:

1. G82: Providing a text alternative that identifies the purpose of the non-text content using a short text alternative technique listed below

2. Using HTML form controls and links (future link)

3. H44: Using label elements to associate text labels with form controls (HTML)

4. H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)

5. Using (X)HTML according to spec (future link)

Situation D: If non-text content is multimedia; live audio-only or live video-only content; a test or exercise that must use a particular sense; or primarily intended to create a specific sensory experience:

1. Providing a descriptive label using a short text alternative technique listed below

2. G68: Providing a descriptive label that describes the purpose of live audio-only and live video-only content using a short text alternative technique listed below

3. G100: Providing the accepted name or a descriptive name of the non-text content using a short text alternative technique listed below

Situation E: If non-text content is a CAPTCHA:

1. G143: Providing a text alternative that describes the purpose of the CAPTCHA AND G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality

Situation F: If the non-text content should be ignored by assistive technology:

1. 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

   • H67: Using null alt text and no title attribute on img elements for images that AT should ignore (HTML)

   • C9: Using CSS to include decorative images (CSS)

Providing short text alternatives in HTML

• H36: Using alt attributes on images used as submit buttons (HTML)

• H37: Using alt attributes on img elements (HTML)

• H35: Providing text alternatives on applet elements (HTML)

• H53: Using the body of the object element (HTML)

• H52: Using the body of the applet element (HTML)

• H24: Providing text alternatives for the area elements of image maps (HTML)

• Providing text alternatives for strings where look-alike glyphs are used in place of letters (e.g. Leetspeak) (future link)

• Providing text alternatives for ASCII art (future link)

Providing long text alternatives in HTML

• H45: Using longdesc (HTML)

• H53: Using the body of the object element (HTML)

• H52: Using the body of the applet element (HTML)

Common Failures Identified by the Working Group for 1.1.1

• F30: Failure of SC 1.1.1 due to using text alternatives that are not alternatives (e.g. filenames or placeholder text)

• F20: Failure of SC 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur

• F3: Failure of SC 1.1.1 due to using CSS to include images that convey important information

• F39: Failure of SC 1.1.1 due to providing a text alternative that is not null. (e.g. alt="spacer" or alt="image") for images that should be ignored by assistive technology

• F38: Failure of SC 1.1.1 due to omitting the alt-attribute for non-text content used for decorative purposes only in HTML

• F71: Failure of SC 1.1.1 due to using text look-alikes to represent text without providing a text alternative

• F72: Failure of SC 1.1.1 due to using ASCII art without providing a text alternative

• F65: Failure of SC 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type "image"

• F67: Failure of SC 1.1.1 due to providing long description for non-text content that does not serve the same purpose or does not present the same information

General Techniques for Informative Non-Text Content (Advisory)

• 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)

General Techniques for Live Non-Text Content (Advisory)

• 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 a transcript of a live audio only presentation after the fact (future link)

HTML Techniques (Advisory)

• H46: Using noembed with embed (HTML)

• Writing for browsers that do not support frame (future link)

• Providing alternative content for iframe (future link)

• Providing text and non-text alternatives for object (future link)

• Not using long descriptions for iframe (future link)

• Providing redundant text links for client-side image maps (future link)

CSS Techniques (Advisory)

• Using CSS margin and padding rules instead of spacer images (future link)

• Using CSS background, :before or :after rules for decorative images instead of img elements (future link)

• Displaying empty table cells (future link)

Sufficient Techniques for 1.3.1 (for the technologies you checked above)

Situation A: The technology provides semantic structure to make information and relationships conveyed through presentation programmatically determinable:

1. G115: Using semantic elements to mark up structure AND H49: Using semantic markup to mark emphasized or special text (HTML)

2. G117: Using text to convey information that is conveyed by variations in presentation of text

3. Separating information and structure from presentation to enable modification of presentation without altering content (future link)

4. Making information and relationships conveyed through presentation programmatically determinable using the following techniques:

   • G138: Using semantic markup whenever color cues are used

   • H51: Using table markup to present tabular information (HTML)

   • H39: Using caption elements to associate data table captions with data tables (HTML)

   • H73: Using the summary attribute of the table element to give an overview of data tables (HTML)

   • H63: Using the scope attribute to associate header cells and data cells in data tables (HTML)

   • H43: Using id and headers attributes to associate data cells with header cells in data tables (HTML)

   • 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)

   • H71: Providing a description for groups of form controls using fieldset and legend elements (HTML)

   • H48: Using ol, ul and dl for lists (HTML)

   • H42: Using h1-h6 to identify headings (HTML)

   • SCR21: Using functions of the Document Object Model (DOM) to add content to a page (SCRIPT)

Situation B: The technology in use does NOT provide the semantic structure to make the information and relationships conveyed through presentation programmatically determinable:

1. G117: Using text to convey information that is conveyed by variations in presentation of text

2. Making information and relationships conveyed through presentation programmatically determinable or available in text using the following techniques:

   • T1: Using standard text formatting conventions for paragraphs (TXT)

   • T2: Using standard text formatting conventions for lists (TXT)

   • T3: Using standard text formatting conventions for headings (TXT)

   • Presenting tabular information in plain text (future link)

Common Failures Identified by the Working Group for 1.3.1

• F2: Failure of SC 1.3.1 due to using CSS to create variations in presentation of text that conveys information without also using the appropriate markup or text

• F17: Failure of SC 1.3.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML

• F33: Failure of SC 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content

• F34: Failure of SC 1.3.2 and 1.3.2 due to using white space characters to format tables in plain text content

• F42: Failure of SC 1.3.1 due to using scripting events to emulate links

• F43: Failure of SC 1.3.1 due to using structural markup in a way that does not represent relationships in the content

• F46: Failure of SC 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables

• F48: Failure of SC 1.3.1 due to using the pre element to markup tabular information

• F62: Failure of SC 1.3.1 due to insufficient information in DOM to determine specific relationships in XML

• F64: Failure of SC 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text

• F68: Failure of SC 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable

Advisory Techniques for 1.3.1

• Using CSS styles to change or enhance the presentation of structure (future link)

• Using CSS rather than tables for page layout (future link)

• Positioning labels to maximize predictability of relationships

• SCR25: Using Dynamic Web Content Accessibility to programmatically identify form fields as required (SCRIPT)

• ARIA1: Using Accessible Rich Internet Application describedby property to provide a descriptive, programmatically determined label (ARIA)

• Providing labels for all form controls that do not have implicit labels (future link)

Sufficient Techniques for 1.3.2 (for the technologies you checked above)

1. G57: Ordering the content in a meaningful sequence for all the content in the Web page

2. Marking sequences in the content as meaningful using one of the following techniques AND G57: Ordering the content in a meaningful sequence for those sequences

   • H34: Using a Unicode right-to-left mark (RLM) or left-to-right mark (LRM) to mix text direction inline (HTML)

   • H56: Using the dir attribute on an inline element to resolve problems with nested directional runs (HTML)

   • C8: Using CSS letter-spacing to control spacing within a word (CSS)

   • C6: Positioning content based on structural markup (CSS)

Common Failures Identified by the Working Group for 1.3.2

• F34: Failure of SC 1.3.2 and 1.3.2 due to using white space characters to format tables in plain text content

• F33: Failure of SC 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content

• F32: Failure of SC 1.3.2 due to using white space characters to control spacing within a word

• F49: Failure of SC 1.3.2 due to using an HTML layout table that does not make sense when linearized

• F1: Failure of SC 1.3.2 due to changing the meaning of content by positioning information with CSS

Advisory Techniques for 1.3.2

• Using left-justified text for languages that are written left to right and right-justified text for languages that are written right-to-left (future link)

• Using appropriate justification for languages that are written right-to-left (future link)

• Providing a link to linearized rendering (future link)

• Providing a style switcher between style sheets that affect presentation order (future link)

Sufficient Techniques for 1.3.3 (for the technologies you checked above)

1. G96: Providing textual identification of items that otherwise rely only on shape and/or position to be understood

Common Failures Identified by the Working Group for 1.3.3

• F14: Failure of SC 1.3.3 due to identifying content only by its shape or location

• F26: Failure of SC 1.3.3 due to using a graphical symbol alone to convey information

Advisory Techniques for 1.3.3

• Using an image with a text alternative for graphical symbols instead of a Unicode font glyph with the desired graphical appearance but different meaning (future link)

Sufficient Techniques for 1.4.1 (for the technologies you checked above)

Situation A: If the color of particular words is used to indicate information:

1. G14: Ensuring that color encoded information is also available in text

2. G122: Including a text cue whenever color cues are used

3. Ensuring that when text color is used to convey information, the text style is visually differentiated without color (future link)

Situation B: If color is used within an image to convey information:

1. G111: Using color and pattern

2. G14: Ensuring that color encoded information is also available in text

Common Failures Identified by the Working Group for 1.4.1

• F13: Failure of SC 1.4.1 due to having a text alternative that does not include information that is conveyed by color in the image

• F73: Failure of SC 1.4.1 due to creating links that are not visually evident without color vision

General Techniques

• Conveying information redundantly using color (future link)

Client-side Scripting Techniques

• Changing the background color or border of the element with focus (future link)

Sufficient Techniques for 1.4.2 (for the technologies you checked above)

1. G60: Playing a sound that turns off automatically within three seconds

2. Playing sounds only on user request (future link)

3. Providing a control near the top of the Web page that turns off sounds that play automatically (future link)

4. Providing a user interface control to pause or stop multimedia (future link)

Common Failures Identified by the Working Group for 1.4.2

• F23: Failure of SC 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off

Advisory Techniques for 1.4.2

• Providing a sitewide preference to turn off audio in addition to providing a control near the top of the Web page that turns off sounds that play automatically (future link)

Sufficient Techniques for 1.4.3 (for the technologies you checked above)

Situation A: text is less than 18 point if not bold and less than 14 point if bold

1. G18: Ensuring that a contrast ratio of at least 5:1 exists between text and background behind the text

2. H21: Not specifying background color, not specifying text color, and not using CSS that changes those defaults (HTML)

Situation B: text is as least 18 point if not bold and at least 14 point if bold

1. G145: Ensuring that a contrast ratio of at least 3:1 exists between text and background behind the text

2. H21: Not specifying background color, not specifying text color, and not using CSS that changes those defaults (HTML)

Common Failures Identified by the Working Group for 1.4.3

• F24: Failure of SC 1.4.3 and 1.4.5 due to specifying foreground colors without specifying background colors or vice versa

Advisory Techniques for 1.4.3

• Using a higher contrast value for text that is over a patterned background (future link)

• Creating foreground and background contrast (future link)

• Using a light pastel background rather than a white background behind black text (future link)

• Using unicode text and style sheets instead of images of text (future link)

• Using a higher contrast values for lines in diagrams (future link)

• Using greater contrast level for red-black text/background combinations

• Using colors that are composed predominantly of mid spectral components for the light and spectral extremes (blue and red wavelengths) for the dark

Sufficient Techniques for 1.4.4 (for the technologies you checked above)

1. G142: Using a technology that has commonly-available user agents that support zoom

2. Ensuring that text containers resize when the text resizes AND using measurements that are relative to other measurements in the content by using one or more of the following techniques:

   • Techniques for relative measurements

     • C12: Using percent for font sizes (CSS)

     • C13: Using named font sizes (CSS)

     • C14: Using em units for font sizes (CSS)

   • Techniques for text container resizing

     • Calculating size and position in a way that scales with text size (future link) (SCRIPT)

     • G146: Using liquid layout

3. Providing controls on the Web page that incrementally change the size of the text (future link)

4. Providing options within the content to switch between layouts that use a variety of font sizes (future link)

Common Failures Identified by the Working Group for 1.4.4

• F69: Failure of SC 1.4.4 and 1.4.7 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured

Advisory Techniques for 1.4.4

• Providing large fonts by default (future link)

• Avoiding the use of text in raster images (future link)

• Using page-percent for container sizes (future link)

• Avoiding scaling font sizes smaller than the user-agent default (future link)

  Note: The author won't actually know the font size, but should avoid percentage scaling that results in less than 100%

• Avoiding justified text (future link)

• Providing sufficient inter-line and inter-column spacing (future link)

Sufficient Techniques for 1.4.5 (for the technologies you checked above)

Situation A: text is less than 18 point if not bold and less than 14 point if bold

1. G17: Ensuring that a contrast ratio of at least 7:1 exists between text and background behind the text

2. H21: Not specifying background color, not specifying text color, and not using CSS that changes those defaults (HTML)

Situation B: text is as least 18 point if not bold and at least 14 point if bold

1. G18: Ensuring that a contrast ratio of at least 5:1 exists between text and background behind the text

2. H21: Not specifying background color, not specifying text color, and not using CSS that changes those defaults (HTML)

Common Failures Identified by the Working Group for 1.4.5

• F24: Failure of SC 1.4.3 and 1.4.5 due to specifying foreground colors without specifying background colors or vice versa

Advisory Techniques for 1.4.5

• Using a higher contrast value for text that is over a patterned background (future link)

• Using unicode text and style sheets instead of images of text (future link)

• Using a light pastel background rather than a white background behind black text (future link)

• Using a higher contrast values for lines in diagrams (future link)

• Using greater contrast level for red-black text/background combinations

• Using colors that are composed predominantly of mid spectral components for the light and spectral extremes (blue and red wavelengths) for the dark

Sufficient Techniques for 1.4.6 (for the technologies you checked above)

1. G56: Mixing audio files so that non-speech sounds are at least 20 decibels lower than the speech audio content

2. Not including audio content (future link)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 1.4.6

• Providing a way for users to adjust auditory levels of foreground and background sound independently. (future link)

Sufficient Techniques for 1.4.7 (for the technologies you checked above)

1. G146: Using liquid layout AND ensuring that text containers resize when the text resizes AND using measurements that are relative to other measurements in the content by using one or more of the following techniques:

   • Techniques for relative measurements

     • C12: Using percent for font sizes (CSS)

     • C13: Using named font sizes (CSS)

     • C14: Using em units for font sizes (CSS)

   • Techniques for text container resizing

     • Calculating size and position in a way that scales with text size (future link) (SCRIPT)

2. Providing options within the content to switch between layouts that use a variety of font sizes (future link)

3. Using single-column layouts (future link)

Common Failures Identified by the Working Group for 1.4.7

• F69: Failure of SC 1.4.4 and 1.4.7 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured

Advisory Techniques for 1.4.7

• Providing large fonts by default (future link)

• Avoiding the use of text in raster images (future link)

• Using page-percent for container sizes (future link)

• Avoiding scaling font sizes smaller than the user-agent default (future link)

  Note: The author won't actually know the font size, but should avoid percentage scaling that results in less than 100%

• Avoiding justified text (future link)

• Providing sufficient inter-line and inter-column spacing (future link)

Sufficient Techniques for 2.1.1 (for the technologies you checked above)

1. G21: Ensuring that users are not trapped in content AND G90: Providing keyboard-triggered event handlers using one of the following techniques:

   • SCR20: Using both keyboard and other device-specific functions (SCRIPT)

   • Making JavaScript actions keyboard accessible (future link)

   • Creating device-independent image effects (future link)

Common Failures Identified by the Working Group for 2.1.1

• F54: Failure of SC 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function

• F10: Failure of SC 2.1.1 and Conformance Requirement 6 due to combining multiple content formats in a way that traps users inside one format type

• F55: Failure of SC 2.1.1 and 3.2.1 due to using script to remove focus when focus is received

Advisory Techniques for 2.1.1

• Providing keyboard access to important links and form controls (future link)

• Using unique letter combinations to begin each item of a list (future link)

• Choosing the most abstract event handler (future link)

• Using the onactivate event (future link)

• Avoiding use of common user-agent keyboard commands for other purposes (future link)

Sufficient Techniques for 2.1.2 (for the technologies you checked above)

1. No additional techniques exist for this Success Criterion. Follow techniques for Success Criterion 2.1.1. If that is not possible because there is a requirement for analog, time-dependent input, then it is not possible to meet this Level 3 Success Criterion.

Sufficient Techniques for 2.2.1 (for the technologies you checked above)

Situation A: If there are session time limits:

1. G133: Providing a checkbox on the first page of a multipart form that allows users to ask for longer session time limit or no session time limit

Situation B: If a time limit is controlled by a script on the page:

1. Providing a way for the user to turn the time limit off (future link)

2. Providing the user with a means to set the time limit to 10 times the default time limit (future link)

3. SCR16: Providing a script that warns the user a time limit is about to expire (SCRIPT) AND SCR1: Allowing the user to extend the default time limit (SCRIPT)

Common Failures Identified by the Working Group for 2.2.1

• F40: Failure of SC 2.2.1 due to using meta redirect with a time limit

• F41: Failure of SC 2.2.1, 2.2.5, and 3.2.5 due to using meta refresh with a time-out

• F58: Failure of SC 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out

Advisory Techniques for 2.2.1

• Using a script to poll the server and notify a user if a time limit is present (future link)

Sufficient Techniques for 2.2.2 (for the technologies you checked above)

1. G11: Creating content that blinks for less than 3 seconds

2. Using a technology to include blinking content that can be turned off via the user agent (future link)

3. Using a control in the Web page that stops blinking content (future link) using one of the following techniques:

   • Setting animated gif images to stop blinking after n cycles (within 3 seconds) (future link)

   • Providing a link, button, or other mechanism that reloads the page without the blinking content (future link)

   • SCR22: Using scripts to control blinking and stop it in three seconds or less (SCRIPT)

Common Failures Identified by the Working Group for 2.2.2

• F47: Failure of SC 2.2.2 due to using the blink element

• F4: Failure of SC 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than three seconds

• F50: Failure of SC 2.2.2 due to a script that causes a blink effect without a mechanism to stop the blinking at 3 seconds or less

• F7: Failure of SC 2.2.2 due to an object or applet, such as Java or Flash, that has blinking content without a mechanism to pause the content that blinks for more than three seconds

Advisory Techniques for 2.2.2

• Providing a mechanism to stop all content that blinks within a Web page (future link)

• Providing the user with a means to stop moving content even if it stops automatically within 3 seconds (future link)

Sufficient Techniques for 2.2.3 (for the technologies you checked above)

1. G4: Allowing the content to be paused and restarted from where it was stopped

2. Using script to scroll content, and providing a mechanism to pause it (future link)

3. Allowing purely decorative content to be stopped (future link)

Common Failures Identified by the Working Group for 2.2.3

• F16: Failure of SC 2.2.3 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Sufficient Techniques for 2.2.4 (for the technologies you checked above)

1. G5: Allowing users to complete an activity without any time limit

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Sufficient Techniques for 2.2.5 (for the technologies you checked above)

1. G75: Providing a mechanism to postpone any updating of content

2. Allowing users to request updates instead of automatically updating content (future link)

3. SCR14: Using scripts to make nonessential alerts optional (SCRIPT)

Common Failures Identified by the Working Group for 2.2.5

• F40: Failure of SC 2.2.1 due to using meta redirect with a time limit

• F41: Failure of SC 2.2.1, 2.2.5, and 3.2.5 due to using meta refresh with a time-out

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Sufficient Techniques for 2.2.6 (for the technologies you checked above)

1. Providing options to continue without loss of data using one of the following technqiues:

   • G105: Saving data so that it can be used after a user re-authenticates

   • Encoding user data as hidden data in re-authorization page (future link)

Common Failures Identified by the Working Group for 2.2.6

• F12: Failure of SC 2.2.6 due to having a session time limit without a mechanism for saving user's input and re-establishing that information upon re-authentication

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Sufficient Techniques for 2.3.1 (for the technologies you checked above)

Situation A: Web content server over the Internet for general viewing

1. Using all possible 341 x 256 pixel rectangles on 1024 x 768 pixel display to represent a 10 degree field of view at normal viewing distance AND G15: Ensuring that content does not violate the general flash threshold or red flash threshold

   Note: There is a tool that is available to carry out this test.

2. G19: Ensuring that no component of the content flashes more than three times in any 1-second period

Situation B: Web content designed for a specific large-scale display where size and viewing distance is known

1. Using actual viewing distance to calculate a 10 degree field of view in pixels AND G15: Ensuring that content does not violate the general flash threshold or red flash threshold

   Note: There is a tool that is available to carry out this test.

2. G19: Ensuring that no component of the content flashes more than three times in any 1-second period

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 2.3.1

• Reducing contrast for any flashing content (future link)

• Avoiding fully saturated reds for any flashing content (future link)

• Reducing the number of flashes even if they do not violate thresholds (future link)

• Providing a mechanism to suppress any flashing content before it begins (future link)

Sufficient Techniques for 2.3.2 (for the technologies you checked above)

1. G19: Ensuring that no component of the content flashes more than three times in any 1-second period

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 2.3.2

• Reducing contrast for any flashing content (future link)

• Avoiding fully saturated reds for any flashing content (future link)

• Reducing the number of flashes even if they don't violate thresholds (future link)

Sufficient Techniques for 2.4.1 (for the technologies you checked above)

1. Creating links to skip blocks of repeated material using one of the following techniques:

   • G1: Adding a link at the top of each page that goes directly to the main content area

   • G123: Adding a link at the beginning of a block of repeated content to go to the end of the block

   • G124: Adding links at the top of the page to each area of the content

2. Grouping blocks of repeated material in a way that can be skipped, using one of the following techniques:

   • HTML Techniques for creating links to skip blocks

     • Creating HTML links to skip blocks of content (future link)

   • HTML Techniques for grouping blocks of repeated material

     • H69: Providing heading elements at the beginning of each section of content (HTML)

     • H50: Using structural elements to group links (HTML) .

     • H70: Using frame elements to group blocks of repeated material (HTML) AND H64: Using the title attribute of the frame element (HTML) .

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 2.4.1

• Providing keyboard access to important links and form controls (future link)

• Providing skip links to enhance page navigation (future link)

• Providing access keys (future link)

• C6: Positioning content based on structural markup (CSS)

Sufficient Techniques for 2.4.2 (for the technologies you checked above)

1. G88: Providing descriptive titles for Web pages AND associating a title with a Web page using one of the following techniques:

   • H25: Providing a title using the title element (HTML)

Common Failures Identified by the Working Group for 2.4.2

• F25: Failure of SC 2.4.2 due to the title of a Web page not identifying the contents

Advisory Techniques for 2.4.2

• G127: Identifying a Web page's relationship to a larger collection of Web pages using a technology-specific technique

• Identifying the subject of the Web page (future link)

• ARIA1: Using Accessible Rich Internet Application describedby property to provide a descriptive, programmatically determined label (ARIA)

• Providing a meaningful name for identifying frames (future link)

Sufficient Techniques for 2.4.3 (for the technologies you checked above)

1. G59: Placing the interactive elements in an order that follows sequences and relationships within the content

2. Giving focus to elements in an order that follows sequences and relationships within the content using one of the following techniques:

   • H4: Creating a logical tab order through links, form controls, and objects (HTML)

Common Failures Identified by the Working Group for 2.4.3

• F44: Failure of SC 2.4.4 due to using tabindex to create a tab order that does not follow relationships and sequences in the content

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Sufficient Techniques for 2.4.4 (for the technologies you checked above)

1. G91: Providing link text that describes the purpose of a link

   • H30: Providing link text that describes the purpose of a link for anchor elements (HTML)

   • H24: Providing text alternatives for the area elements of image maps (HTML)

2. G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence

3. Providing a supplemental description of the purpose of a link using one of the following techniques:

   • H33: Supplementing link text with the title attribute (HTML)

   • C7: Using CSS to hide a portion of the link text (CSS)

4. Identifying the purpose of a link using link text combined with programmatically determined link context using one of the following techniques:

   • H77: Identifying the purpose of a link using link text combined with its enclosing list item (HTML)

   • H78: Identifying the purpose of a link using link text combined with its enclosing paragraph (HTML)

   • H79: Identifying the purpose of a link using link text combined with its enclosing table cell and associated table headings (HTML)

Common Failures Identified by the Working Group for 2.4.4

• F63: Failure of SC 2.4.6 due to providing link context only in content that is not related to the link

Advisory Techniques for 2.4.4

• H2: Combining adjacent image and text links for the same resource (HTML)

• ARIA1: Using Accessible Rich Internet Application describedby property to provide a descriptive, programmatically determined label (ARIA)

Sufficient Techniques for 2.4.5 (for the technologies you checked above)

1. Using two or more of the following techniques:

   • G125: Providing links to navigate to related Web pages

   • G64: Providing a Table of Contents

   • G63: Providing a site map

   • Providing a search engine to help users find content (future link)

   • G126: Providing a list of links to all other Web pages

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 2.4.5

• H59: Using the link element and navigation tools (HTML)

• Including information about presentation modes in tables of contents and concept maps (future link)

Sufficient Techniques for 2.4.6 (for the technologies you checked above)

1. G130: Providing descriptive headings

2. G131: Providing descriptive labels

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 2.4.6

• Using unique section headings in a Web Page (future link)

• Starting section headings with unique information (future link)

Sufficient Techniques for 2.4.7 (for the technologies you checked above)

1. G65: Providing a breadcrumb trail

2. G63: Providing a site map

3. G128: Indicating current location within navigation bars

4. G127: Identifying a Web page's relationship to a larger collection of Web pages using one of the following techniques:

   • H59: Using the link element and navigation tools (HTML)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 2.4.7

• Providing a link to the home page or main page (future link)

Sufficient Techniques for 2.4.8 (for the technologies you checked above)

1. G91: Providing link text that describes the purpose of a link using one of the following techniques:

   • H30: Providing link text that describes the purpose of a link for anchor elements (HTML)

   • H24: Providing text alternatives for the area elements of image maps (HTML)

2. Providing a supplemental description of the purpose of a link using one of the following techniques:

   • C7: Using CSS to hide a portion of the link text (CSS)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 2.4.8

• H2: Combining adjacent image and text links for the same resource (HTML)

• H33: Supplementing link text with the title attribute (HTML)

Sufficient Techniques for 2.4.9 (for the technologies you checked above)

1. G141: Organizing a page using headings

2. H64: Using the title attribute of the frame element (HTML)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 2.4.9

• Using the 'live' property to mark live regions (future link) (ARIA)

Sufficient Techniques for 3.1.1 (for the technologies you checked above)

1. Identifying default human language(s) using one of the following techniques:

   • H57: Using language attributes on the html element (HTML)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.1.1

• Specifying the default language in the HTTP header (future link)

Additional HTML Techniques (Advisory)

• using http or the Content-Language meta tag for metadata (future link)

Sufficient Techniques for 3.1.2 (for the technologies you checked above)

1. Identifying changes in human languages using one of the following techniques:

   • H58: Using the lang language attributes to identify changes in the human language (HTML)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.1.2

• Making text that is not in the default human language of the Web page visually distinct (future link)

• Giving the names of any languages used in foreign passages or phrases (future link)

Additional HTML Techniques (Advisory)

• Marking individual words, especially when they are links to versions in other languages (Deutsch, Français, Nederlands, Castellano, etc.) (future link)

Sufficient Techniques for 3.1.3 (for the technologies you checked above)

Situation A: If the word or phrase has a unique meaning within the Web page:

1. G101: Providing the definition of a word or phrase used in an unusual or restricted way for the first occurrence of the word or phrase in a Web page using one of the following techniques:

   • G55: Linking to definitions

     • H40: Using definition lists (HTML)

     • H60: Using the link element to link to a glossary (HTML)

   • G112: Using inline definitions

     • H54: Using the dfn element to identify the defining instance of a word (HTML)

2. G101: Providing the definition of a word or phrase used in an unusual or restricted way for each occurrence of the word or phrase in a Web page using one of the following techniques:

   • G55: Linking to definitions

     • H40: Using definition lists (HTML)

     • H60: Using the link element to link to a glossary (HTML)

   • G62: Providing a glossary

   • Providing a function to search an on-line dictionary (future link)

   • Using a dictionary cascade (future link)

Situation B: If the word or phrase means different things within the same Web page:

1. G101: Providing the definition of a word or phrase used in an unusual or restricted way for each occurrence of the word or phrase in a Web page using one of the following techniques:

   • G55: Linking to definitions

     • H40: Using definition lists (HTML)

     • H60: Using the link element to link to a glossary (HTML)

   • G112: Using inline definitions

     • H54: Using the dfn element to identify the defining instance of a word (HTML)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.1.3

• Using the title attribute to provide explanations of words or phrases (future link)

• Using markup and visual formatting to help users recognize words that have special meaning (future link)

• Providing a voice-enabled dictionary search so that users who have difficulty typing or spelling can speak the word whose definition they need (future link)

• Providing a sign language dictionary to help users who are deaf find the necessary definitions (future link)

• Providing a mechanism for finding definitions for all words in text content (future link)

• Providing a mechanism to determine the meaning of each word or phrase in text content (future link)

• Avoiding unusual foreign words (future link)

Sufficient Techniques for 3.1.4 (for the technologies you checked above)

Situation A: If the abbreviation has only one meaning within the Web page:

1. G102: Providing the expansion or explanation of an abbreviation for the first occurrence of the abbreviation in a Web page using one of the following techniques:

   • G97: Providing the abbreviation immediately following the expanded form

   • G55: Linking to definitions

   • H28: Providing definitions for abbreviations by using the abbr and acronym elements (HTML)

2. G102: Providing the expansion or explanation of an abbreviation for all occurrences of the abbreviation in a Web page using one of the following techniques:

   • G55: Linking to definitions

   • G62: Providing a glossary

     • H60: Using the link element to link to a glossary (HTML)

   • Providing a function to search an on-line dictionary (future link)

   • Using a dictionary cascade (future link)

   • H28: Providing definitions for abbreviations by using the abbr and acronym elements (HTML)

Situation B: If the abbreviation means different things within the same Web page:

1. G102: Providing the expansion or explanation of an abbreviation for all occurrences of abbreviations in a Web page using one of the following techniques:

   • G55: Linking to definitions

   • H28: Providing definitions for abbreviations by using the abbr and acronym elements (HTML)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.1.4

• Using the title attribute to provide explanations of words or phrases (future link)

• Using unique abbreviations in a Web page (future link)

• Using visual formatting to help users recognize abbreviations (future link)

• Providing access to a talking dictionary to support users who might have difficulty decoding written definitions (future link)

• Providing a voice-enabled dictionary search so that users who have difficulty typing or spelling can speak the word whose definition they need (future link)

Sufficient Techniques for 3.1.5 (for the technologies you checked above)

1. G86: Providing a text summary that requires reading ability less advanced than the upper secondary education level

2. G103: Providing visual illustrations of complex ideas, events, and processes

3. G79: Providing a spoken version of the text

4. Making the text easier to read (future link)

5. Providing sign language versions of information, ideas, and processes that must be understood in order to use the content (future link)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Additional technology-independent techniques

• Providing text for navigational and landing pages that requires reading ability that is less advanced than the lower secondary education level (future link)

• Providing text for interior pages that requires reading ability at the lower secondary education level (future link)

• Including content summaries in metadata (future link)

• Using the clearest and simplest language appropriate for the content (future link)

Additional technology-specific techniques

• Using the Dublin Core accessibility element to associate text content with text, graphical, or spoken supplements (future link)

• Using RDF to associate supplements with primary content (future link)

• Providing a clear representational image on the site's home page (future link)

• Making metadata viewable by humans (future link)

Sufficient Techniques for 3.1.6 (for the technologies you checked above)

1. Providing the pronunciation immediately following the word (future link)

2. Linking to pronunciations (future link)

3. G62: Providing a glossary that includes pronunciation information for words that have a unique pronunciation in the content and have meaning that depends on pronunciation

4. Providing pronunciation information using a technology-specific technique below

   • H62: Using the ruby element (HTML) (XHTML 1.1)

   • Using standard diacritical marks that can be turned off (future link)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.1.6

• Providing pronunciations in a sound file, so that users can listen to the pronunciations of the word (future link)

• Providing a mechanism for finding pronunciations for all foreign words in text content (future link)

• Providing a mechanism to determine the pronunciations of each word or phrase in text content (future link)

Sufficient Techniques for 3.2.1 (for the technologies you checked above)

1. G107: Using "activate" rather than "focus" as a trigger for changes of context

Common Failures Identified by the Working Group for 3.2.1

• F52: Failure of SC 3.2.1 due to opening a new window as soon as a new page is loaded without prior warning

• F55: Failure of SC 2.1.1 and 3.2.1 due to using script to remove focus when focus is received

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Sufficient Techniques for 3.2.2 (for the technologies you checked above)

1. G80: Providing a submit button to initiate a change of context using a technology-specific technique listed below

2. G13: Describing what will happen before a change to a form control is made

   • H32: Providing submit buttons (HTML)

   • Using a button with a select element to perform an action (future link)

   • Hiding and showing content based on a select element change (future link)

   • Hiding and showing content based on a radio element change (future link)

Common Failures Identified by the Working Group for 3.2.2

• F36: Failure of SC 3.2.2 due to automatically submitting a form and presenting new content without prior warning when the last field in the form is given a value

• F37: Failure of SC 3.2.2 due to launching a new window without prior warning when the status of a radio button, check box or select list is changed

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Sufficient Techniques for 3.2.3 (for the technologies you checked above)

1. G61: Presenting repeated components in the same relative order each time they appear

Common Failures Identified by the Working Group for 3.2.3

• F66: Failure of SC 3.2.3 due to presenting navigation links in a different relative order on different pages

Advisory Techniques for 3.2.3

• Using templates to ensure consistency across multiple Web pages (future link)

Additional Technology-Specific Techniques (Advisory)

CSS Techniques

• Creating layout, positioning, layering, and alignment (future link)

Sufficient Techniques for 3.2.4 (for the technologies you checked above)

1. Using consistent labels, names, and text alternatives for content that has the same functionality.

   • 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)

Common Failures Identified by the Working Group for 3.2.4

• F31: Failure of SC 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages

Advisory Techniques for 3.2.4

• Ensuring that the text alternative conveys the function of the component and what will happen when the user activates it (future link)

• Using the same non-text content for a given function whenever possible (future link)

Sufficient Techniques for 3.2.5 (for the technologies you checked above)

Situation A: If the Web page allows automatic updates:

1. G76: Providing a mechanism to request an update of the content instead of updating automatically

Situation B: If automatic redirects are possible:

1. SVR1: Implementing automatic redirects on the server side instead of on the client side (SERVER)

2. G110: Using an instant client-side redirect using one of the following techniques:

   • H76: Using meta refresh to create an instant client-side redirect (HTML)

Situation C: If the Web page uses pop-up windows:

1. Including pop-up windows using one of the following techniques:

   • Using the target attribute to open a new window (future link)

   • SCR24: Using script to open a new window on user request (SCRIPT)

1. SCR19: Using an onchange event on a select element without causing a change of context (SCRIPT)

Common Failures Identified by the Working Group for 3.2.5

• F60: Failure of SC 3.2.5 due to launching a new window when a user enters text into an input field

• F61: Failure of SC 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content

• F9: Failure of SC 3.2.5 due to changing the context when the user removes focus from a form element

• F22: Failure of SC 3.2.5 due to opening windows that are not requested by the user

• F41: Failure of SC 2.2.1, 2.2.5, and 3.2.5 due to using meta refresh with a time-out

HTML Techniques (Advisory)

Open new windows by:

• Using the target attribute instead of scripts (future link), indicating that the link may open in a new window, or

• Providing normal hyperlinks without the target attribute (future link), because many user agents allow users to open links in another window or tab.

Sufficient Techniques for 3.3.1 (for the technologies you checked above)

Situation A: If a form contains fields for which information from the user is mandatory.

1. G83: Providing text descriptions to identify required fields that were not completed

Situation B: If information provided by the user is required to be in a specific data format or of certain values.

1. G85: Providing a text description when user input falls outside the required format or values

2. SCR18: Providing client-side validation and alert (SCRIPT)

3. Providing client-side validation and adding error text via the DOM (future link)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.3.1

• G139: Creating a mechanism that allows users to jump to errors

• Validating form submissions on the server (future link)

• Re-displaying a form with a summary of errors (future link)

• Providing error notification as the user enters information (future link)

• Assisting the user in making corrections by providing links to each error (future link)

• Highlighting or visually emphasizing errors where they occur (future link)

• Supplementing text with non-text content when reporting errors (future link)

Sufficient Techniques for 3.3.2 (for the technologies you checked above)

Situation A: If a mandatory field contains no information:

1. G83: Providing text descriptions to identify required fields that were not completed

Situation B: If information for a field is required to be in a specific data format:

1. G85: Providing a text description when user input falls outside the required format or values

2. Providing links to suggested correction text "close to" form fields, or providing the suggested correction text itself directly on the Web page "next to" form fields (future link)

3. SCR18: Providing client-side validation and alert (SCRIPT)

4. Providing client-side validation and adding error text via the DOM (future link)

Situation C: Information provided by the user is required to be one of a limited set of values:

1. G84: Providing a text description when the user provides information that is not in the list of allowed values

2. Providing links to suggested correction text "close to" form fields, or providing the suggested correction text itself directly on the Web page "next to" form fields (future link)

3. SCR18: Providing client-side validation and alert (SCRIPT)

4. Providing client-side validation and adding error text via the DOM (future link)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.3.2

• G139: Creating a mechanism that allows users to jump to errors

• Making error messages easy to understand and distinguishable from other text in the Web page (future link)

• Validating form submissions on the server (future link)

• When mandatory information has not been provided, including descriptions or examples of correct information in addition to identifying the field as mandatory (future link)

• Repeating and emphasizing suggestions for correcting each input error in the context of its form field (future link)

• Providing a way for the user to skip from each item in a list of suggestions to its corresponding form field (future link)

• Providing additional contextual help for the form field requiring change (future link)

Techniques for providing suggestions to the user

• Providing a text description that contains information about the number of input errors, suggestions for corrections to each item, and instructions on how to proceed (future link)

• Providing a text description that contains suggestions for correction as the first item (or one of the first items) of content, or emphasizing this information in the content (future link)

• Displaying errors and suggestions in the context of the original form (for example, re-displaying a form where input errors and suggestions for correction are highlighted and displayed in the context of the original form) (future link)

HTML Techniques

• Providing "correct examples" for data and data formats as initial text in mandatory form fields (future link)

• Providing links to suggested correction text "close to" form fields, or providing the suggested correction text itself directly on the Web page "next to" form fields (future link)

Client-Side Scripting Techniques

• SCR18: Providing client-side validation and alert (SCRIPT)

• Providing client-side validation and adding error text via the DOM (future link)

• Calling a function from the submit action of a form to perform client side validation (future link)

ARIA Techniques

• ARIA2: Identifying required fields with the "required" property (ARIA)

• ARIA3: Identifying valid range information with the "valuemin" and "valuemax" properties (ARIA)

Sufficient Techniques for 3.3.3 (for the technologies you checked above)

Situation A: If an application causes a legal transaction to occur, such as making a purchase or submitting an income tax return:

1. Providing a period of time after submission of the form when the order can be updated or cancelled by the user (future link)

2. G98: Providing the ability for the user to review and correct answers before submitting

Situation B: If an action causes information to be deleted:

1. G99: Providing the ability to recover deleted information

2. Providing a dialog to the user which requires confirmation before information is deleted (future link)

3. Requiring a user to select a confirmation checkbox before submitting an action that causes information to be deleted (future link)

Situation C: If the Web page includes a testing application:

1. G98: Providing the ability for the user to review and correct answers before submitting

2. Asking for confirmation before final submission (future link)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.3.3

• Informing the user what irreversible action is about to happen (future link)

• SCR18: Providing client-side validation and alert (SCRIPT)

• Placing focus in the field containing the error (future link)

• Avoiding use of the same words or letter combinations to begin each item of a drop-down list (future link)

Sufficient Techniques for 3.3.4 (for the technologies you checked above)

1. G131: Providing descriptive labels AND one of the following:

   • G89: Providing expected data format and example

   • Providing text instructions at the beginning of a form or set of fields that describes the necessary input (future link)

   • Positioning labels to maximize predictability of relationships (future link)

   • Providing linear form design / grouping similar items (future link)

   • G83: Providing text descriptions to identify required fields that were not completed

2. H44: Using label elements to associate text labels with form controls (HTML)

3. H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)

4. H71: Providing a description for groups of form controls using fieldset and legend elements (HTML)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.3.4

• G13: Describing what will happen before a change to a form control is made

• ARIA1: Using Accessible Rich Internet Application describedby property to provide a descriptive, programmatically determined label (ARIA)

• SCR25: Using Dynamic Web Content Accessibility to programmatically identify form fields as required (SCRIPT)

Sufficient Techniques for 3.3.5 (for the technologies you checked above)

Situation A: If a form requires text input:

1. G71: Providing a help link on every Web page

2. Using scripts to provide context-sensitive bubble help (future link)

3. Providing help by an assistant in the Web page (future link)

4. Providing spell checking and suggestions for text input if applicable to the language (future link)

5. Using the title attribute to provide context-sensitive help

6. Providing instructions at the top of a form (future link)

Situation B: If a form requires text input in an expected data format:

1. G89: Providing expected data format and example

2. Providing instructions at the top of a form (future link)

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Advisory Techniques for 3.3.5

• Checking byte of character and auto-converting to expected byte for text input if applicable (future link)

Sufficient Techniques for 3.3.6 (for the technologies you checked above)

1. Following the sufficient techniques for Success Criterion 3.3.3 for all forms that require the user to submit information.

Sufficient Techniques for 4.1.1 (for the technologies you checked above)

1. G134: Validating Web pages

2. Fully conforming to specifications (future link)

3. Ensuring that Web pages can be parsed by using one of the following techniques:

   • H74: Ensuring that all id attribute values are unique for the document AND that opening and closing tags are used according to specification (HTML)

   • H75: Ensuring that all id attribute values are unique for the document AND that the Web page is well-formed (HTML)

Common Failures Identified by the Working Group for 4.1.1

• F70: Failure of SC 4.1.1 due to incorrect use of start and end tags or attribute markup

(No failures/advisory techniques currently documented) (@@ add XSLT to differentiate these)

Sufficient Techniques for 4.1.2 (for the technologies you checked above)

Situation A: If using a standard user interface component in a markup language (e.g. HTML):

1. G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes using technology-specific techniques below:

   • Using HTML form controls and links (future link)

   • H44: Using label elements to associate text labels with form controls (HTML)

   • H64: Using the title attribute of the frame element (HTML)

   • H65: Using the title attribute to identify form controls when the label element cannot be used (HTML)

   • Using (X)HTML according to spec (future link)

   • Using XHTML role, state, and value attributes if repurposing static elements as interactive user interface components (future link)

   • SCR21: Using functions of the Document Object Model (DOM) to add content to a page (SCRIPT)

   • Using DOM Level 2 events (future link)

Situation B: If using script or code to re-purpose a standard user interface component in a markup language:

1. Exposing the names and roles, allowing user-settable properties to be directly set, and providing notification of changes using one of the following techniques:

   • SCR21: Using functions of the Document Object Model (DOM) to add content to a page (SCRIPT)

   • Using DOM Level 2 events (future link)

Situation C: If using a standard user interface component in a programming technology:

1. G135: Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes

Situation D: If creating your own user interface component in a programming language:

1. G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes

Common Failures Identified by the Working Group for 4.1.2

• F59: Failure of SC 4.1.2 due to using script to make div or span a user interface control in HTML

  Note: This failure may be solved in the future using DHTML roadmap techniques.

• F15: Failure of SC 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely

• F20: Failure of SC 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur

• F68: Failure of SC 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable

Advisory Techniques for 4.1.2

• Providing labels for all form controls that do not have implicit labels (future link)