a11yNot reference

The 103 cases of the a11yNot pageand the Alpenglow shop: the problem each one shows, the criteria it fails, the tools that flag it, and links to where it sits in the shop and in the catalogue page. Texts are the catalogue's own.

Audit rules: ARIA 11

Audit rules: ARIA
CaseProblemWCAGFlagged byWhere
AX_ARIA_01Elements with ARIA roles must use a valid, non-abstract ARIA rolen/aAInspector Sidebar, aXe
AX_ARIA_02aria-labelledby attributes should refer to an element which exists in the DOMn/aaXe, Accessibility Developer Tools, WAVE
AX_ARIA_03Elements with ARIA roles must have all required attributes for that rolen/aaXe, Accessibility Developer Tools
AX_ARIA_04ARIA state and property values must be validn/aaXe, Accessibility Developer Tools
AX_ARIA_06aria-owns should not be used if ownership is implicit in the DOMn/aAccessibility Developer Tools
AX_ARIA_07An element's ID must not be present in more than one aria-owns attribute at any timen/aAccessibility Developer Tools
AX_ARIA_08Elements with ARIA roles must ensure required owned elements are presentn/aaXe, Accessibility Developer Tools
AX_ARIA_09Elements with ARIA roles must be in the correct scopen/aaXe, AInspector Sidebar, Accessibility Developer Tools
AX_ARIA_10This element has an unsupported ARIA attributen/aaXe, Accessibility Developer Tools
AX_ARIA_11This element has an invalid ARIA attributen/aAInspector Sidebar, aXe, Accessibility Developer Tools
AX_ARIA_12This element does not support ARIA roles, states and propertiesn/aAccessibility Developer Tools

Audit rules: COLOR 1

Audit rules: COLOR
CaseProblemWCAGFlagged byWhere
AX_COLOR_01Text elements should have a reasonable contrast ration/aaXe

Audit rules: FOCUS 2

Audit rules: FOCUS
CaseProblemWCAGFlagged byWhere
AX_FOCUS_01These elements are focusable but either invisible or obscured by another elementn/an/a
AX_FOCUS_02Elements with onclick handlers must be focusablen/aAInspector Sidebar

Audit rules: HTML 2

Audit rules: HTML
CaseProblemWCAGFlagged byWhere
AX_HTML_01The web page should have the content's human language indicated in the markupn/aaXe
AX_HTML_02An element's ID must be unique in the DOMn/aaXe, Accessibility Developer Tools

Audit rules: TABLE 2

Audit rules: TABLE
CaseProblemWCAGFlagged byWhere
AX_TABLE_01aTables must have appropriate headersn/aAInspector Sidebar, aXe
AX_TABLE_01bTables must have appropriate headersn/aaXe, Accessibility Developer Tools

Audit rules: TEXT 2

Audit rules: TEXT
CaseProblemWCAGFlagged byWhere
AX_TEXT_01Controls and media elements should have labelsn/aAInspector Sidebar, aXe, Accessibility Developer Tools, WAVE
AX_TEXT_02Images should have an alt attribute, unless they have an ARIA role of "presentation"n/aAInspector Sidebar, aXe, Accessibility Developer Tools, WAVE

Audit rules: VIDEO 1

Audit rules: VIDEO
CaseProblemWCAGFlagged byWhere
AX_VIDEO_01Video elements should use <track> elements to provide captionsn/aaXe, Accessibility Developer Tools

WCAG 1: Perceivable 50

