Accessibility

Last updated 16 August 2026

We want this site to be usable by everyone, including people using screen readers, keyboard navigation, magnification, or reduced motion.

What we aim for

We aim to meet WCAG 2.2 level AA. No independent auditor has reviewed this site, so this is not a claim of certified conformance.

What we have done is measure it ourselves, and it is worth being specific rather than vague in either direction. On 4 September 2026 every page was rendered and checked by machine, at desktop width and again at 390px with a coarse pointer, and the faults it found were fixed:

• Contrast: 7 failures across 193 pages, now 0. Text sitting on a gradient used to be skipped by the checker rather than measured, which hid 62 more; gradients are now composited and measured at their worst stop.
• Visible focus: 74 controls had none. An outline was declared using a color variable that was never defined, which makes the whole declaration invalid, so the browser drew nothing. Now 0.
• Touch targets: 69 controls under 44px on a phone, now 0. The checker had only ever rendered a desktop viewport, so the entire coarse-pointer rule set had never been tested despite most of this audience being on a phone.
• Horizontal scrolling: one page, now none.

Two honest limits. Automated checking cannot tell you whether a page makes sense read aloud, and we have not tested this site with a screen reader in the hands of somebody who uses one daily. And two standalone downloads, the free eBook sample and the print-and-play deck, still contain heading-order and target-size faults; they are generated from the book source, and we have not fixed them because doing so risks breaking the printed and EPUB editions built from the same file.

What the site does today

• Semantic HTML with real headings, landmarks and lists, so structure is announced correctly.
• Every navigation region and control carries an accessible name.
• Images that carry meaning have alternative text; decorative artwork is hidden from assistive technology.
• The layout reflows to narrow screens and to zoom without horizontal scrolling.
• Color is taken from a fixed palette chosen for contrast, and color is never the only way information is conveyed.
• Every page of writing on this site reads without JavaScript: the method, the twenty rooms, the 114 micro zones and every article are plain HTML. Three things do need scripts, and they are the interactive ones rather than the reading ones: the shop builds its product cards in the browser, the guided reset keeps your progress on your own device, and the menu opens on a small screen. A visit count is also recorded by a small self hosted script, described on the privacy page.
• No external requests, so nothing loads unpredictably from another origin.

Known gaps

We would rather name these than imply they do not exist.

• No formal third-party accessibility audit has been carried out.
• Focus-visible styling has not been verified on every interactive element.
• The contact and newsletter forms are not connected, so their error and success states cannot yet be tested properly.
• The downloadable PDF has not been checked for tagged-PDF accessibility.

Tell us

If any part of this site is difficult to use, please email support@6s-success.com and describe what happened and what you were using. We will fix what we can and tell you what we cannot.