What does WCAG stand for?
WCAG stands for Web Content Accessibility Guidelines. These guidelines provide recommendations for making websites and digital services more accessible to people with disabilities.
WCAG is developed by the World Wide Web Consortium, commonly known as the W3C.
Its aim is to help ensure digital products can be used by people with visual, hearing, motor, cognitive and other accessibility needs.
What does WCAG compliance mean?
WCAG compliance means that a website or application meets a defined set of accessibility requirements.
WCAG includes three levels of conformance:
- Level A: The minimum accessibility requirements.
- Level AA: The level most organisations aim to meet.
- Level AAA: The highest and most demanding level.
Meeting Level AA is a common target because it addresses many of the accessibility barriers users are likely to encounter.
Why is WCAG important?
It makes software available to more people
Inaccessible software can prevent people from reading content, completing forms, making purchases or using essential services.
Accessibility helps remove those barriers and gives more users equal access to digital products.
It improves the general user experience
Many accessibility improvements benefit everyone. Clear navigation, readable text, meaningful labels and helpful error messages make software easier for all users.
It can support legal and contractual requirements
Organisations may be required to meet accessibility standards because of legislation, public-sector requirements, customer contracts or internal policies.
It improves overall software quality
Accessibility testing regularly uncovers unclear interfaces, missing labels, poor keyboard behaviour and inconsistent navigation.
Fixing these issues results in a more reliable and usable product.
The four WCAG principles
WCAG is organised around four principles, commonly remembered using the acronym POUR.
1. Perceivable
Users must be able to perceive the information being presented.
- Images should have appropriate alternative text.
- Videos should include captions where needed.
- Text should have sufficient colour contrast.
- Content should use clear headings and structure.
2. Operable
Users must be able to operate and navigate the interface.
- Interactive controls should work with a keyboard.
- Keyboard focus should remain visible.
- Users should not become trapped inside a component.
- Flashing content should be avoided or controlled.
3. Understandable
Content and functionality should be predictable and understandable.
- Form fields should have clear labels.
- Error messages should explain how to fix the issue.
- Navigation should remain consistent.
- Instructions should be clear and easy to follow.
4. Robust
Content should work reliably across different browsers, devices and assistive technologies.
This includes screen readers, voice-control software, keyboard-only navigation and browser accessibility tools.
What should QA testers check?
Keyboard navigation
Try navigating the complete page using only the keyboard.
- Can every interactive control be reached?
- Is the focus order logical?
- Can menus and modal windows be opened and closed?
- Is the current focus position visible?
Colour contrast
Text and important controls should remain readable against their backgrounds.
Light grey text on a white background may look clean but can be difficult for many users to read.
Alternative text
Images that communicate important information should include meaningful alternative text.
<img
src="warehouse-scanner.jpg"
alt="Employee scanning warehouse stock using a handheld device"
>Decorative images should normally use an empty alternative text value so screen readers can ignore them.
<img src="decorative-pattern.svg" alt="">Forms and labels
Every form field should have a clear, associated label. Placeholder text should not be used as the only label.
Error messages
A useful error message should explain what went wrong, identify the affected field and tell the user how to correct it.
Responsive layouts and zoom
Test whether the page remains usable when text is enlarged or the browser is zoomed. Content should not overlap, disappear or become impossible to operate.
Useful accessibility testing tools
- Lighthouse in Chrome or Microsoft Edge developer tools
- axe DevTools
- WAVE Web Accessibility Evaluation Tool
- Accessibility Insights
- NVDA screen reader for Windows
- Browser colour contrast checkers
Automated tools are useful, but they cannot identify every accessibility issue. Manual keyboard testing and assistive technology testing are still important.
Examples of accessibility bugs
- A button cannot be reached using the Tab key.
- A keyboard focus indicator is not visible.
- An image containing important information has no alternative text.
- A form field has no accessible label.
- A modal window cannot be closed with the keyboard.
- An error is communicated using colour alone.
- A screen reader announces an incorrect control name.
- Text becomes unreadable when the page is zoomed.
Is automated accessibility testing enough?
No. Automated tools can quickly identify issues such as missing alternative text, invalid markup and some contrast failures.
However, automated testing may not determine whether alternative text is meaningful, whether focus order makes sense or whether instructions are genuinely understandable.
A strong accessibility testing approach combines automated checks, keyboard testing, manual review and testing with assistive technologies.
Final thoughts
WCAG is not simply a checklist. It provides a framework for building digital products that more people can use independently.
QA testers play an important role by identifying accessibility barriers before they affect real users.
Even basic checks such as keyboard navigation, visible focus, clear labels and readable contrast can make a meaningful difference to the quality of an application.