Accessibility statement

The decisions underneath

• Nothing is signalled by colour alone. This site has no success green and no error red — both of those are chemical notation here, and a red error message beside a red element token would teach a student exactly the wrong thing. States are carried by a rule, a word and weight.
• The focus ring is never removed. It is an ink ring, a white gap, then an ink ring again, so one of the two always stands out against whatever is behind it. The sticky header is 60 pixels at the default text size, and every anchor target reserves that height plus a gap above itself — both measured in rem, so the bar and the clearance grow together and focus stays clear of the bar through 200 per cent text, which is what SC 1.4.4 asks for. Past 200 per cent the navigation wraps to a third line and outgrows the reservation; that limit is recorded in the stylesheet rather than hidden, and every link stays reachable.
• Every page reads without JavaScript. The mobile menu is a native disclosure element, and every word of every page is in the markup the server sends. Token Play is an enhancement, not a route, and so is the consent panel — with scripting off, Cloudflare Zaraz cannot ask and nothing it gates can run. PostHog needs scripting for an unrelated reason — it is a script, not something the panel gates — so it is off too, for the same practical result: a reader with scripting off sees exactly the site with every measurement already off, whether that measurement waits for the panel or not. The two forms are the exception, and it is a real one: they are HubSpot embeds and they need scripting to appear at all, so with scripting off there is nothing there. Where each one sits, the telephone number, WhatsApp and the email address are printed beside it and again in a noscript block, so that reader is given a route rather than a blank space. Until 3 September 2026 the schools form posted and redirected on its own; that is what the change cost, and it is recorded here rather than quietly dropped.
• Wide content scrolls inside itself. The board inventories and the syllabus mapping are real tables with captions and scoped headers, each in its own scrolling container, so the page never scrolls sideways and the table can still be read.
• Text can be re-spaced. No text container has a fixed height, so line height, word spacing and letter spacing can all be forced without anything clipping.
• Chemical notation is set properly. Real subscript and superscript elements, never Unicode subscript characters, which screen readers handle unreliably and most fallback fonts do not carry. The three typefaces are self-hosted for the same reason — the reaction arrow is absent from the subsets a font CDN serves.
• Nothing is asked behind a placeholder. Where this site draws a form control, the label sits above its field and is never a placeholder, hints are permanent rather than tooltips, and an error is named in words and tied to its field. That is the standard the site’s own forms were built to and the standard anything added here will be held to; inside the two HubSpot embeds the fields and their error messages are HubSpot’s, which is why they are listed above as untested rather than claimed.
• Help is in the same place on every page. Phone, WhatsApp and email, in that order, in the footer, on every page of the site.
• The only overlay on this site is the consent panel, and it asks something real. Since 4 September 2026 a panel from Cloudflare Zaraz appears once, before Analytics or Advertising runs, and stays reachable afterwards from a control on the cookies page rather than reappearing on every visit. Its keyboard reachability and dismissal are checked in the pass this page describes; its markup is Cloudflare’s and is named above as one of the things we cannot fully warrant. The two HubSpot forms load with the page and draw nothing of their own beyond their fields, so they take no keyboard stop before that. Since 5 September 2026 PostHog also loads with the page, on every page, and it too draws nothing and takes no keyboard stop — it is not part of the panel above, so nothing about this bullet's "asks something real" applies to it. Google Ads is an advertising tag; it draws nothing either.

What has not been tested by a person

This is the part of an accessibility statement worth reading. A build gate proves a keyboard path works; it cannot prove it makes sense.

Nobody has read this site with a screen reader.

Focus order, and whether a chemical formula is announced in a way that teaches anything, are not arithmetic and cannot be settled by a build gate. A pass with NVDA and with VoiceOver is still outstanding — nothing below replaces it. What has been checked, on 30 August 2026: the accessibility tree a screen reader actually reads from was pulled programmatically for a full keyboard round of Token Play. Each token announces the symbol a reader can see and then its name and type (“Ca, Calcium, element”; “2, Valency two”; “CO3, Carbonate, radical”), which is SC 2.5.3 — the accessible name has to contain the visible text, and it used to say “Calcium, element” and never the symbol, each slot announces its state (“Empty element slot”, then “Calcium, element, placed in the element slot. Press Enter to take it back.”), and the live region announced “Calcium carbonate. That is a correct formula.” — the spoken name, not the letters. That confirms the underlying data is correct and well-formed; it does not confirm it sounds right, which only a person using a screen reader can.

