<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible-ovjbz0bbc" -->

---
title: 5 reasons why WCAG AA compliance does not mean your...
description: Meeting WCAG 2.2 AA compliance does not guarantee an accessible or usable website, because WCAG's scope is limited to preventing disadvantage for people with...
canonical: https://daily.dev/posts/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible-ovjbz0bbc
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: 5 reasons why WCAG AA compliance does not mean your website is accessible | daily.dev
og:description: Meeting WCAG 2.2 AA compliance does not guarantee an accessible or usable website, because WCAG's scope is limited to preventing disadvantage for people with...
og:url: https://daily.dev/posts/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible-ovjbz0bbc
og:image: https://api.daily.dev/og/posts/OvJbz0bbc.png
og:image:alt: 5 reasons why WCAG AA compliance does not mean your website is accessible
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 5 reasons why WCAG AA compliance does not mean your website is accessible

**[Craig Abbott](https://daily.dev/sources/craigabbott)** · 8 min read · 0 upvotes · 0 comments

## Summary

Meeting WCAG 2.2 AA compliance does not guarantee an accessible or usable website, because WCAG's scope is limited to preventing disadvantage for people with impairments, not ensuring good user experience. Five concrete gaps are outlined: the use-of-color criterion only applies when color conveys information, so unstyled links can pass while being indistinguishable from text; there is no minimum font-size requirement, so text could technically be unreadably small yet still pass contrast and resize checks; timing criteria only cover deliberately timed UI elements, not slow page loads caused by network or server issues; readability-related success criteria (unusual words, reading level, pronunciation) are AAA rather than AA, so overly complex language can still pass; and audio quality issues like static or distortion don't fail WCAG AA as long as a transcript alternative exists. The piece argues WCAG AA should be seen as a measurable baseline rather than proof of full accessibility.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.craigabbott.co.uk/blog/2025/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible>

## Questions this post answers

### Does WCAG 2.2 have a minimum font-size requirement?

No, WCAG 2.2 does not define a minimum font-size. Text only needs to meet a 4.5:1 contrast ratio under success criterion 1.4.3 for small text, and must be resizable to 200% without losing content or functionality under 1.4.4 Resize Text. Text could technically be set at 1 pixel and still pass both criteria as long as it can scale to 2 pixels without breaking layout or content.

_Teams auditing real accessibility gaps beyond checkbox compliance can track guidance like this on daily.dev._

### Can a website fail to be usable due to slow loading times and still pass WCAG 2.2 AA?

Yes, slow loading times are not covered by WCAG's timing criteria. Success criterion 2.2.1 Timing Adjustable only addresses deliberately timed interface elements such as session timeouts or keyboard shortcuts, not network latency, database inefficiencies, or server speed. A page that takes 30 seconds to load could still pass WCAG 2.2 AA because the poor experience is equal for all users regardless of impairment.

_Developers weighing performance against compliance checklists can follow this kind of nuance on daily.dev._

### Are readability requirements like reading level and avoiding unusual words mandatory under WCAG 2.2 AA?

No, readability-focused success criteria such as 3.1.3 Unusual Words, 3.1.5 Reading Level, and 3.1.6 Pronunciation are all classified as level AAA, not AA. Since level AA is the only level typically mandated by legislation, content can be dense, jargon-heavy, or hard to understand while still fully complying with WCAG 2.2 AA, as long as language attributes are set correctly in code.

_Content and UX teams balancing legal compliance with real readability can track these distinctions on daily.dev._

## Similar posts on daily.dev

- [How to Build More Accessible Websites with WCAG 2.2](https://daily.dev/posts/how-to-build-more-accessible-websites-with-wcag-2-2-ionjqlod0) · freeCodeCamp · 2 upvotes · 0 comments
- [You Can’t Make Something Accessible to Everyone](https://daily.dev/posts/you-can-t-make-something-accessible-to-everyone-7c2srzhwu) · Adrian Roselli · 57 upvotes · 7 comments
- [Hidden Web Accessibility Issues Most Designers Miss in 2026](https://daily.dev/posts/hidden-web-accessibility-issues-most-designers-miss-in-2026-gm6w0zamx) · Netguru · 0 upvotes · 0 comments
- [If It's Not Accessible, It's Not Design](https://daily.dev/posts/if-it-s-not-accessible-it-s-not-design-eyj1yetec) · DEV · 3 upvotes · 0 comments

---

Tags: [#webdev](https://daily.dev/tags/webdev), [#ux](https://daily.dev/tags/ux), [#accessibility](https://daily.dev/tags/accessibility)

[View this post on daily.dev](https://daily.dev/posts/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible-ovjbz0bbc)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"5 reasons why WCAG AA compliance does not mean your website is accessible","url":"https://daily.dev/posts/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible-ovjbz0bbc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible-ovjbz0bbc"},"datePublished":"2026-09-20T07:43:54.344Z","dateModified":"2026-09-20T07:47:11.430Z","description":"Meeting WCAG 2.2 AA compliance does not guarantee an accessible or usable website, because WCAG's scope is limited to preventing disadvantage for people with...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8164672c2ea6eb4872ff17f2a17235a7?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8164672c2ea6eb4872ff17f2a17235a7?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Craig Abbott","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Craig Abbott","logo":"https://media.daily.dev/image/upload/s--7L_KxzEH--/f_auto,q_auto/v1789890198/logos/craigabbott?_a=BAMAMicg0","url":"https://daily.dev/sources/craigabbott"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible-ovjbz0bbc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"webdev,ux,accessibility","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Craig Abbott","item":"https://daily.dev/sources/craigabbott"},{"@type":"ListItem","position":3,"name":"5 reasons why WCAG AA compliance does not mean your website is accessible"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/5-reasons-why-wcag-aa-compliance-does-not-mean-your-website-is-accessible-ovjbz0bbc#faq","mainEntity":[{"@type":"Question","name":"Does WCAG 2.2 have a minimum font-size requirement?","acceptedAnswer":{"@type":"Answer","text":"No, WCAG 2.2 does not define a minimum font-size. Text only needs to meet a 4.5:1 contrast ratio under success criterion 1.4.3 for small text, and must be resizable to 200% without losing content or functionality under 1.4.4 Resize Text. Text could technically be set at 1 pixel and still pass both criteria as long as it can scale to 2 pixels without breaking layout or content. Teams auditing real accessibility gaps beyond checkbox compliance can track guidance like this on daily.dev."}},{"@type":"Question","name":"Can a website fail to be usable due to slow loading times and still pass WCAG 2.2 AA?","acceptedAnswer":{"@type":"Answer","text":"Yes, slow loading times are not covered by WCAG's timing criteria. Success criterion 2.2.1 Timing Adjustable only addresses deliberately timed interface elements such as session timeouts or keyboard shortcuts, not network latency, database inefficiencies, or server speed. A page that takes 30 seconds to load could still pass WCAG 2.2 AA because the poor experience is equal for all users regardless of impairment. Developers weighing performance against compliance checklists can follow this kind of nuance on daily.dev."}},{"@type":"Question","name":"Are readability requirements like reading level and avoiding unusual words mandatory under WCAG 2.2 AA?","acceptedAnswer":{"@type":"Answer","text":"No, readability-focused success criteria such as 3.1.3 Unusual Words, 3.1.5 Reading Level, and 3.1.6 Pronunciation are all classified as level AAA, not AA. Since level AA is the only level typically mandated by legislation, content can be dense, jargon-heavy, or hard to understand while still fully complying with WCAG 2.2 AA, as long as language attributes are set correctly in code. Content and UX teams balancing legal compliance with real readability can track these distinctions on daily.dev."}}]}
```

