Jump to beginning of inaccessible report page

W3C logoWeb Accessibility Initiative (WAI) logo

Inaccessible Tickets Page Report Before and After Demonstration

Improving a Web site using Web Content Accessibility Guidelines (WCAG) 2.0

Perceivable

Conformance of Tickets Page to WCAG 2.0 - Perceivable
# Title Description Result
1.1 Text Alternatives Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. Some success criteria failed
1.1.1 Non-text Content All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A)
  • Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)
  • Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
  • Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
  • Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
  • CAPTCHA: If the purpose non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
  • Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
 Fail
Failures
  • Failure 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
  • Failure 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)
  • Failure 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
  • Failure 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
  • Failure 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"
  • Failure F71 - Failure of Success Criterion 1.1.1 due to using text look-alikes to represent text without providing a text alternative
1.2 Time-based Media Provide alternatives for time-based media. All success criteria met
1.2.1 Audio-only and Video-only (Prerecorded) For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A)
  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
 Pass
Techniques Pass due to no corresponding content
1.2.2 Captions (Prerecorded) Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Pass
Techniques Pass due to no corresponding content
1.2.3 Audio Description or Media Alternative (Prerecorded) An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Pass
Techniques Pass due to no corresponding content
1.2.4 Captions (Live) Captions are provided for all live audio content in synchronized media. (Level AA) Pass
Techniques Pass due to no corresponding content
1.2.5 Audio Description (Prerecorded) Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Pass
Techniques Pass due to no corresponding content
1.2.6 Sign Language (Prerecorded) Sign language interpretation is provided for all prerecorded audio content in synchronized media. (Level AAA) Pass
Techniques Pass due to no corresponding content
1.2.7 Extended Audio Description (Prerecorded) Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. (Level AAA) Pass
Techniques Pass due to no corresponding content
1.2.8 Media Alternative (Prerecorded) An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. (Level AAA) Pass
Techniques Pass due to no corresponding content
1.2.9 Audio-only (Live) An alternative for time-based media that presents equivalent information for live audio-only content is provided. (Level AAA) Pass
Techniques Pass due to no corresponding content
1.3 Adaptable Create content that can be presented in different ways (for example simpler layout) without losing information or structure. Some success criteria failed
1.3.1 Info and Relationships Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) Fail
Failures
  • Failure 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
  • Failure F46 - Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables
  • Failure 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
1.3.2 Meaningful Sequence When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) Fail
Failures Failure F49 - Failure of Success Criterion 1.3.2 due to using an HTML layout table that does not make sense when linearized
1.3.3 Sensory Characteristics Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A)

Note: For requirements related to color, refer to Guideline 1.3.

 Pass
Techniques Pass due to no corresponding content
1.4 Distinguishable Make it easier for users to see and hear content including separating foreground from background. Some success criteria failed
1.4.1 Use of Color Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)

Note: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.

 Fail
Failures Failure F73 - Failure of Success Criterion 1.4.1 due to creating links that are not visually evident without color vision
1.4.2 Audio Control If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A)

Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

 Pass
Techniques Pass due to no corresponding content
1.4.3 Contrast (Minimum) The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA)
  • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
  • Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
 Fail
Failures
  • Failure 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
1.4.4 Resize text Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA) Pass
Techniques
  • Technique G142 - Using a technology that has commonly-available user agents that support zoom
  • Technique G179 - Ensuring that there is no loss of content or functionality when the text resizes and text containers do not resize
1.4.5 Images of Text If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA)
  • Customizable: The image of text can be visually customized to the user's requirements;
  • Essential: A particular presentation of text is essential to the information being conveyed.

Note: Logotypes (text that is part of a logo or brand name) are considered essential.

 Fail
Failures Text in HTML and CSS decoration can be used to achieve the same visual presentation, rather than using images of text
1.4.6 Contrast (Enhanced) The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: (Level AAA)
  • Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1;
  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
  • Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
 Fail
Failures
  • The visual presentation of text does not have a contrast ratio of at least 7:1
  • Failure 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
1.4.7 Low or No Background Audio For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: (Level AAA)
  • No Background: The audio does not contain background sounds.
  • Turn Off: The background sounds can be turned off.
  • 20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds.

Note: Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content.

 Pass
Techniques Pass due to no corresponding content
1.4.8 Visual Presentation For the visual presentation of blocks of text, a mechanism is available to achieve the following: (Level AAA)
  1. foreground and background colors can be selected by the user
  2. width is no more than 80 characters or glyphs (40 if CJK)
  3. text is not justified (aligned to both the left and the right margins)
  4. line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing
  5. text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window
 Fail
Failures
  • Line spacing can not be adjusted to 1.5 times larger without losing information or functionality
  • Failure 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
  • Failure F88 - Failure of SC 1.4.8 due to using text that is justified (aligned to both the left and the right margins)
1.4.9 Images of Text (No Exception) Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. (Level AAA)

Note: Logotypes (text that is part of a logo or brand name) are considered essential.

 Fail
Failures Images of text are used for non-decorative purposes while the particular presentation of text is not essential to the information being conveyed

Operable

Conformance of Tickets Page to WCAG 2.0 - Operable
# Title Description Result
2.1 Keyboard Accessible Make all functionality available from a keyboard. Some success criteria failed
2.1.1 Keyboard All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)

Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path dependent input but the underlying function (text input) does not.

Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

 Fail
Failures
  • Failure F54 - Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function
  • Failure 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
2.1.2 No Keyboard Trap If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)

Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

 Pass
Techniques Technique G21 - Ensuring that users are not trapped in content
2.1.3 Keyboard (No Exception) All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA) Fail
Failures
  • Failure F54 - Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function
  • Failure 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