WCAG 1: Perceivable
CaseProblemWCAGFlagged byWhere
F1Changing the meaning of content by positioning information with CSS1.3.2n/a
F2-1Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text1.3.1WAVE
F2-2Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text1.3.1n/a
F2-3Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text1.3.1n/a
F24-1Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa1.4.3, 1.4.6, 1.4.8n/a
F24-2Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa1.4.3, 1.4.6, 1.4.8AInspector Sidebar, aXe
F24-3Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa1.4.3, 1.4.6, 1.4.8aXe, Accessibility Developer Tools
F24-4Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa1.4.3, 1.4.6, 1.4.8n/a
F24-5Failure of Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa1.4.3, 1.4.6, 1.4.8AInspector Sidebar, aXe, Accessibility Developer Tools
F3-1Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information1.1.1n/a
F3-2Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information1.1.1n/a
F3-3Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information1.1.1n/a
F32-1Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word1.3.2n/a
F32-2Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word1.3.2n/a
F32-3Failure of Success Criterion 1.3.2 due to using white space characters to control spacing within a word1.3.2n/a
F33Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to create multiple columns in plain text content1.3.1, 1.3.2n/a
F34Failure of Success Criterion 1.3.1 and 1.3.2 due to using white space characters to format tables in plain text content1.3.1, 1.3.2n/a
F39Failure 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 technology1.1.1WAVE
F42-1Failure 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 determinable1.3.1, 2.1.1AInspector Sidebar, WAVE
F42-2Failure 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 determinable1.3.1, 2.1.1AInspector Sidebar, WAVE
F42-3Failure 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 determinable1.3.1, 2.1.1AInspector Sidebar
F42-4Failure 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 determinable1.3.1, 2.1.1n/a
F43-1Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content1.3.1AInspector Sidebar, WAVE
F43-2Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content1.3.1AInspector Sidebar, aXe, WAVE
F43-3Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content1.3.1n/a
F43-4Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content1.3.1n/a
F46Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables1.3.1WAVE
F48-1Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information1.3.1n/a
F48-2Failure of Success Criterion 1.3.1 due to using the pre element to markup tabular information1.3.1n/a
F49-1Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized1.3.2n/a
F49-2Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized1.3.2AInspector Sidebar, aXe
F65Failure 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"1.1.1AInspector Sidebar, aXe, Accessibility Developer Tools, WAVE
F68-1Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determined1.3.1, 4.1.2AInspector Sidebar, aXe, Accessibility Developer Tools, WAVE
F68-2Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determined1.3.1, 4.1.2AInspector Sidebar, aXe, Accessibility Developer Tools, WAVE
F68-3Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determined1.3.1, 4.1.2AInspector Sidebar, aXe, Accessibility Developer Tools, WAVE
F69-1Failure 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 obscured1.4.4n/a
F69-2Failure 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 obscured1.4.4n/a
F71-1Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative1.1.1n/a
F71-2Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative1.1.1n/a
F72Failure of Success Criterion 1.1.1 due to using ASCII art without providing a text alternative1.1.1n/a
F73Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision1.4.1n/a
F80Failure of Success Criterion 1.4.4 when text-based form controls do not resize when visually rendered text is resized up to 200%1.4.4n/a
F87-1Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS1.3.1n/a
F87-2Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS1.3.1n/a
F88-1Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins)1.4.8WAVE
F88-2Failure of Success Criterion 1.4.8 due to using text that is justified (aligned to both the left and the right margins)1.4.8n/a
F90Failure of Success Criterion 1.3.1 for incorrectly associating table headers and content via the headers and id attributes1.3.1aXe
F91Failure of Success Criterion 1.3.1 for not correctly marking up table headers1.3.1aXe
F92Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information1.3.1aXe
F93Failure of Success Criterion 1.4.2 for absence of a way to pause or stop an HTML5 media element that autoplays1.4.2n/a

WCAG 2: Operable 19

WCAG 2: Operable
CaseProblemWCAGFlagged byWhere
F4Failure of Success Criterion 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than five seconds2.2.2WAVE
F40Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit2.2.1, 2.2.4n/a
F41-1Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out2.2.1, 2.2.4, 3.2.5aXe
F41-2Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out2.2.1, 2.2.4, 3.2.5n/a
F44Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability2.4.3Accessibility Developer Tools, aXe, WAVE
F47Failure of Success Criterion 2.2.2 due to using the blink element2.2.2aXe, WAVE
F50Failure 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 less2.2.2n/a
F54Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function2.1.1n/a
F55-1Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received2.1.1, 2.4.7, 3.2.1n/a
F55-2Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received2.1.1, 2.4.7, 3.2.1n/a
F55-3Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received2.1.1, 2.4.7, 3.2.1n/a
F63-1Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link2.4.4n/a
F63-2Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link2.4.4n/a
F78-1Failure 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 indicator2.4.7n/a
F78-2Failure 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 indicator2.4.7n/a
F78-3Failure 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 indicator2.4.7n/a
F84-1Failure 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.2.4.9Accessibility Developer Tools, WAVE
F84-2Failure 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.2.4.9WAVE
F89Failure 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 link2.4.4, 2.4.9, 4.1.2AInspector Sidebar, aXe, Accessibility Developer Tools, WAVE

WCAG 3: Understandable 3

WCAG 3: Understandable
CaseProblemWCAGFlagged byWhere
F36-1Failure 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 value3.2.2AInspector Sidebar
F36-2Failure 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 value3.2.2AInspector Sidebar, WAVE
F37Failure of Success Criterion 3.2.2 due to launching a new window without prior warning when the selection of a radio button, check box or select list is changed3.2.2n/a

WCAG 4: Robust 10

WCAG 4: Robust
CaseProblemWCAGFlagged byWhere
F59Failure 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 control4.1.2AInspector Sidebar
F70-1Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup4.1.1n/a
F70-2Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup4.1.1n/a
F70-3Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup4.1.1n/a
F70-4Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup4.1.1n/a
F70-5Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup4.1.1n/a
F70-6Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup4.1.1n/a
F86-1Failure 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 number4.1.2AInspector Sidebar, aXe, Accessibility Developer Tools, WAVE
F86-2Failure 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 number4.1.2AInspector Sidebar, aXe, Accessibility Developer Tools, WAVE
F86-3Failure 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 number4.1.2AInspector Sidebar, aXe, Accessibility Developer Tools, WAVE