Skip to content
01Accessibility

Accessibility

A site should work for everyone, however they use it. Here is our commitment, what we do to meet it, and how to tell us when something gets in your way.

Last updated: 2026

This statement covers the accessibility of the Scriptus website and the standard we hold the work we deliver to. It is written plainly, with the technical detail in the smaller notes.

01Commitment

Built in, not bolted on

We believe a site or app should work for everyone, however they use it — with a mouse, a keyboard, a screen reader, a phone, or with motion turned off. Accessibility is part of how we build, not a box we tick at the end.

We aim to meet WCAG 2.2 Level AA — a widely recognised standard for accessible digital products — across this site and the work we deliver for clients.

02What we do

How we get there

On every project, we treat the basics as non-negotiable:

  • Everything works with a keyboard alone, in a sensible order, with a visible focus indicator.
  • Text has enough contrast against its background to be read comfortably.
  • Content is structured so screen readers can announce it correctly.
  • Motion and animation respect the “reduce motion” setting on your device.
  • Images, controls, and forms carry the labels assistive technology needs.
Under the hood

Semantic HTML and ARIA only where it adds meaning, full keyboard operability with managed focus, WCAG contrast ratios enforced in the design tokens, components tested with a screen reader, and a site-wide prefers-reduced-motion gate on every animation.

03Ongoing work

Honest about the gaps

Accessibility is never “finished” — standards evolve, and real people use products in ways no checklist predicts. We treat accessibility issues as bugs: when we find one, or you report one, we fix it.

If part of this site is not working for you today, that is on us to put right — please tell us (below) and we will.

04Third parties

Content we do not control

Some pages may include content or tools provided by other companies — for example an embedded map or a third-party form. We choose accessible providers where we can, but we cannot guarantee parts we do not build or control. If one of them blocks you, let us know and we will look for an alternative.

05Contact

Tell us about a barrier

If anything on this site is hard or impossible to use, email us at hello@scriptus.ca — tell us what happened and what you were trying to do. A real person reads it, and we will work to fix it and find you a way through in the meantime.