Hey PH community! Quick update from the AccessGuard team.
WCAG 2.2 added 9 new success criteria back in October 2023, but most automated scanners still only catch one or two of them and mark the rest as "manual review required." We just shipped full automated coverage for all 9.
Hey PH community! I am launching AccessGuard on March 2 - an AI-powered WCAG scanner that gives developers production-ready code fixes. Building this has been a deep dive into the accessibility space, and one thing I have noticed is that most teams want to do the right thing but hit real friction. Whether it is translating cryptic WCAG guidelines into actual code changes, figuring out which issues to fix first, or just finding a workflow that does not feel like a chore - there are a lot of pain points. I would love to hear from this community before launch:
What is the hardest part of making your site accessible?
Do you use any accessibility tools today? What do you wish they did better?
If you could fix one thing about the accessibility workflow, what would it be?
How do you handle alt text for images? Drop your thoughts below - genuinely curious what the biggest blockers are for teams trying to ship accessible products.
