Skip to the content ForoHackers
Log inJoin

Accessibility: start here

Accessibility
#523 · Ophuscado · · Report

Accessibility is designing and building so that people with disabilities, and people in unusual situations, can use a product: someone who cannot see the screen, hear the sound, use a mouse or process fast motion, or who is simply in bright sun or holding a baby. Done early it costs little, and it improves things for everyone.

Key concepts

  • Perceivable, operable, understandable, robust: the four principles behind the Web Content Accessibility Guidelines.
  • Semantics: using the right element for the job so assistive technology can tell what each part is.
  • Keyboard access: everything works without a pointer, with a visible focus and a logical order.
  • Text alternatives and captions: a description for images, and captions and transcripts for audio and video.
  • Contrast, size and motion: readable text, resizable layouts, and the option to reduce animation.

Vocabulary

  • Screen reader: software that reads out or shows in braille what is on screen, using the accessibility tree.
  • ARIA: attributes that add roles and states for custom controls when plain elements are not enough.
  • Assistive technology: tools such as screen readers, switches, magnifiers and voice control.
  • Accessibility tree: the structure of names, roles and states a platform exposes to those tools.

What to study, in order

  1. Use a page with only the keyboard, then with a screen reader, and note what fails.
  2. Learn semantic HTML thoroughly before touching ARIA.
  3. Check contrast, zoom to large text and test with reduced motion.
  4. Read the guidelines' success criteria and apply them to one component.
  5. Test with disabled users, who find what no checklist will, and fix what they find.

Related tags

#interface-design #frontend #web-standards #usability

Log in or join to reply.