Accessibility.
What we have built, what we know is not right yet, and where to tell us when something does not work for you.
Last updated
. This is the version in force. Anything we change appears here with a new date.
01
Where we stand
We want this page to work for everyone who lands on it, including people using a keyboard, a screen reader, or a browser with JavaScript turned off.
We refer to the Web Content Accessibility Guidelines, version 2.1, at level AA. We have not been audited against them by anyone, and we have not run a formal test, so we do not claim to meet them. What follows is what we have actually built and what we know is missing.
02
What is built in
The page works without JavaScript. The questions open and close using the browser's own disclosure elements rather than scripted panels, so they respond to a keyboard and read correctly to a screen reader even if nothing loads.
Every link and button shows a clear focus outline when you move through the page with a keyboard, and that outline appears for keyboard users without cluttering the page for everyone else.
There is one main heading per page and the heading levels run in order, so a screen reader's outline of the page matches what a sighted reader sees.
If your device asks for reduced motion, we honour it. Animations and transitions are switched off and in-page jumps stop gliding.
Decorative icons are hidden from screen readers rather than announced as meaningless graphics, and the page language is declared so a screen reader picks the right voice.
The booking calendar opens in a dialog built on the browser's own dialog element. While it is open, keyboard focus stays inside it, Escape closes it, and focus returns to the button you opened it with.
03
What we know is not right yet
The booking calendar is supplied by Calendly and runs inside a frame we do not control. We cannot set its description, and we cannot guarantee how it behaves with assistive technology.
Inside that dialog, the message shown while the calendar loads is visual only and is not announced. If it fails to load, a working link to open the calendar in a new tab appears and is reachable by keyboard, but the failure itself is not read out.
The sections of the page are not individually labelled, so a screen reader cannot jump between them by name.
We have not tested with a real screen reader across more than one browser, and we have not had a person who relies on one review the page.
04
Colour and contrast
The site uses a single light colour scheme. We checked the text colours against their backgrounds by calculation and they meet the AA contrast threshold for body text, with the small uppercase labels sitting closest to the line.
That is a calculation, not an audit, and it does not cover every combination on the page.
05
Tell us if something does not work
If any part of this page is difficult or impossible for you to use, write to stomejiwebcreators@gmail.com and tell us what happened and what you were using. We will fix what we can and tell you honestly when something is not ours to fix.
If you cannot use the calendar, say so in that email and we will book a time with you directly.