Getting started with Web Accessibility

Emmanuel Amoah
2 min readJan 22, 2024

--

In my previous post, I explained why we developers and designers should be concerned about web accessibility.

Today, I introduce the W3C’s Web Accessibility Initiative (WAI), its resources, and other learning materials to help web authors get started with Web Accessibility.

W3C’s Web Accessibility Initiative (WAI)

The Web Accessibility Initiative of the W3C develops strategies, standards and resources to help us make the Web more accessible to people with disabilities.

Front page of the W3C WAI website
Front page of the W3C WAI website (w3.org/WAI)

Who can use WAI resources?

WAI provides technical and educational resources for the following roles:

  • Content writers
  • Designers
  • Developers
  • Evaluators & Testers
  • Managers
  • Policy makers
  • Trainers & Educators
  • Web users, People with disabilities & Advocates

Standards and Guidelines

WAI provides 3 accessibility guidelines for different categories of developers. These are:

  • Web Content Accessibility Guidelines (WCAG) — For creators of web content, i.e., web developers & web designers.
  • Authoring Tool Accessibility Guidelines (ATAG) — For creators of software used to PRODUCE web content. E.g., CMS, Blogs, Social networking sites, etc.
  • User Agent Accessibility Guidelines (UAAG) — For creators of software used to RENDER web content. E.g., Browsers, Media Players, etc.

Where to start

Take the “Introduction to Web Accessibility” free online course by W3Cx

Home page for “Introduction to Web Accessibility” course on edX
Home page for “Introduction to Web Accessibility” course on edX

Other free resources

You can also learn about web accessibility for free online from the following resources:

Up next…

In the next post, we will get introduced to the Web Content Accessibility Guidelines (WCAG), and talk about the four core principles (P.O.U.R)

Stay tuned for more!

Thanks for reading! Found this helpful? Be sure to leave a like and share!

Social accounts:

This article was written as an accessible alternative to the post shared on my LinkedIn account.

--

--