Service UI should support Accessibility (a11y)

[chessbyte]

Some background information on accessibility can be found at w3.org, a11yproject and usability.gov. One can find a community-driven accessibility checklist here.

The following checklist is derived from the IBM Accessibility Checklist

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.

• Non-text Content

Time-based Media: Provide alternatives for time-based media.

• Audio-only and Video-only (Prerecorded)
• Captions (Prerecorded)
• Audio Description or Media Alternative (Prerecorded)
• Captions (Live)
• Audio Description (Prerecorded)

Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

• Info and Relationships
• Meaningful Sequence
• Sensory Characteristics
• Orientation
• Identify Input Purpose

Distinguishable: Make it easier for users to see and hear content including separating foreground from background.

• Use of Color
• Audio Control
• Contrast (Minimum)
• Resize Text
• Images of Text
• Reflow
• Non-text Contrast
• Text Spacing
• Content on Hover or Focus

Keyboard Accessible: Make all functionality available from a keyboard.

• Keyboard
• No Keyboard Trap
• Character Key Shortcuts

Enough Time: Provide users enough time to read and use content.

• Timing Adjustable
• Pause, Stop, Hide

Seizures: Do not design content in a way that is known to cause seizures.

• Three Flashes or Below Threshold

Navigable: Provide ways to help users navigate, find content, and determine where they are.

• Bypass Blocks
• Page Titled
• Focus Order
• Link Purpose (In Context)
• Multiple Ways
• Headings and Labels
• Focus Visible

Input Modalities: Make it easier for users to operate functionality through various inputs beyond keyboard.

• Pointer Gestures
• Pointer Cancellation
• Label in Name
• Motion Actuation

Readable: Make text content readable and understandable.

• Language of Page
• Language of Parts

Predictable: Make Web pages appear and operate in predictable ways.

• On Focus
• On Input
• Consistent Navigation
• Consistent Identification

Input Assistance: Help users avoid and correct mistakes.

• Error Identification
• Labels or Instructions
• Error Suggestion
• Error Prevention (Legal, Financial, Data)

Compatible: Maximize compatibility with current and future user agents, including assistive technologies.

• Parsing
• Name, Role, Value
• Status Messages
• Accessibility-supported Technologies Only

[Fryguy]

Closing in favor of putting the UI on the Chopping Block ManageIQ/manageiq#21377