We built this site to meet WCAG 2.2 Level AA.
The places our clients run are open to everyone, and we hold our own front door to the same standard. We tested every page of this site against version 2.2 of the Web Content Accessibility Guidelines (WCAG) at Level AA on October 7, 2026.
We explain how we build accessible websites for clients on our accessibility page.
We ran these tests before publishing this statement.
- axe-core 4.11 checked all 15 pages against WCAG 2.2 Levels A and AA at desktop and phone widths and found no failures.
- Lighthouse gave every page an accessibility score of 100 on a simulated phone.
- The W3C’s Nu HTML Checker found no errors in the markup of any page.
- On every page we moved through the first forty stops with only a keyboard, and each one showed a focus indicator.
- Every page reflows to a width of 320 pixels without sideways scrolling and keeps its layout at 200 percent zoom.
- We loaded every page again with reduced motion and then with forced colours switched on in Chrome.
- Screen reader testing with VoiceOver on a Mac and an iPhone comes next, and its results will join this list.
You can change how this site looks and moves.
The Settings button at the top of every page opens a panel where you can switch on dark mode or high contrast. It also sets the text in one of three sizes and can widen its spacing to the values in WCAG 1.4.12. Underlined links and a page without motion are each one switch away, and Reset puts everything back.
Your browser keeps these choices on your device, so they carry from page to page without a cookie. If your device already asks for reduced motion, the site follows it.
We publish every failure our tests find.
As of October 7, 2026, our tests have found no failures against WCAG 2.2 Level AA.
We hold client websites to the same standard.
Accessibility shapes a project from the first sketch, because a website for a public place should welcome everyone who wants to visit. We check every colour pairing for contrast before we design a page, and each component’s specification sets its focus state and a touch target big enough for a thumb.
Every feature we build carries written acceptance criteria for accessibility. Automated checks scan each template, and then one of us works through it with a keyboard and a screen reader before launch. The editing tools we set up keep headings in order and ask for alternative text whenever someone adds an image.
We caption every video and add transcripts to longer films. Where a client needs accessible tours, we build them to work with a keyboard and describe each space in text.
Tell us if something doesn’t work.
If any part of this site is hard to use, email info@wearethestill.ca. It helps to name the page and describe what got in your way, and one of us will write back.
We last reviewed this statement on October 7, 2026.