Last updated 15 September 2026
PMV Publishing is committed to making this website usable by everyone, including people with disabilities. This page explains the standard we build to, how the site is tested, what those tests can and cannot tell you, and how to reach us if something here does not work for you.
The standard we build to
We build and maintain this site against the Web Content Accessibility Guidelines, version 2.1, at Level AA. Those guidelines are written by the World Wide Web Consortium, the body that sets the technical standards of the web, and they rest on four ideas: that content must be perceivable, operable, understandable and robust. At Level A and Level AA together, a page is measured against 50 separate requirements.
A newer version, 2.2, was published in October 2023 and adds nine further requirements. It does not replace 2.1 or make it obsolete; the two share the same foundation, and anything that meets 2.2 also meets 2.1. We name 2.1 Level AA here because that is the version this site is actually measured against, and we would rather publish the standard we test than the newest one on the shelf.
What we do when we build a page
Every page is built with real headings in the right order and proper landmark regions, so screen-reader software can move through it by structure instead of guesswork. Every page can be operated by keyboard alone, with a visible focus outline and a skip-to-content link. Every book cover and image carries descriptive alternative text. Text is sized to stay readable when it is enlarged, and every text and background pairing is checked so the words stand out from what is behind them. Form fields carry labels, and status messages are announced. The layout reflows to any screen width without sideways scrolling, and animation is suppressed for readers who ask their device to reduce motion.
How this site is tested
Every page on this site is scanned with axe-core, an open-source accessibility testing engine. The scan runs the Level A and Level AA rule set, and it runs on each page twice: once at a desktop screen width and once at a phone width of 375 pixels, because a problem can exist at one size and not the other. Each page is sampled twice after it loads and then loaded again as a returning visitor, since some things only appear on a second visit. Anything the scan flags is checked a third time in a clean browser session before it is recorded. The report for each scan lists every page it covered and exactly what was found there.
What an automated scan cannot tell you
An automated scan is a measurement, not a verdict. Research published by Deque, the company behind axe-core, put automated coverage at about 57 percent of accessibility problems — measured across more than two thousand audits and roughly three hundred thousand individual issues. The rest need a person. A scan can confirm that an image carries alternative text; it cannot tell you whether that text describes the picture. It can confirm that a heading exists; it cannot tell you whether the wording is clear.
The engine also returns results it cannot decide either way, which it marks as needing review. Those are neither failures nor passes — they are the places a human review would look first. We read pages by hand as well, and we rely on reader reports for anything a machine cannot see.
We have not published a keyboard-only or screen-reader review of this site, and a passing scan is not a substitute for one. We do not claim this site satisfies every requirement. What we publish is what was actually measured, on the dates it was measured.
Scan history
Every page of this site is scanned, and every completed passing scan is kept here, newest first. A scan that finds problems, cannot reach every page, or does not stay deployed is withheld for review and fixed rather than published here.
- September 2, 2026 scan — 153 pages, 37,218 checks passed, no violations (PASS)
- August 24, 2026 scan — 145 pages, 17,875 checks passed, no violations (PASS)
- August 18, 2026 scan — passed with no violations (summary only; this earlier audit did not record per-page detail)
- July 28, 2026 scan — passed with no violations (summary only; this earlier audit did not record per-page detail)
Known limitations
Checkout is handled by Stripe, and our downloadable EPUB files render in your own reading app — the accessibility of those is governed by those providers and your device, not by this site.
If something here does not work for you
Tell us, and we will help you directly while we fix it. Email support@pmvpublishing.com. If you can, say which page you were on and what happened — but you do not need to know the technical reason, and you will never be asked to explain your disability or prove anything. We can also provide anything published on this site in another format.