Skip to content

Instantly share code, notes, and snippets.

Last active December 11, 2015 05:19
Show Gist options
  • Save davatron5000/4551421 to your computer and use it in GitHub Desktop.
Save davatron5000/4551421 to your computer and use it in GitHub Desktop.
layout title description categories
How-to: Future proof your accessibility efforts.
Ways to make your accessibility effort as future proof as possible.

Future proofing your accessibility work will help lower your development costs as well as support current and future user agents, such as assistive technologies (AT). WCAG has 2 guidelines, Parsing and Name, role, value, for futureproofing your website.

  1. Parsing relates to ensuring that user agents and AT are able to read and navigate your web site correctly. Validating your site using the W3C Markup Validator can help you find errors in your markup and ease the burden of the AT parsing your web page. Follow the official specifications for your markup. E.g. make sure to close open tags (<div class="a-class">...</div>) and use unique IDs.
  2. Name, role, and value are related to interface components and controls. By default, all standard HTML controls already meet this criteria. This guideline is mainly aimed at developers that design and/or script their own interface components and controls.

While these are only two recommendations to make your site more accessible, it should have a good spot in every web developers workflow. Use of checklists, like the one we have composed here on The Accessibility Project, can help keep you on task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment