Accessibility statement
This statement covers 153base.ca. We build accessible websites for a living, so it would be poor form not to publish where our own site stands, including the parts that are not finished.
Conformance target
We aim to meet WCAG 2.1 Level AA. We also design against EN 301 549, the accessibility standard referenced in public sector procurement, and Ontario’s obligations under the AODA.
We consider this site partially conformant. Partially conformant means most of the site meets the standard, and the exceptions are listed below rather than left for you to discover.
How this site is built
- Hand-written HTML rather than page-builder output, so heading order, landmark regions and form semantics are deliberate rather than generated.
- Body text at 18px with a 1.65 line height. Nothing on the site is set below 14px.
- Every colour pair is contrast-checked. Body text sits at 17.9:1 against white, and the lowest ratio used for body-size text anywhere is 5.4:1 against a 4.5:1 requirement. One exception, stated rather than hidden: the large figures on the dark band are 3.7:1, which clears the 3:1 WCAG sets for text at that size but would not be acceptable at body size, so it is used nowhere else.
- A two-tone focus ring, so the focused element stays visible against both light and dark surfaces.
- Pointer targets are at least 24 × 24 CSS pixels, most are 44 × 44.
- Motion is limited to a short fade and rise as sections enter the viewport. It is disabled entirely for anyone with
prefers-reduced-motionset, and the animation is built so that content is visible when JavaScript does not run at all. A failed animation can cost you the effect, never the content. - Decorative images carry an empty
altand are hidden from assistive technology. Images that carry meaning get real alt text. - Fonts are self-hosted. The site makes no third-party requests, sets no tracking cookies, and therefore needs no cookie banner.
How we test
Automated checks catch roughly a third of accessibility problems, so they are a floor rather than a verdict. We combine them with manual testing.
- Automated: axe-core against the WCAG 2.0 and 2.1 A and AA rule sets, plus best-practice rules.
- Keyboard: every interactive element reached and operated by keyboard alone, checking focus order, focus visibility, and that focus is never trapped or hidden behind the sticky header.
- Zoom and reflow: 200% zoom with no loss of content or horizontal scrolling.
- Text spacing: increased line height, paragraph, letter and word spacing, checking nothing overlaps or clips.
Measured results
Last audited 6 August 2026. These are figures from an actual run, not estimates, and you are welcome to re-run them yourself.
| Check | Tool | Result |
|---|---|---|
| Accessibility violations | axe-core 4.12.1 | 0 across 35 applicable rules |
| Lighthouse accessibility | Lighthouse 12.8.2 | 100 / 100 |
| Lighthouse performance | Lighthouse 12.8.2 | 100 / 100 |
| Lighthouse best practices | Lighthouse 12.8.2 | 100 / 100 |
| Largest Contentful Paint | Lighthouse 12.8.2 | 0.5 s |
| Cumulative Layout Shift | Lighthouse 12.8.2 | 0 |
| Total Blocking Time | Lighthouse 12.8.2 | 0 ms |
| Page weight | Lighthouse 12.8.2 | 220 KiB across 26 requests |
A perfect automated score is not the same as an accessible site. It means no machine-detectable failures were found. The manual testing above is what the claim actually rests on.
Known limitations
These are the things we know are not right yet.
- Screen reader testing is not yet complete. We have tested with the keyboard throughout, but have not finished a full pass with VoiceOver and NVDA. Until that is done we will not claim full conformance.
- The site is English only. There is no French version, which limits who can use it.
- Some pages are still in progress. Service detail pages and the contact form are being built, and have not been audited.
- No user testing with people with disabilities. Automated tools and our own keyboard testing are not a substitute for this, and we intend to address it.
Tell us if something is wrong
If any part of this site is difficult or impossible for you to use, we want to know. Please email contactus@153base.ca and describe what happened and what you were trying to do.
We will acknowledge your message within one business day and tell you what we intend to do about it, including a timeframe. If you need information from this site in a different format, ask and we will provide it.
Technical information
This site relies on HTML, CSS, JavaScript and SVG. It is built to work when JavaScript is unavailable, apart from the mobile navigation menu.
Statement prepared 6 August 2026 and based on testing carried out by 153 Base Solutions Inc. We review it whenever the site changes materially, and at minimum every six months.