Accessibility

Statement first prepared July 17, 2026. Claims below last verified August 20, 2026.

The standard

This site is built to WCAG 2.2 Level AA as an engineering target. In every area the testing below covers, it conforms; the areas not yet tested are named on this page rather than left to be inferred from silence. A standard we design and test against is not a legal guarantee, and this page does not claim the site is perfectly compliant. No accessibility overlay or widget is used here. Overlays tend to paper over problems rather than fix them, and they are not a substitute for building the page properly.

How the site is built

• The pages are plain HTML with real landmarks and headings, one page-level heading each.
• Nothing on the site depends on JavaScript. Every page is readable and every link works with scripting switched off entirely, so there is no loading state to get stuck in and nothing to fail silently. While the site is under construction there is one script, which opens the construction notice as a dialog box the first time you arrive; with scripting off it simply does not appear, and the same notice is written across the top of every page either way.
• A skip link is the first thing you reach with the keyboard, and every interactive element shows a visible focus outline.
• Text scales with your browser’s own font size setting rather than overriding it, and the layout reflows to a 320-pixel width without a horizontal scrollbar. There is a real exception to this, described under “Known problems” below.
• Color is never the only way meaning is carried, and text contrast is measured rather than eyeballed.
• Animation respects your system’s reduced-motion setting, and decorative artwork is hidden from screen readers instead of being announced as meaningless images.
• No content is embedded from anywhere else. The typeface is served from this site and there are no third-party widgets, players, or iframes. This site loads two scripts. One is the invisible visitor counter described in the Privacy Policy, which renders nothing you can see or interact with. The other runs only while the site is under construction: it opens the construction notice as a dialog box once per browsing session, and it stops being served when the site launches. Our hosting provider currently adds one more script of its own to each page as it is delivered; the site's own security policy blocks it from running, and it draws nothing either way.

What has actually been tested

Testing is automated against real browsers rather than a checklist, and every entry below says when it was last run, because “tested” and “tested once, before the site changed” are different claims.

• Every page rendered in Chromium, Firefox, and WebKit, the engine behind Safari, at sixteen widths from 320 pixels to 3840 pixels, on July 17, 2026. No text clipped and no content pushed off-screen. Every standalone control, meaning buttons, navigation items, and footer links, is at least the 24-pixel minimum target size; links inside a sentence are smaller, which the standard allows because they sit in a line of text. After the site was restructured on July 20, 2026, the layout checks were re-run in Chromium at seven widths from 320 pixels to 1920 pixels, and again on August 18, 2026 at five widths across all ten pages.
• Contrast of every text and interface color pair calculated against the 4.5:1 and 3:1 thresholds, most recently for the current palette on July 21, 2026. Two failures found this way, in the step numbers and the focus outline, were fixed rather than excused.
• Keyboard operation checked in Chromium and Firefox on July 15, 2026: the skip link works and moves focus, the tab order follows the page, and the mobile menu opens, closes, and exposes its links from the keyboard alone. The menu is plain HTML with no script, and the only change to it since has been the addition of current-page markers to its links. Re-checked in Chromium on August 18, 2026, including that every focused element shows a visible outline. The construction notice dialog added on August 20, 2026 uses the browser's own dialog element, so Escape closes it, focus stays inside it while it is open, and the page behind it cannot be scrolled or reached. That was checked in Chromium and in Firefox on August 20, 2026, at nine window sizes down to 256 by 256 pixels. It has not been checked in Safari.
• Page zoom without loss of content or function: to 200% on July 17, 2026, and to 400% on August 18, 2026. Both levels are required at this standard; 400% is the harder of the two.

Known problems

This section exists because the one below it was not the right home for a fault we have measured and not yet finished fixing. “Not tested” and “tested, and it fails” are different things to tell you.

• Enlarging text to 200% on a very narrow screen cuts off the right edge of the page.On a 320-pixel-wide screen, with your browser’s font size set to twice its normal value, the page becomes wider than the screen and there is no horizontal scrollbar to reach the rest, so some words are cut off. This is a failure of WCAG 2.2 success criterion 1.4.4, Resize Text. It affects every page, including this one and the Privacy Policy. Measured on August 29, 2026.
  Work on it started the same day and has reduced the overflow by about half, but it is not finished, and it would be wrong to describe a partial fix as a fix. Increasing the whole page’s zoom, rather than only the text size, is not affected and works to 400%. If this is standing between you and reading something here, email the address below and it will be sent to you in a form you can read.

What has not been tested yet

These are genuinely outstanding. They are listed because an accessibility statement that mentions only its successes is not much use to the person reading it.

• Screen readers. The site has not been tested with VoiceOver, NVDA, or JAWS. Automated tools cannot stand in for that, so no claim is made about it. This matters most for the construction notice dialog: a dialog box is exactly the kind of component screen readers handle differently from one another, and it is the newest thing here.
• Safari with Full Keyboard Access. Keyboard testing was done in Chromium and Firefox. Safari only moves focus to links when Full Keyboard Access is switched on, and that combination has not been checked on real hardware.

If something here does not work for you

Please email tali@lecturebound.com and describe what you ran into, along with the browser and any assistive technology you use. It will be treated as a bug in the site rather than a problem with your setup, and you will get a reply from a person. If something on the site is standing between you and getting in touch, that is the site’s fault, and Tali would still like to hear from you.