Just because something passes WCAG (Web Content Accessibility Guidelines) doesn't mean it actually works for everyone.
The main issue is that WCAG conformance is basically about meeting legal requirements, not about inclusion. You can check all the boxes for WCAG 2.2 Level AA and still have a website that's frustrating or impossible for many people to use.
The WCAG doesn't cover everything
Even if you meet the highest level (AAA), there are still accessibility barriers that aren't addressed in the guidelines. The cognitive and learning disability areas are especially lacking.
For example, you might have a multi-step checkout process that's technically accessible. But people with memory impairments or processing delays are screwed if they have to remember information from step 1 when they're on step 5. The guidelines don't tackle cognitive load across time.
The WCAG ignores usability
Your site might be technically keyboard-accessible but use weird key combinations that nobody expects. Or maybe the focus indicator disappears too quickly for someone with attention issues to notice. Technically compliant, but still unusable.
Your settings page might have perfect contrast and keyboard navigation. But if it's cluttered with dozens of options then it's still basically unusable by anyone who isn't an expert.
WCAG doesn't guarantee accessibility
Things like confusing layouts, bad heading structure or complex tables can make a site hell to navigate with a screen reader, even if it passes WCAG tests.
When your contact page has a phone number as the only way for your customers to get in touch with you, you might be compliant. But someone with a hearing or speech disability will still not be able to use your product.
Stop asking "does this meet WCAG?"
Instead, you should be asking "can people actually use this?"
Now you're thinking about including everyone. Compliance asks "are we legally covered?" while inclusion asks "does this actually work for people?" Compliance might protect you from lawsuits. But it's inclusion that creates better experiences for people.
And the only way to really know if something is a better experience is to test it with actual users.
Bottom line: WCAG is a starting point, not a finish line.