WCAG A – The Minimum Requirements of Accessibility Explained
WCAG A – also called WCAG Level A – is the lowest of the three conformance levels of the Web Content Accessibility Guidelines. WCAG A defines the absolute minimum requirements for the accessibility of a website. Without meeting WCAG A, digital content is effectively unusable for many people with disabilities. Level A thus forms the foundation on which the higher conformance levels WCAG AA and WCAG AAA are built.
In the current version WCAG 2.2, WCAG A includes around 30 success criteria that every website must fulfill. These criteria address the most fundamental barriers: missing alternative texts, functions that cannot be operated via keyboard, missing language labels, or flashing content that can trigger epileptic seizures. WCAG A is the minimum below which a website is considered non-accessible.
It is important to understand: WCAG A alone is sufficient neither for user satisfaction nor for legal compliance. The Barrierefreiheitsstärkungsgesetz (BFSG) and the European Accessibility Act (EAA) require at least WCAG AA. Anyone who only achieves WCAG A has only overcome the absolute entry barrier – a fully accessible website looks different.
WCAG A at a Glance
- Conformance Level: Lowest of three levels (A, AA, AAA) within WCAG.
- Number of Criteria: Around 30 success criteria in WCAG 2.2 at Level A.
- Goal: Basic accessibility – minimum requirement for use by people with disabilities.
- Legal Significance: WCAG A alone is not enough – the legal requirement in Germany is WCAG AA.
The Most Important WCAG A Success Criteria
The Level A criteria of WCAG are distributed across the four POUR principles (Perceivable, Operable, Understandable, Robust). Here are the key requirements that every website must meet at Level A:
- 1.1.1 Non-Text Content: Every image, graphic, and non-textual element needs alternative text for screen readers.
- 1.3.1 Info and Relationships: Structure and relationships in the content must be semantically labeled (headings, lists, tables).
- 2.1.1 Keyboard: All functions must be operable via keyboard – without a mouse.
- 2.1.2 No Keyboard Trap: Users must not be "trapped" in components when using the keyboard.
- 2.3.1 Three Flashes: Content must not flash more than three times per second (protection against seizures).
- 3.1.1 Language of Page: The main language must be labeled in the HTML code (lang="en").
- 4.1.2 Name, Role, Value: All user interface components must be correctly identifiable for assistive technologies.
Who Relies on WCAG A?
WCAG A addresses barriers that would mean complete exclusion for certain user groups – not just a difficulty. Blind people rely on alt texts (1.1.1) because without them, they cannot perceive anything. People with motor impairments need keyboard accessibility (2.1.1) because they cannot use a mouse. Users with photosensitive epilepsy must be protected from flashing content (2.3.1).
This makes WCAG A the non-negotiable basis: whoever violates Level A criteria excludes entire user groups completely. While the higher levels WCAG AA and WCAG AAA gradually make usage more comfortable, WCAG A prevents exclusion from usage in the first place.
Checking WCAG A: Tools and Process
WCAG A can be checked automatically to a large extent because many Level A criteria are technically measurable: Are alt attributes missing? Is the language declared? Is there a semantic structure? Automated accessibility scanners reliably detect these problems. About 70 percent of all WCAG A violations can be identified this way – significantly more than at the higher levels.
The remaining 30 percent concern criteria that require human judgment: Is an alt text meaningfully formulated or just mechanically present? Does the tab order make logical sense? Here, manual tests with screen readers like NVDA or VoiceOver are indispensable.
SiteCockpit Solution
Automatically Check WCAG A with easyMonitoring
With easyMonitoring, you automatically test your website against all Level A criteria of WCAG 2.2. The tool scans for missing alt texts, keyboard issues, language markup, and other basic barriers – and provides prioritized task lists. After the WCAG A foundation, the path leads logically to WCAG AA, the legally required standard.
Discover easyMonitoring →From WCAG A Foundation to Full Conformance
WCAG A is never the end goal, but the starting point. After fulfilling the Level A criteria, work follows on WCAG AA – the actual industry standard. WCAG AA complements the 30 A criteria with around 20 additional requirements, such as color contrasts, responsive design, and error handling in forms. Only WCAG AA meets the requirements of the BFSG.
The highest level WCAG AAA is aimed at specialized areas of application such as government portals or services for people with severe disabilities. AAA is often not achievable across the board because some criteria conflict with common design principles. The realistic path for most companies: WCAG A as a foundation, WCAG AA as the target standard.
Frequently Asked Questions about WCAG A
Is WCAG A legally sufficient?
No. The BFSG requires at least WCAG AA. WCAG A alone does not make your website BFSG-compliant – it is only the absolute minimum level of accessibility.
How many criteria does WCAG Level A have?
WCAG 2.2 defines around 30 success criteria at Level A, distributed across the four principles: perceivable, operable, understandable, and robust.
What happens if I do not fulfill WCAG A?
Without WCAG A, many users with disabilities are completely excluded from your website. In addition, there is a risk of legal warnings and fines under the BFSG.
How long does it take to implement WCAG A?
This depends on the initial state. For cleanly developed websites, many Level A criteria are already met. Typical implementation times range between two weeks and three months for medium-sized websites.
Check Your Website's WCAG A Status
Does your website meet the minimum requirements of WCAG Level A? Test it now for free with easyMonitoring by SiteCockpit.
Test for free