Accessibility commitment & Accessibility Statement
WCAG 2.1 AA web development. From day one.
Mosaic Ridge LLC engineers every site to WCAG 2.1 Level AA conformance — not as an end-of-project remediation pass, but as the engineering baseline from the first commit.
For public-sector engagements we deliver against Section 508 standards and issue an Accessibility Conformance Report (ACR / VPAT) at project closeout. Section 508 documentation is included at no additional cost.
The direct answer
Every Mosaic Ridge site is WCAG 2.1 AA conformant.
Accessibility is engineered into a Mosaic Ridge build from the first commit — not retrofitted at the end. Semantic HTML, keyboard-navigable components, visible focus indicators, accessible form labels, sufficient color contrast, and screen-reader-tested interactions are baseline deliverables on every tier from Foothold to Summit.
There is no “accessibility upgrade” we sell on top of the published tier price. WCAG 2.1 AA conformance is included at $1,800, at $7,500, and on Custom-scoped engagements alike. The same engineering posture applies whether the contract is a regional retailer or a state agency.
For procurement and public-sector engagements, we issue a full Accessibility Conformance Report (ACR) aligned with the ITI VPAT 2.5 template at project closeout — also at no additional cost.
What WCAG 2.1 AA covers
Four principles. Fifty success criteria.
WCAG 2.1 Level AA conformance means meeting 50 specific success criteria from the W3C Web Content Accessibility Guidelines, organized under four principles. In practice for a Mosaic Ridge build, each principle translates to concrete engineering practices.
- Perceivable
- Text alternatives for non-text content. Captions for media. Color contrast at or above 4.5:1 for body text, 3:1 for large text. Content not conveyed by color alone.
- Operable
- Full keyboard navigation with no keyboard traps. Visible focus indicators on every interactive element. No content that flashes more than three times per second. Skip links to main content.
- Understandable
- Predictable navigation order. Form fields labeled and errors clearly communicated. Page language declared. Consistent layout patterns across the site.
- Robust
- Markup parses cleanly across assistive technologies. ARIA used correctly and sparingly — preferring semantic HTML first. Tested against NVDA, VoiceOver, and JAWS.
Testing methodology
How we test
Every project we ship is reviewed using a combination of automated tooling and manual review. Automated tools catch roughly 30–40% of WCAG violations; manual screen-reader and keyboard testing catches the rest.
- axe-core (automated rule-based testing)
- Lighthouse (Chromium accessibility audits)
- Manual keyboard navigation review
- Screen reader walkthroughs (NVDA on Windows, VoiceOver on macOS / iOS)
- Color-contrast verification against WCAG 2.1 AA thresholds
Coverage checklist
What we test for
The checklist below maps to the WCAG 2.1 AA success criteria a procurement-grade auditor would verify. Every build is reviewed against every item before launch.
- Keyboard navigation and focus order
- Visible focus indicators on every interactive element
- Screen-reader compatibility with semantic HTML and ARIA
- Color contrast: ≥4.5:1 for body text, ≥3:1 for large text
- Form labels, error states, and submission feedback
- Alt text on meaningful images and aria-hidden on decorative ones
- Heading hierarchy and document landmarks
- Motion reduction for users with `prefers-reduced-motion`
Procurement deliverables
Public-sector engagements
For state, local, and educational clients, we deliver against Section 508 standards as a contract requirement. On request, we provide:
Accessibility Conformance Report (ACR)
Project-closeout report mapped to WCAG 2.1 AA success criteria with documented conformance levels.
Voluntary Product Accessibility Template (VPAT)
ITI VPAT 2.5 template populated against Section 508 standards where applicable.
Remediation plan for known issues
Documented timeline for any non-conformant items identified during testing, with criticality ratings.
Our own engineering posture
This site.
The Mosaic Ridge marketing site (mosaicridge.com) is built to the same WCAG 2.1 AA standard we apply to client work. We use Next.js with semantic HTML, keyboard-navigable components, skip-to-content links, and tested screen-reader compatibility.
If you encounter an accessibility barrier on this site, we consider that a defect and want to fix it. Use the contact method below; we aim to acknowledge reports within five business days and remediate confirmed issues on a documented timeline.
Frequently asked
Common questions about accessibility.
- What does WCAG 2.1 AA conformance actually mean for our site?
- WCAG 2.1 Level AA is the international standard for web accessibility maintained by the W3C. Conformance means the site meets 50 specific success criteria covering four principles: content must be perceivable (text alternatives, captions, sufficient color contrast), operable (full keyboard navigation, no seizure-triggering content), understandable (predictable layout, clear error messages), and robust (parses correctly across assistive technologies). In practice for a Mosaic Ridge build, that means semantic HTML, visible focus indicators on every interactive element, color contrast at or above 4.5:1 for body text, accessible form labels, and tested compatibility with NVDA and VoiceOver screen readers.
- What's the difference between WCAG, Section 508, and the ADA?
- WCAG (Web Content Accessibility Guidelines) is the international technical standard. Section 508 is the federal procurement standard for U.S. government IT — it adopts WCAG 2.0 AA criteria by reference and adds federal-specific provisions. The ADA (Americans with Disabilities Act) is the civil rights law; courts have increasingly interpreted Title III to require WCAG 2.1 AA conformance for public-facing websites of businesses considered places of public accommodation. We build to WCAG 2.1 AA, which is the most rigorous of the three, and deliver Section 508 conformance documentation for public-sector clients on request. We do not provide legal advice on ADA Title III exposure — that's a question for counsel.
- Do you deliver an Accessibility Conformance Report (ACR) or VPAT?
- Yes. For public-sector engagements and any client that requests it, we issue an Accessibility Conformance Report aligned with the ITI VPAT 2.5 template at project closeout. The ACR documents each WCAG 2.1 AA success criterion, our conformance level (Supports, Partially Supports, Does Not Support, Not Applicable), and remarks where remediation is planned or impossible. There is no additional cost for ACR/VPAT delivery on procurement engagements.
- Is every Mosaic Ridge build WCAG 2.1 AA, or only the procurement ones?
- Every build. We don't have a separate 'commercial' tier with weaker accessibility — the same engineering standards apply whether the client is a regional retailer or a state agency. The ACR/VPAT documentation is only produced on request because most commercial clients don't need formal conformance paperwork, but the underlying engineering is identical.
- Do you test with real screen readers, or just automated tools?
- Both, in that order. Automated tools (axe-core, Lighthouse) catch roughly 30-40% of WCAG violations — useful but insufficient. Every site we ship is also walked through with NVDA on Windows and VoiceOver on macOS / iOS, with the keyboard as the only input device, to verify the experience for actual assistive-technology users. Automated tools cannot detect a confusing navigation flow or an unhelpful aria-label; humans can.
- What if our existing site fails an accessibility audit?
- We scope remediation work as a Custom engagement. The first step is a documented audit — we run automated tooling, manually test with assistive technology, and produce a prioritized issue list mapped to the failing WCAG criteria. From there, remediation is either a fixed-price scope (for sites with a contained set of issues) or a rebuild recommendation (for sites where the underlying CMS or template architecture makes per-issue remediation more expensive than rebuilding on Next.js). We'll tell you honestly which one applies.
- How long does an accessibility-focused project take?
- A new build at WCAG 2.1 AA conformance does not take longer than a non-accessible build of the same scope — accessibility is engineered in from the first commit, not bolted on at the end. Foothold builds ship in 2-3 weeks, Ridgeline in 3-4, Storefront and Summit in 4-6, all to WCAG 2.1 AA. Remediation of an existing site varies with the depth of the issues; an audit + estimate takes 5-10 business days.
- Is accessibility an extra cost on top of the tier price?
- No. WCAG 2.1 AA conformance is included in every Mosaic Ridge tier — Foothold through Summit — at the published price. ACR/VPAT documentation is also included at no additional cost on procurement engagements. The cost of doing accessibility correctly from day one is negligible compared to retrofitting it later, which is why we build it in by default rather than charging for it as a premium.
Report an accessibility issue
Email hello@mosaicridge.com with the URL, the assistive technology you were using (browser, screen reader, OS), and a short description of the barrier you encountered. We will acknowledge within five business days.
For procurement evaluators: detailed accessibility documentation, ACR / VPAT samples, and policy references are available on request as part of vendor due diligence. Contact us via the contact form or directly by phone or email.
Procurement-ready engineering
Tell us what you're scoping.
A new public-facing site. A services portal. A custom internal tool. Send the brief and we'll respond within one business day — with ACR / VPAT samples attached on request.