
What is WCAG and Why Does it Matter

Why should we talk about Web Content Accessibility Guidelines (WCAG)? The present and future of engagement are online and web based . With the growth of the metaverse, ongoing drive towards digital transformation and meteoric rise in online purchases, the ability to deliver a great digital experience has become table stakes.
Trend trackers have pointed out how much more important the web experience has become since the start of the pandemic. But for the more than 1 in 5 people with a disability, these experiences might come with caveats. Worldwide, more than 220 million people have a vision impairment of some sort and over 2 billion have a disability of some kind. What implications does this have for web design? Quite a lot!
History of WCAG
The need for a set of web content accessibility guidelines was recognized decades ago. We’ll explore what those standards are, but how have they evolved over time, and when did they first come together?
To find the origins of WCAG we have to go back to before the Y2K crisis. Back to the previous millennium. The year 1999. On May 5 th of that year, the HTML-focused WCAG 1.0 helped shaped the standards for web accessibility and digital experience. In 2008, those rules got an update in the form of WCAG 2.0.
Where the original had focused on HTML, the new guidelines (and the 2018 WCAG 2.1) expressed a technology-agnostic approach to accessibility for “web content on desktops, laptops, tablets, and mobile devices.” The goal of WCAG overall has not changed from creating a more accessible web environment, but each update has given additional guidance on this critical topic.
What Does WCAG Require?
The standards set out in WCAG 2.1 cover four key factors for accessible design along with a series of conformance criteria to evaluate WCAG compliance. In particular, WCAG 2.1 indicates web content should be perceivable, operable, understandable, and robust. What do these mean?
1 Perceivable
“Information and user interface components must be presentable to users in ways they can perceive.”
If a user cannot see, hear, or otherwise interact with web content, it is not accessible to them. This means, for example, that non-text content should have transcripts, alt-text, or other features meant to enable screen reading. Perceivable design isn’t limited to text accessibility, but WCAG 2.1 has additional guidelines on creating more perceivable content.
Example: Thanks to labels for all text fields in the screens of CSG Forte Checkout, users can understand what information each field is meant to include, allowing them to complete the form.


