Summary:
- The WCAG 2.1 AA checklist contains 50 success criteria across four categories (POUR) — all must be met for BFSG compliance.
- Violations in Austria are penalized with up to €80,000 (companies) or €7,200 (sole traders); SMS enforcement inspections begin in 2026.
- The free automated check at BFSG-Scan.at reviews your website against the most important WCAG 2.1 AA criteria in 60 seconds.
---
What Is the WCAG 2.1 AA Checklist?
The WCAG 2.1 AA checklist summarizes all 50 success criteria your website must meet to be considered accessible under Austria's Barrierefreiheitsstärkungsgesetz (BFSG). WCAG stands for Web Content Accessibility Guidelines — an international standard by the W3C.
Since 28 June 2025, the BFSG applies to all businesses and service providers in Austria offering digital products or services. Violations can result in fines of up to €80,000 (companies) or €7,200 (sole traders) (§22 BFSG).
The criteria follow four POUR principles: Perceivable, Operable, Understandable, Robust.
---
Principle 1: Perceivable
All content must be presented in a way that users can perceive — regardless of sensory limitations.
- [ ] 1.1.1 Non-text Content (A): Images, icons and graphics have descriptive alt texts
- [ ] 1.2.1 Audio-only and Video-only (A): Recorded audio/video content has text alternatives or transcripts
- [ ] 1.2.2 Captions (Prerecorded) (A): Recorded videos have captions
- [ ] 1.2.3 Audio Description (A): Videos have audio description or full text alternative
- [ ] 1.2.5 Audio Description (AA): Prerecorded video has audio description for visual information
- [ ] 1.3.1 Info and Relationships (A): Structure and relationships are programmatically determined (headings, lists, tables correctly marked up)
- [ ] 1.3.2 Meaningful Sequence (A): Reading order of content is correct
- [ ] 1.3.3 Sensory Characteristics (A): Instructions do not rely solely on shape, color, size or position
- [ ] 1.4.1 Use of Color (A): Color is not the only means of conveying information
- [ ] 1.4.3 Contrast (Minimum) (AA): Text has a contrast ratio of at least 4.5:1 (large text: 3:1)
---
Principle 2: Operable
All functionality must be operable without a mouse — e.g. by keyboard alone.
- [ ] 2.1.1 Keyboard (A): All functionality is accessible via keyboard
- [ ] 2.1.2 No Keyboard Trap (A): Users can navigate away from any component using keyboard
- [ ] 2.2.1 Timing Adjustable (A): Time limits can be extended or disabled
- [ ] 2.2.2 Pause, Stop, Hide (A): Moving, blinking or scrolling content can be paused
- [ ] 2.3.1 Three Flashes or Below Threshold (A): No content flashes more than three times per second
- [ ] 2.4.1 Bypass Blocks (A): Repeated navigation blocks can be skipped (skip links)
- [ ] 2.4.2 Page Titled (A): Every page has a unique, descriptive title
- [ ] 2.4.3 Focus Order (A): Focus order is logical and meaningful
- [ ] 2.4.4 Link Purpose (In Context) (A): Every link is understandable from its text or context
- [ ] 2.4.7 Focus Visible (AA): Keyboard focus indicator is visible
---
Principle 3: Understandable
Content and operation must be understandable for all users.
- [ ] 3.1.1 Language of Page (A): HTML document has the correct
langattribute (e.g.lang="en") - [ ] 3.1.2 Language of Parts (AA): Passages in other languages are marked up
- [ ] 3.2.1 On Focus (A): No automatic context changes on focus
- [ ] 3.2.2 On Input (A): No automatic context changes on input
- [ ] 3.2.3 Consistent Navigation (AA): Navigation is consistent across all pages
- [ ] 3.2.4 Consistent Identification (AA): Same functions are named consistently
- [ ] 3.3.1 Error Identification (A): Form error messages are clear and descriptive
- [ ] 3.3.2 Labels or Instructions (A): Form fields have clear labels or instructions
---
Principle 4: Robust
Content must work with current and future technologies — including assistive technologies.
- [ ] 4.1.1 Parsing (A): HTML is valid (no duplicate IDs, correct nesting)
- [ ] 4.1.2 Name, Role, Value (A): All UI components have correct ARIA roles, names and properties
- [ ] 4.1.3 Status Messages (AA): Status messages (e.g. "Saved") are programmatically communicated
---
Most Common Failures According to WebAIM 2024
The annual WebAIM Million Report analyzes one million websites. 2024 results:
| Rank | Failure | Affected Websites |
|---|---|---|
| 1 | Low color contrast | 81.0% |
| 2 | Missing image alt text | 54.5% |
| 3 | Missing form labels | 48.6% |
| 4 | Missing button text | 27.5% |
| 5 | Missing document language | 17.1% |
| 6 | Missing link text | 15.9% |
These six failures alone cover the most common WCAG 2.1 AA violations and can be detected automatically.
---
Checklist in Practice: How to Use It
The WCAG 2.1 AA checklist is a tool — not an end in itself. Here's how to proceed:
1. Run an automated scan: Tools like BFSG-Scan.at detect 30–40% of all errors — fast and free.
2. Add manual tests: Navigate through your site using the Tab key. Test with a screen reader (NVDA/Windows, VoiceOver/Mac).
3. Set priorities: Start with the most common errors (contrast, alt texts, labels).
4. Document: Keep your WCAG conformance statement up to date — it is mandatory under BFSG.
5. Set up monitoring: Accessibility is not a one-time project. New content can introduce new errors.
> Legal note: Under §22 BFSG, violations in Austria can result in fines of up to €80,000 for companies and €7,200 for sole traders. Regular checks protect against penalties.
---
Automated Checking with BFSG-Scan.at
Instead of going through the checklist manually, you can have your website checked automatically in 60 seconds:
- Free quick check: 5 pages, instant report with the most common errors
- Full audit (€449): All pages, detailed PDF report, WCAG 2.1 AA conformance assessment
- Monitoring (€99/month): Weekly automated checks, alerts for new errors
BFSG-Scan automatically checks for contrast, alt texts, labels, document language, ARIA roles and more — and delivers prioritized recommendations directly for your development team.