Accessibility

The library aims to make long technical material usable across keyboards, touch screens, screen readers, narrow displays, print, and reduced-bandwidth connections. Accessibility is treated as part of publishing quality rather than a final visual check.

Current design commitments

• Pages use semantic headings, landmarks, links, buttons, lists, tables, and native disclosure controls wherever possible.
• Interactive controls are keyboard reachable and receive a visible focus indicator.
• Text and controls are designed for strong contrast and browser zoom.
• Chapter navigation adapts to small screens without removing access to the book contents.
• Images should include meaningful alternative text when they teach information; decorative cover images may use empty alternative text when the adjacent book title provides the same link name.
• Print styles remove navigation and interactive chrome so chapters and worksheets remain usable on paper.
• Narrated chapters retain ordinary readable text. Audio is an additional format, not the only way to receive the content.

Known limitations

Some technical diagrams are raster images and may be harder to inspect at extreme zoom. Wide comparison tables and code samples can require horizontal movement on narrow screens. The custom narrated-text experience depends on JavaScript, although the chapter text and audio file remain independently available.

The site does not currently claim formal conformance with a specific WCAG level. A conforming experience requires continuing review of content, generated pages, third-party fonts, images, transcripts, and new interactions—not only a one-time template audit.

Useful issue reports

An accessibility report is most actionable when it includes the page URL, device or assistive technology, browser, expected behavior, and what prevented completion. Screenshots or short recordings are helpful when they do not expose private information.