We build to WCAG 2.1 AA.
Accessibility is a default in everything we ship for clients — and we hold this site to the same standard. Software that excludes people isn't finished. This statement explains how we approach it.
What we build to, on this site and yours.
Semantic structure
Pages use proper landmarks and a logical heading order, so screen readers and assistive tech can navigate them predictably.
Keyboard navigation
Every interactive element is reachable and operable by keyboard alone, with a visible skip-to-content link and clear focus states.
Colour contrast
Text and meaningful UI are designed to meet WCAG 2.1 AA contrast ratios across our interface.
Text alternatives
Meaningful images carry descriptive alt text; decorative images are marked as decorative so they don't add noise.
Respecting preferences
We honour reduced-motion preferences and avoid motion that could trigger discomfort.
Bilingual delivery
For client projects we build full English/French parity into the architecture, so accessibility extends across both official languages.
Found a barrier? Tell us.
We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Accessibility is an ongoing effort, and no site is ever perfectly done — if something on this site gets in your way, we want to fix it.
Email eric@usebluestone.com with the page and a short description of the problem, and we'll respond and work to resolve it.
Building accessible software for a public body? See how we work with the public sector.