Accessibility Statement.
RedactLabs targets WCAG 2.2 AA for redactlabs.ca and treats accessibility as part of the production quality gate, not a separate retrofit.
Statement date: 2026-10-05
Target: WCAG 2.2 AA.
The target is conformance, not a certification claim. We verify through code review, keyboard checks, and automated Lighthouse audits.
This statement applies to the public redactlabs.ca website. It does not make a blanket certification claim for every third-party service linked from the site or for client work delivered under separate statements of work.
Ontario’s IASR website accessibility requirements under the AODA apply to organizations with 50 or more employees in Ontario. RedactLabs targets WCAG 2.2 AA regardless of that threshold.
What is implemented.
These claims are grounded in the site layout, components, global CSS, motion system, and navigation code.
| Area | Implemented on the site |
|---|---|
| Landmarks | BaseLayout renders a skip link, Header, main content region, and Footer. Header and footer navigation use semantic nav elements and accessible names where needed. |
| Keyboard operation | The mobile menu moves focus into the overlay, traps Tab while open, closes on Escape, returns focus to the trigger, and syncs inert with the hidden state. Forms, buttons, links, tables, and scan results expose focusable controls. |
| Focus states | A global :focus-visible rule draws a 2px outline in the signal colour, the same value as the shared focus-ring token. Form controls, table scroll regions, buttons, and the mobile navigation trigger also define visible focus treatment. |
| Reduced motion | Global CSS, the GSAP/Lenis motion system, particle canvas, buttons, tables, accordion, and form controls honor prefers-reduced-motion. Reduced-motion users get static or already-revealed content instead of animated effects. |
| Contrast tokens | The design token file documents AA-oriented text, muted text, accent, and light-theme contrast decisions; components consume token names rather than one-off colors. |
| Structured controls | The DataTable component uses real table markup with captions and row/column headers. FormField renders explicit labels, described-by wiring, aria-invalid support, and live error regions. |
How we check it.
The repository includes automated Lighthouse checks in the PR quality workflow.
| Practice | Current repository evidence |
|---|---|
| Automated CI audit | The quality workflow runs Lighthouse CI for accessibility, performance, best practices, and SEO on a bounded set of key pages (home, services, pricing, contact, about). Accessibility is asserted as an error at a minimum score of 0.9, so a failing score fails the pull-request check. |
| PR visibility | The same workflow posts Lighthouse per-page scores back to the pull request when reports are available. |
| Manual review | Routes outside the bounded Lighthouse set, interactive states, keyboard flows, and legal/document pages still require human review before release. |
Known constraints.
These are the areas that need continued attention during design and release review.
- Representative audit set
- The automated Lighthouse job covers selected pages, not every route in the site. New or materially changed pages still need manual accessibility review.
- Third-party widgets
- Cloudflare Turnstile is used on form surfaces for bot verification. If the widget creates a barrier, visitors can email contact@redactlabs.ca directly.
- Motion and canvas
- Decorative particle canvases and scroll treatments are enhancements. The code disables or reduces those effects for users who request reduced motion, but motion-heavy changes still need review before release.
Report an accessibility issue.
Accessibility feedback uses the same public enquiry path published on the site.
Email contact@redactlabs.ca with the page URL, device/browser, assistive technology if relevant, and a short description of the barrier.
Accessible formats and communication supports are available on request, at no cost, through contact@redactlabs.ca.
The Trust page publishes a one-business-day acknowledgement target for sales and scoping enquiries; accessibility feedback sent through this public contact path is handled against the same acknowledgement target.