Skip to main content A11A Logo, showing the A11A string and an A within a circle A11A, All about accessibility!

Techniques for Web Content Accessibility Guidelines (WCAG) 2.1

Posted by

Vincenzo Rubano
on · 2 minutes reading.

Techniques for WCAG 2.1 is an informative document provided by the Web Accessibility Initiative (WAI) at W3C, to provide guidance for developers and accessibility evaluators on meeting WCAG 2.1 success criteria. These techniques often include practical code examples, and explain how to meet WCAG success criteria leveraging specific web technologies.

In particular, these techniques can be broken down into the following groups:

  • ARIA techniques, that explain how to meet WCAG 2.1 success criteria by leveraging the WAI-ARIA specification;
  • client-side script techniques, that explain how to meet WCAG 2.1 success criteria while using client-side scripting languages to implement dynamic features in a web page;
  • CSS Techniques, that explain how to meet WCAG 2.1 success criteria with Cascading StyleSheets (CSS);
  • common failures, that document some of the most common failures on meeting WCAG 2.1 success criteria you can find in web applications, explaining the reason why they are problematic and often providing more accessible alternatives;
  • general techniques, that cover various aspects on how to meet WCAG 2.1 success criteria with the user interaction model;
  • HTML techniques, that cover specific aspects on how to meet WCAG 2.1 success criteria while using the HTML markup language;
  • PDF techniques, that explains how to meet WCAG 2.1 success criteria while using PDF documents
  • Server-Side script techniques, that explain how to improve web accessibility by leveraging server-side languages;
  • Silverlight techniques, that discuss how to meet WCAG 2.1 success criteria while leveraging Microsoft Silverlight;
  • SMIL techniques, that discuss how to meet WCAG 2.1 success criteria while using the SMIL language.

Please note that this document is by no means exhaustive, and given its nature it is subject to change over time; in addition to this, it is not meant as a standalone resource, but rather as a support document to be used in conjunction with other accessibility-related resources.

Filed under: