Accessibility

Statement first prepared July 17, 2026. Claims below last verified October 11, 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.
• 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. Setting your browser’s font size to twice its normal value does not cut off text or controls on any page, at 320 or 390 pixels wide. That was not true before September 4, 2026, and a handful of long words were still being cut on this site until September 23, 2026; both fixes are described under “Recently fixed” 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. The only script the website includes that runs in your browser is the invisible visitor counter described in the Privacy Policy, which renders nothing you can see or interact with. Pages eligible for search also contain an inert data label describing the site to search engines; it executes nothing and draws nothing.

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.

• All fourteen pages checked in Chromium, Firefox, and Linux WebKitGTK at sixteen widths from 320 to 3840 pixels on October 11, 2026. The checks measured both content boxes and the text inside them, with no clipping or horizontal overflow. Text enlarged to 200% was also checked in all three engines at 320, 390, 768 and 1440 pixels, using browser font preferences or Firefox's text-only zoom. WebKit is the engine behind Safari; these Linux checks do not replace testing on a physical Apple device.
• The palette's text and interface color pairs were calculated against the 4.5:1 and 3:1 thresholds on July 21, 2026. Representative rendered text pairs were rechecked on October 11, 2026, and automated accessibility scans of six main pages at mobile and desktop sizes found no violations. Automated scans do not replace the screen reader checks listed below.
• Keyboard operation rechecked in Chromium, Firefox and Linux WebKitGTK on October 11, 2026: the skip link moves focus to the main content, the mobile menu opens and exposes its links from the keyboard, and navigation links work. Chromium checks also confirmed visible focus outlines and readable destinations for the Services and FAQ links.
• 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.

Recently fixed

This section is here because a page that only ever describes its successes is not much use. It records a real fault, what it did to you, and what fixing it took.

• Enlarging text to 200% used to cut off the right edge of every page. Fixed on September 4, 2026, with a second, smaller fix live on this site from September 23, 2026. If you set your browser’s font size to twice its normal value on a narrow screen, the page became wider than the screen with no horizontal scrollbar to reach the rest, so text was cut off and could not be recovered by scrolling. On a 320-pixel-wide screen it took the entire header navigation off screen. That was a failure of WCAG 2.2 success criterion 1.4.4, Resize Text, and it affected every page.
  The cause was layout widths written in units that grow with your font size, so the page demanded more room exactly as the text needed more room. Those are now fixed widths. Re-measured afterwards in Chromium at 320 and 390 pixels wide with text at 200%: no box on any of the pages then checked reached past the edge of the screen. The same check against the standard’s text spacing test (criterion 1.4.12) is also clean at 320, 390 and 768 pixels. Page zoom, as opposed to text-only resize, was never affected and still works to 400%.
  An audit on September 6, 2026 used a more exact check, one that measures the text itself rather than the box around it, and found five places where a single long word was still being cut at 320 or 390 pixels with text at 200%: four passages on the home page and one label above a heading on the About page. The box around each fit the screen; the word inside it did not. The fix was made on September 12, 2026 and has been live on this site since September 23, 2026: those columns were given back the width they have at normal text size, and a word that is still wider than the screen now breaks onto a second line rather than running off the edge.
  That fix was re-measured on September 23, 2026 on every page of the site, at 320, 390, 768 and 1440 pixels wide with text at 200%, in Chromium and in Firefox, measuring the text itself: nothing was cut off. The fix is stylesheet-level and should behave the same elsewhere, but Safari has not been re-checked, which is why this names the two browsers rather than implying more.

If something here still stands between you and reading a page, 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.
• Safari with Full Keyboard Access. Keyboard testing was done in Chromium, Firefox and Linux WebKitGTK. Safari only moves focus to links when Full Keyboard Access is switched on, and that combination has not been checked on real hardware. Physical iPhone and iPad testing also remains outstanding.

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.