WCAG 2.1 Workshop Eliminated 350+ Accessibility Bugs

When I joined a British company, I learned that by law their website had to be accessible. But in reality, accessibility was barely discussed—the interface had many barriers for users.

I had just completed a course at Projector on Inclusive Web Design and decided it was time to act. I researched 12 main pages of the site, identified common mistakes, and prepared a workshop presentation for the development team.

In the workshop, I broke down:

• What web accessibility is and why it matters not only for people with disabilities

• What standards exist (particularly WCAG 2.1) and how POUR principles impact real experience

• What specific problems exist on our site and how they complicate usage

• Why this isn't "box-checking," but about quality UX for all users.
  

After this, I was invited to join the team that was already working on implementing accessibility in practice. The company underwent an external audit, and—brace yourself—over 350 errors were found, half of which were critical. The biggest problems were with keyboard navigation and screen reader support.

Together with colleagues, we began systematically fixing everything:

• Updated the design system

• Reworked the component library

• Added automated checks

• Created documentation to make future work easier and error-free.
  

After a follow-up audit, the company achieved WCAG 2.1 AA compliance. All critical errors were eliminated, and those remaining were low priority.

This experience taught me one simple thing: accessibility isn't about fixing "bugs." It's about creating a product that's convenient for everyone to use. And how important it is to build inclusion into the process "from the start," not after release.

Accessibility isn't a technical requirement—it's the foundation of quality UX for all users.

Anastasiia Savushkina

WCAGENTS Expert

Accessible Website, Confident Business

Start your journey to accessibility today