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 two guidelines, Parsing and Name, role, value, for future-proofing 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, value are related to interface components and controls (i.e, focus states). By default, all standard HTML controls already meet this criteria. This guideline is aimed mainly 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 developer’s workflow. Use of checklists, like The Accessibility Project checklist, can help keep you on task.

Edit on GitHub