Csep-590B-Lec-2

• We will structure our work around the Web Accessibility Initiative (WAI).
• It conforms to the POUR standard:
  • Perceivable
  • Operable
  • Understandable
  • Robust: interpretable by wide variety of user agents (including assistive tech)

Perceivable

• Perceivable alternates for time-based media
  • e.g. closed captions, transcripts, ASL interpretation
• Ensure information is available for accessibility tools
• Distinguishable:
  • ensure color/volume contrasts conform to standards
  • ensure text is resizable
  • tooltips should be hoverable, dismissable, and persistent

Operable

• Keyboard accessible
  • benefits screen reader users, speech input users, switch input users
  • common pitfalls:
    • keyboard "traps" where focus is stuck on one section of the page
    • shortcuts need to be configurable / removable
    • invisible content
• Give users enough time for things
• Avoid flashing visual content which can trigger seizures
• Navigable:
  • jumpable uninteresting content
  • focus is perceivable
  • links have purposeful text
  • sections
• Pointers should be able to access everything like keyboards
• Use larger actionable element, rather than padding, so that users can trigger actions more easily

Understandable

• Readable:
  • avoid jargon, if necessary include a glossary
  • Clear and simple language
• Predictable:
  • don't change context just because of focus
  • use familiar names/icons for common things
• Input assistance:
  • creating error-free input (e.g. auto correct)
  • detecting input errors (show red squiggle)

Robust

• Compatible:
  • Don't circumvent AT with unconventional / custom widgets.
  • Use standard markup.
  • Style with CSS, not javascript