Most formulas outside the method pages carry no spoken name.

A formula is given a spoken form — “calcium carbonate” rather than “C-A-C-O-three” — only where the site holds one. That covers the formulas the method pages set, and 107 of the 365 formulas on a board inventory page. The rest are announced character by character — confirmed directly on /syllabus/cbse/, where HCl and the first NaOH and NaCl carry no spoken label at all. The map is being extended; a wrong spoken name would be worse than none, so it is written by hand rather than generated.

The fourteen FAQ questions are not headings.

Each question on /faq/ is a native <details> with its question in the <summary>, and a browser exposes a summary as a disclosure control whose contents are its name — so the question cannot also be a heading, and heading navigation on that page reaches the three group headings and stops. It was marked up as an <h3> inside the summary, which produced no heading at all and read, in the source, as solved; the h3 has been removed rather than left claiming a role the browser discards. The alternative is a JavaScript accordion, where a real heading can hold a real button, and it is the worse trade: every answer is in the DOM here and a reader with no JavaScript loses nothing. The questions are reachable as fourteen named buttons, and each still has its own anchor.

Nobody with a colour vision deficiency has read it.

The design forbids colour as the only signal anywhere — the three token colours are near-identical in luminance, so every token carries its type as content, as form and as a written label as well. That is the right design; it has not been confirmed by a reader who needs it. What has been checked, on 30 August 2026: Token Play was rendered under Chromium’s own protanopia, deuteranopia, tritanopia and achromatopsia emulation. Under achromatopsia — no colour information at all — the three tokens stayed unmistakable: a filled circle, a circle with a visible inner ring, a smaller mono digit, each with its type written underneath. That confirms the redundant signals hold under simulation; it is not the same as a genuinely colour-blind reader using the page, and the statement will keep saying so until one has.

The photographs are not here yet.

Most of the photography now exists, and every shipped image carries alternative text written for it. Two places still render a ruled plate naming the photograph that belongs in them — a forthcoming title has no cover, and one shot in the timeline has no archive material behind it — and several images that ARE here stand in for a page that was never photographed. Each of those says so, in a visible caption as well as in the alt text, rather than letting a substitute pass as the thing described.

The two forms are somebody else’s.

Since 3 September 2026 the enquiry form on the schools page and the message form on the contact page are HubSpot embeds, rendered inside an iframe HubSpot controls and loaded with the page. The labels, the error messages, the focus order and the target sizes inside that frame are HubSpot’s, and their accessibility is not ours to guarantee — this is now the largest untested surface on the site, and it sits on the page a school arrives at. The form it replaced was ours and was built to every commitment on this page. The telephone number, WhatsApp and the email address are printed beside each embed and need no scripting at all; that is the route we would point a reader to who finds the embed unusable, and we would want to be told.

The consent panel is somebody else’s too.

Since 4 September 2026 measurement waits behind a panel Cloudflare Zaraz draws, not this site. Its markup, its focus order, its dismissal and its target sizes are Cloudflare’s, and they are not held to the commitments on this page any more than the HubSpot forms above are. It is reachable and dismissible by keyboard in the pass we have run, which is not the same as a person who relies on assistive technology having used it, and the honest status is untested until one has. The control that reopens it on /legal/cookies/ is ours and is built to every commitment here.

There has been no third-party audit.

Everything above is a self-evaluation by the people who built the site.

Tell us if something does not work

If a page will not do what you need it to, we would rather hear it than not. Tell us which page and what happened, and if you can, what you were using to read it — that is usually the thing that lets us reproduce the problem. A person answers the phone from the Kochi office on weekdays: +91 99471 23678, WhatsApp +91 99471 23678, or learn@playwaybooks.com.

If you need something on this site in another form — a syllabus inventory as a plain document, a page read to you over the phone — ask, and we will send it.

Contact Playway Books

This statement was prepared on 30 August 2026 by the people who built the site, using the automated evidence described above and a review of the code, and reviewed again on 2 September 2026 when the legal pages were redrafted. It has not been audited by a third party. It is reviewed whenever the build gates change.