This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Review Failures which may no longer be failures

From WCAG WG
Jump to: navigation, search
technique Action Aria technique which may resolve
F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS Review Would aria-flowto resolve this?
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 None
F3: Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information None
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 None
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 None
F8: Failure of Success Criterion 1.2.2 due to captions omitting some dialogue or important sound effects None
F9: Failure of Success Criterion 3.2.5 due to changing the context when the user removes focus from a form element None
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 None
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 None
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 None
F14: Failure of Success Criterion 1.3.3 due to identifying content only by its shape or location None
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 Review We may be able to improve this one. Add ARIA to the resources
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 None
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 None
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 None
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 None
F22: Failure of Success Criterion 3.2.5 due to opening windows that are not requested by the user None
F23: Failure of 1.4.2 due to playing a sound longer than 3 seconds where there is no mechanism to turn it off None
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 None
F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents None
F26: Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information None
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) None
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 None
F32: Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word None
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 None
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 None
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 None
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 None
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 Review Should we allow role="presentation" as well?
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 None
F40: Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit None
F41: Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out None
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 None Already allows for ARIA
F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content Review Should allow role="presentation" to "nullify" the semantics
F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability Review Should this failure mention anything about tabindex=0 and tabindex=-1
F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables None
F47: Failure of Success Criterion 2.2.2 due to using the blink element None
F48: Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information None
F49: Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized None
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 None
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 None
F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function Review Not ARIA related but language of test procedure needs clarifying to make it clear that it is the functionality that needs to be able to be invoked, not the specific script function
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 None
F58: Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out Review Not ARIA related but as written the test procedure disallows a dialog box coming up asking the user if they need more time, and if the user ignores it the page times out.
F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML Review Need to add ARIA to the resources
F60: Failure of Success Criterion 3.2.5 due to launching a new window when a user enters text into an input field Review Not ARIA related. Should also allow something which allows the user to pick a value
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 NOTE The first test procedure is ridiculous
F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML None
F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link Review Needs modifying to allow aria-describedby (at least) as a solution
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" Review Need to determine if the aria accessible name calculation can actually meet this
F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages None
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 None
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 Review need to modify to allow aria-labelledby in this case
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 None
F70: Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup None
F71: Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative None
F72: Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative None
F73: Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision None
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 None
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 None
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 None
F77: Failure of Success Criterion 4.1.1 due to duplicate values of type ID None
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 None
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 Review Add Aria to resources
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% None
F81: Failure of Success Criterion 1.4.1 due to identifying required or error fields using color differences only None
F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label None
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) None
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. None
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 Review Technique needs clarifying. Test Procedure is ok but the rest needs looking at.
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 Review Add aria techniques as another alternative test procedure
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 Review ARIA explicitly allows this as part of the text alternative computation. We need to decide if it is well enough supported.
F88: Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins) None
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 Review ARIA explicitly allows this as part of the text alternative computation. We need to Should allow aria accessible name calculation to procide support