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
Closed 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
Closed 1.2 Time-based Media Provide alternatives for time-based media. All success criteria met
Closed 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
Closed 1.4 Distinguishable Make it easier for users to see and hear content including separating foreground from background. Some success criteria failed

Operable

Conformance of Tickets Page to WCAG 2.0 - Operable
# Title Description Result
Closed 2.1 Keyboard Accessible Make all functionality available from a keyboard. Some success criteria failed
Closed 2.2 Enough Time Provide users enough time to read and use content. All success criteria met
Closed 2.3 Seizures Do not design content in a way that is known to cause seizures. All success criteria met
Closed 2.4 Navigable Provide ways to help users navigate, find content and determine where they are. Some success criteria failed

Understandable

Conformance of Tickets Page to WCAG 2.0 - Understandable
# Title Description Result
Closed 3.1 Readable Make text content readable and understandable. Some success criteria failed
Closed 3.2 Predictable Make Web pages appear and operate in predictable ways. Some success criteria failed
Closed 3.3 Input Assistance Help users avoid and correct mistakes. Some success criteria failed

Robust

Conformance of Tickets Page to WCAG 2.0 - Robust
# Title Description Result
Closed 4.1 Compatible Maximize compatibility with current and future user agents, including assistive technologies. Some success criteria failed