2.2 Enough Time Provide users enough time to read and use content. All success criteria met
2.2.1 Timing Adjustable For each time limit that is set by the content, at least one of the following is true: (Level A)
  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.

Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1 which puts limits on changes of content or context as a result of user action.

 Pass
Techniques Pass due to no corresponding content
2.2.2 Pause, Stop, Hide For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3.

Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Note 3: Content that is updated periodically by software, or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users, and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

 Pass
Techniques Pass due to no corresponding content
2.2.3 No Timing Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. (Level AAA) Pass
Techniques Technique G5 - Allowing users to complete an activity without any time limit
2.2.4 Interruptions Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA) Pass
Techniques Pass due to no corresponding content
2.2.5 Re-authenticating When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA) Pass
Techniques Pass due to no corresponding content
2.3 Seizures Do not design content in a way that is known to cause seizures. All success criteria met
2.3.1 Three Flashes or Below Threshold Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)

Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

 Pass
Techniques Technique G19 - Ensuring that no component of the content flashes more than three times in any 1-second period
2.3.2 Three Flashes Web pages do not contain anything that flashes more than three times in any one second period. (Level AAA) Pass
Techniques Technique G19 - Ensuring that no component of the content flashes more than three times in any 1-second period
2.4 Navigable Provide ways to help users navigate, find content and determine where they are. Some success criteria failed
2.4.1 Bypass Blocks A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A) Fail
Failures No mechanisms are available to bypass blocks of content that are repeated on multiple Web pages
2.4.2 Page Titled Web pages have titles that describe topic or purpose. (Level A) Fail
Failures Failure F25 - Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents
2.4.3 Focus Order If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A) Pass
Techniques Technique G59 - Placing the interactive elements in an order that follows sequences and relationships within the content
2.4.4 Link Purpose (In Context) The purpose of each link can be determined from the link text alone, or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) Fail
Failures
  • Failure F63 - Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link
  • Failure F89 - Failure of 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
2.4.5 Multiple Ways More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA) Pass
Techniques
2.4.6 Headings and Labels Headings and labels describe topic or purpose. (Level AA) Fail
Failures Headings are not programmatically determined
2.4.7 Focus Visible Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) Fail
Failures
  • Failure 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
  • Failure 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
2.4.8 Location Information about the user's location within a set of Web pages is available. (Level AAA) Fail
Failures No information is available about the user's location within a set of Web pages
2.4.9 Link Purpose (Link Only) A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. (Level AAA) Fail
Failures
  • Failure 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
  • Failure F89 - Failure of 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
2.4.10 Section Headings Section headings are used to organize the content. (Level AAA)

Note 1: "Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content.

Note 2: This success criterion covers sections within writing, not user interface components. User Interface components are covered under Success Criterion 4.1.2.

 Fail
Failures Headings are not programmatically determined

Understandable

Conformance of Tickets Page to WCAG 2.0 - Understandable
# Title Description Result
3.1 Readable Make text content readable and understandable. Some success criteria failed
3.1.1 Language of Page The default human language of each Web page can be programmatically determined. (Level A) Fail
Failures The default human language of the Web page can not be programmatically determined
3.1.2 Language of Parts The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) Pass
Techniques Pass due to no corresponding content
3.1.3 Unusual Words A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA) Pass
Techniques Pass due to no corresponding content
3.1.4 Abbreviations A mechanism for identifying the expanded form or meaning of abbreviations is available. (Level AAA) Fail
Failures No mechanism for identifying the expanded form or meaning of abbreviations is available
3.1.5 Reading Level When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. (Level AAA) Pass
Techniques Technique G153 - Making the text easier to read
3.1.6 Pronunciation A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (Level AAA) Pass
Techniques Pass due to no corresponding content
3.2 Predictable Make Web pages appear and operate in predictable ways. Some success criteria failed
3.2.1 On Focus When any component receives focus, it does not initiate a change of context. (Level A) Fail
Failures Failure 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
3.2.2 On Input Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) Fail
Failures Change of context without prior warning when the status of a select list is changed
3.2.3 Consistent Navigation Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) Pass
Techniques

Technique G61 - Presenting repeated components in the same relative order each time they appear

Advisory Techniques

  • Future Link - Using templates to ensure consistency across multiple Web pages
3.2.4 Consistent Identification Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) Fail
Failures Components that have the same functionality within a set of Web pages are not identified at all
3.2.5 Change on Request Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA) Fail
Failures Change of context without prior warning when the status of a select list is changed
3.3 Input Assistance Help users avoid and correct mistakes. Some success criteria failed
3.3.1 Error Identification If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) Pass
Techniques Pass due to no corresponding content
3.3.2 Labels or Instructions Labels or instructions are provided when content requires user input. (Level A) Fail
Failures Label is not provided for form control
3.3.3 Error Suggestion If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Pass
Techniques Pass due to no corresponding content
3.3.4 Error Prevention (Legal, Financial, Data) For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)
  1. Reversible: Submissions are reversible.
  2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
 Pass
Techniques Pass due to no corresponding content
3.3.5 Help Context-sensitive help is available. (Level AAA) Pass
Techniques Pass due to no corresponding content
3.3.6 Error Prevention (All) For Web pages that require the user to submit information, at least one of the following is true: (Level AAA)
  1. Reversible: Submissions are reversible.
  2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
 Pass
Techniques Pass due to no corresponding content

Robust

Conformance of Tickets Page to WCAG 2.0 - Robust
# Title Description Result
4.1 Compatible Maximize compatibility with current and future user agents, including assistive technologies. Some success criteria failed
4.1.1 Parsing In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)

Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

 Fail
Failures Failure F70 - Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup
4.1.2 Name, Role, Value For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)

Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.

 Fail
Failures
  • Failure 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
  • Failure 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
  • Failure F89 - Failure of 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