WCAG 2.2 AA is how we work — not a separate audit phase.
Every site FlowMint builds and every change we ship is reviewed against WCAG 2.2 AA standards as part of our default workflow. Accessibility isn't a service line you buy or a phase you sequence — it's the baseline every engagement runs on.
Built into every phase, not bolted on at launch.
Accessibility reviewed late is accessibility done expensively. We catch issues at each phase, where remediation is cheapest and most effective.
Design review
Color contrast, focus indicators, text sizing, and visual hierarchy reviewed before any code is written.
Build review
Semantic HTML, keyboard navigation, focus management, and ARIA patterns reviewed during implementation, not after.
Content review
Heading structure, link text, alt text, plain-language writing, and reading-level considerations as content is added.
Post-launch review
Every significant change in the stewardship phase runs through the same accessibility review — including content updates by staff.
What WCAG 2.2 AA review actually looks like.
These are the specific checks that run on every page we ship, and re-run when changes affect them. The list isn't exhaustive — it's representative of how we work.
Semantic HTML structure with correct heading hierarchy
Keyboard navigation across every interactive element
Visible focus indicators that meet 2.2 AA contrast and size requirements
Color contrast meeting 4.5:1 for body text and 3:1 for large text and UI components
Screen-reader testing on key user paths (homepage, forms, navigation, key program pages)
Form labels, error messaging, and validation patterns that work for assistive technology
Alt text on meaningful images, decorative-image markup on the rest
Text resizing to 200% without loss of content or function
Reduced-motion preferences honored across animations and interactions
Skip links and landmark regions for keyboard and screen-reader users
Accessibility considerations WCAG doesn't fully cover.
Standards conformance is the floor, not the ceiling. There are accessibility considerations the spec doesn't fully address but that real audiences need.
Plain-language content
Heading and body copy written for the reading level your actual audience uses — not the reading level the writer is comfortable with.
Low-bandwidth performance
Sites that work on slow connections, on older devices, in places where bandwidth is metered or unreliable.
Mobile accessibility
Touch targets sized for thumbs, responsive layouts that don't break navigation, content prioritized for small-screen reading.
Accessible form workflows
Inquiry, donation, and intake forms that work for assistive technology end-to-end — not just at the field level but across multi-step flows and confirmations.
What we don't claim to be.
Accessibility is too important to overclaim. There's specific scope we don't offer — and the honest framing is that recognizing it is part of taking accessibility seriously.
Not a third-party accessibility audit
For organizations that need an independent VPAT or formal third-party WCAG conformance report, a dedicated accessibility consultancy is the right partner. Our work is implementation review, not certification.
Not a legal compliance guarantee
ADA and Section 508 compliance involve legal interpretation we're not qualified to make. We implement against WCAG 2.2 AA standards; an attorney provides legal opinion.
Not a substitute for community testing
The most valuable accessibility validation comes from real users with disabilities testing your site. We can help facilitate that; we can't replace it.
Accessibility-aware partner for your next engagement?
If accessibility is a priority for your organization — by mission, by funder requirement, by regulation, or simply because it's the right way to build — we'd welcome the conversation.