To become a more advanced frontend developer, whether that’s to specialize in UI development, WordPress development or any other form of development that involves creating the end-users’ experience, WCAG is a must to know.

This is my attempt to organize and create notes that other FEDs can utilize to quickly understand WCAG, it’s purpose and how to implement it.

w3.org WCAG Overview

  1. Intro
    • WCAG stands for Web Content Accessibility Guideines
    • “developed through the W3C process”
    • goal: “providing a single shared standard for web content accessibility”
    • explains “how to make web content more accessible to people with disabilities”
    • web content includes text, images, sounds, and code or markup that defines structure, presentation, etc
  2. Who WCAG is for
    • developers of
      • content
      • web authoring tools
      • web accessibility tools
      • mobile content and accessibility
    • anyone else who creates presentational or structural interfaces on the web
    • WCAG is a tech standard, not an intro to accessibility
  3. What is in the WCAG 2 Docs
    • the stable, referenceable tech standards
    • contain 12-13 guidelines organizes under 4 principles
      • POUR
      • perceivable
      • operable
      • understandable
      • robust
    • each guidelines has testable success criteria
    • there are three levels of conformance:
      • A –
      • AA
      • AAA
  4. Other guidelines
    • WCAG is part of a series of accessibility guidelines
    • others are
      • Authoring Tool Accessibility Guidelines (ATAG)
      • User Agent Accessibility Guidelines (UAAG)

Next Notes

  1. Explain the 4 principles of organization and their guideslines
  2. Explain the testable success criteria and their three levels of conformance