Process

Updated on by ,

It’s difficult to find a solid process for ensuring a site is accessible. Most of what I’ve been able to find online gathers different accessibility guidelines but doesn’t present new devs with a simple process to ensure they have a level of baseline accessibility for their projects.

Every project is different and will present unique challenges, but it would be great to be able to fall back on a somewhat simple process for including a11y practices at every stage of designing and building a site.

This is a tentative stab at a process, more or less lifted from Accessible to All at Google’s web.dev.

Contents

  1. Structure
  2. Keyboard Access
    1. Focus Semantics
    2. Tabindex
    3. Focus Styles
  3. Semantics — Screen Reader
    1. Landmarks
    2. Labels
    3. Media
  4. Accessible CSS
    1. Tap Targets
    2. Color and Contrast
    3. Responsive Design
    4. Reordering

Structure

Keyboard Access

Focus Semantics

Tabindex

Focus Styles

Semantics — Screen Reader

Landmarks

Labels

Media

Accessible CSS

Tap Targets

Color and Contrast

Responsive Design

Reordering

WebMentions

No mentions yet

Say something about this post!