Common Failures (all Common Failures on one page)

From Mobile Accessibility Task Force

Main_Page > Draft WCAG Techniques > Failure Techniques

These WCAG Techniques are currently under review by the Mobile Accessibility Task Force. Any changes marked are a draft and are NOT approved by the Mobile Accessibility Task Force and the WCAG Working Group

Instructions to the Task Force

  1. Select a technique to evaluate.
  2. Read the full technique in the WCAG Techniques and the Understanding Documentation
  3. Determine if the technique is applicable to Mobile Accessibility.
    • If the technique is not applicable to mobile accessibility (please use this category sparingly – beware mobile stereotypes):
      • Edit the list below by pasting this string after the technique name: 
        <span style="color:#808080;"> (not applicable)  </span>
      • Add your name and date at the end of the same line.
      • Save this page.
    • If the technique is applicable but does not require any changes:
      • Edit the list below and paste this string after the technique name: 
        <span style="color:green;"> (applicable as is)  </span>
      • Add your name and date at the end of the same line.
      • Save this page.
    • If the technique requires changes:
      • Edit the list below by adding double brackets [[ ]] around the number of the technique to make a new wiki page. (Don't include the colon inside the brackets.)
      • Paste this string after the technique name: 
        <span style="color:#D90000;"> (requires changes)</span>
      • Add your name and date at the end of the same line.
      • Save this page.
      • Open the new page by clicking on the red link.
      • Copy the technique link from the WCAG Techniques page. The link should have the date 20120103 in it.
      • Copy and paste the list below at the top of the page, and enter your comments.
      • Save the new page.
'''Notes on the WCAG Technique Sections'''
* Applicability: PLACEHOLDER
* Description: PLACEHOLDER 
* Examples: PLACEHOLDER 
* Related: PLACEHOLDER
* Tests: PLACEHOLDER 
- NAME and DATE

Failure Techniques

  • F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS: Jon Avila April-01-14 (applicable as is to mobile web; may require equivalent for mobile apps)
  • F2: Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text: Jon Avila (applicable as is to mobile web; may require equivalent for mobile apps)
  • F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information: Jon Avila April-1-2014 (applicable as is to mobile web)
  • F4: Failure of Success Criterion 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than five seconds: Jon Avila April-1-2014 (applicable as is to mobile web)
  • F7: Failure of Success Criterion 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 five seconds: Jon Avila April-1-2014 (not applicable to mobile as these technologies are not supported)
  • F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialogue or important sound effects: Jon Avila April-1-2014 (applicable as is)
  • F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element: Jon Avila April-1-2014 (applicable as is)
  • F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type : Jon Avila April-1-2014 (Not sure -- conceptually this could happen with web views, etc.)
  • F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism for saving user's input and re-establishing that information upon re-authentication: Jon Avila April-1-2014 (applicable as is)
  • F13: Failure of Success Criterion 1.1.1 and 1.4.1 due to having a text alternative that does not include information that is conveyed by color differences in the image: Jon Avila April-1-2014 (applicable as is)
  • F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location : Jon Avila April-1-2014 (applicable as is)
  • F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely : Jon Avila April-1-2014 (applicable as is)
  • F16: Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content : Jon Avila April-1-2014 (applicable as is to mobile web; may require equivalent for mobile apps)
  • F17: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML : Jon Avila April-1-2014 (applicable as is to mobile web; may require equivalent for mobile apps)
  • F19: Failure of Conformance Requirement 1 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web page : Jon Avila April-1-2014 (requires wording change to generalize beyond web pages)
  • F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur: Jon Avila April-1-2014 (applicable as is)
  • F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user Kathy Wahlbin May-05-14 (applicable as is to mobile web; may require equivalent for mobile apps)
  • F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off Kathy Wahlbin May-05-14 (applicable as is)
  • F24: Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa Kathy Wahlbin May-05-14 (applicable as is)
  • F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents Kathy Wahlbin May-05-14 (applicable as is for mobile web; requires changes for mobile apps)
  • F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information Kathy Wahlbin May-05-14 (applicable as is for mobile web; requires changes for mobile apps)
  • F30: Failure of Success Criterion 1.1.1 and 1.2.1 due to using text alternatives that are not alternatives (e.g., filenames or placeholder text) (applicable as is for mobile web; requires changes for mobile apps)
  • F31: Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages (applicable as is for mobile web; requires changes for mobile apps)
  • F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word (applicable as is for mobile web; requires changes for mobile apps)
  • F33: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content (applicable as is for mobile web; requires changes for mobile apps)
  • F34: Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content (applicable as is for mobile web; requires changes for mobile apps)
  • F36: Failure of Success Criterion 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 (applicable as is for mobile web; requires changes for mobile apps)
  • F37: Failure of Success Criterion 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 (applicable as is for mobile web; requires changes for mobile apps)
  • F38: Failure of Success Criterion 1.1.1 due to omitting the alt-attribute for non-text content used for decorative purposes only in HTML (applicable as is for mobile web; requires changes for mobile apps)
  • F39: Failure of Success Criterion 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 (applicable as is for mobile web; requires changes for mobile apps)
  • F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit (applicable as is for mobile web; requires changes for mobile apps)
  • F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out (applicable as is for mobile web; requires changes for mobile apps)
  • F42: Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable (applicable as is)
  • F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content (applicable as is)
  • F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability (applicable as is)
  • F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables (applicable as is)
  • F47: Failure of Success Criterion 2.2.2 due to using the blink element (applicable as is)
  • F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information (applicable as is)
  • F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized (applicable as is)
  • F50: Failure of Success Criterion 2.2.2 due to a script that causes a blink effect without a mechanism to stop the blinking at 5 seconds or less (applicable as is)
  • F52: Failure of Success Criterion 3.2.1 and 3.2.5 due to opening a new window as soon as a new page is loaded (applicable as is) 2014-03-10 Jon Avila
  • F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out (applicable as is to mobile web) 2014-03-10 Jon Avila
  • F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML (applicable as is to mobile web) 2014-03-10 Jon Avila
  • F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field (applicable as is) 2014-03-10 Jon Avila
  • F61: Failure of Success Criterion 3.2.5 due to complete change of main content through an automatic update that the user cannot disable from within the content (applicable as is - mentions web technology) 2014-03-10 Jon Avila
  • F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML (applicable as is to mobile web) 2014-03-10 Jon Avila
  • F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link (applicable as to mobile web) 2014-03-10 Jon Avila
  • F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type "image" (applicable as is to mobile web) 2014-03-10 Jon Avila
  • F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages (applicable as is to mobile web, requires updated for non-web) 2014-03-10 Jon Avila
  • F67: Failure of Success Criterion 1.1.1 and 1.2.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information (applicable as is) 2014-03-10 Jon Avila
  • F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable (applicable as is to mobile web, requires equivalent for mobile apps) 2014-03-10 Jon Avila
  • F69: Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured (applicable as is for mobile web, requires equivalent for mobile apps) 2014-03-10 Jon Avila
  • F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup (applicable as is to mobile web) 2014-03-10 Jon Avila
  • F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative (applicable as is to mobile web, may require equivalent for mobile apps) 2014-03-10 Jon Avila
  • F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative (applicable as is to mobile web, may require equivalent for mobile apps) 2014-03-10 Jon Avila
  • F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision (applicable as is to mobile web, requires equivalent for mobile apps) 2014-03-10 Jon Avila
  • F74: Failure of Success Criterion 1.2.2 and 1.2.8 due to not labeling a synchronized media alternative to text as an alternative (applicable as is) 2014-03-10 Jon Avila
  • F75: Failure of Success Criterion 1.2.2 by providing synchronized media without captions when the synchronized media presents more information than is presented on the page (applicable as is) 2014-03-10 Jon Avila
  • F76: Failure of Success Criterion 3.2.2 due to providing instruction material about the change of context by change of setting in a user interface element at a location that users may bypass (applicable as is) 2014-03-10 Jon Avila
  • F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID (applicable as is to mobile web, may be applicable to mobile apps, e.g. labelfor in Android) 2014-03-10 Jon Avila
  • F78: Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator (applicable as is to mobile web, may require mobile app equivalent) 2014-03-10 Jon Avila
  • F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available (applicable as is) 2014-03-10 Jon Avila
  • F80: Failure of Success Criterion 1.4.4 when text-based form controls do not resize when visually rendered text is resized up to 200% (applicable as is to mobile web, requires equivalent for mobile apps) 2014-03-10 Jon Avila
  • F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only (applicable as is) 2014-03-10 Jon Avila
  • F82: Failure of Success Criterion 3.3.2 by visually formatting a s et of phone number fields but not including a text label
  • F83: Failure of Success Criterion 1.4.3 and 1.4.6 due to using background images that do not provide sufficient contrast with foreground text (or images of text) (applicable as is) 2014-03-10 Jon Avila
  • F84: Failure of Success Criterion 2.4.9 due to using a non-specific link such as "click here" or "more" without a mechanism to change the link text to specific text. (applicable as is to mobile web, may require equivalent for native apps) 2014-03-10 Jon Avila
  • F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order (applicable as is mobile web, requires generalization for mobile apps) 2014-03-10 Jon Avila
  • F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number (applicable as is to mobile web, may require equivalent for mobile apps) 2014-03-10 Jon Avila
  • F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS (applicable as is to mobile web; does not apply to mobile apps) 2014-03-10 Jon Avila
  • F88: Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins) (applicable as is to mobile web; may require equivalent for mobile apps) 2014-03-10 Jon Avila
  • F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link (applicable as is to mobile web; does not apply to mobile apps) 2014-03-10 Jon Avila
  • F90: Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes (applicable as is to mobile web; does not apply to mobile apps) 2014-03-10 Jon Avila
  • F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers (applicable as is to mobile web; does not apply to mobile apps) 2014-03-10 Jon Avila
Retrieved from "https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/index.php?title=Common_Failures_(all_Common_Failures_on_one_page)&oldid=1134"