DPUB Specific Common Failures

Charles LaPierre edited this page Mar 9, 2016 · 1 revision

A11Y DPUB Techniques based on WCAG > DPUB Specific Common Failures

These WCAG Techniques are currently under review by the Digital Publishing Interest Group's Accessibility Task Force. Any changes marked are a draft and are NOT approved by the DPUB Accessibility Task Force and the WCAG Working Group

Common Failuress

Technique Applies to DPUB Owner Comments
F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS Yes George
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 Yes George
F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information Yes George
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 Yes George
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 Yes George
F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialogue or important sound effects Yes George
F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element Yes George
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 Yes George
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 Yes George
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 Yes George
F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location Yes George
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 Yes George
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 Yes George
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 Yes George
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 Yes George
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 Yes George
F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user Yes George
F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off Yes George
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 Yes George
F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents Yes George
F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information Yes George
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) Yes George
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 Yes George
F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word Yes George
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 Yes George
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 Yes George
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 Yes George
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 Yes George
F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them Yes George
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 Yes George
F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit Yes George
F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out Yes George
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 Yes George
F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content Yes George
F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability Yes George
F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables Yes George
F47: Failure of Success Criterion 2.2.2 due to using the blink element Yes George
F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information Yes George
F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized Yes George
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 Yes George
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 Yes George
F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function Yes George
F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received Yes George
F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out Yes George
F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control Yes George
F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field Yes George
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 Yes George
F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML Yes George
F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link Yes George
F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute or text alternative on img elements, area elements, and input elements of type "image" Yes George
F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages Yes George
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 Yes George
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 determined Yes George
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 Yes George
F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup Yes George
F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative Yes George
F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative Yes George
F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision Yes George
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 Yes George
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 Yes George
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 Yes George
F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID Yes George
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 Yes George
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 Yes George
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% Yes George
F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only Yes George
F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label Yes George
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) Yes George
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. Yes George
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 Yes George
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 Yes George
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 Yes George
F88: Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins) Yes George
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 Yes George
F90: Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes Yes George
F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers Yes George
F92: Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information Yes George

March 2016

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.