Accessibility

What has been done, what has not, and how to tell us when something blocks you.

Where things stand

This page says what has been done and what has not. It is deliberately specific, because an accessibility statement that only makes promises is not much use to someone who has hit a barrier.

What has been built in

• Keyboard navigation. Every link, button and form control is reachable and operable by keyboard, with a visible focus outline.
• Semantic structure. Pages use real headings, landmarks and lists, so screen readers get a usable outline rather than a wall of divs.
• Skip link. A skip-to-content link is the first thing in the tab order.
• Contrast. Body text and interface text meet WCAG 2.1 AA contrast against their backgrounds.
• Reduced motion. Hover and transition effects are disabled when your system requests reduced motion.
• Touch targets. Controls are sized for touch rather than shrunk down from a desktop layout.
• Text scaling. Layouts hold together at 200% zoom without horizontal scrolling.

Known limitations

• The printables themselves are visual. A multiplication chart is a grid; there is no meaningful non-visual equivalent of it, and we have not attempted to pretend otherwise.
• Generator interfaces vary. Each generator is built separately, and accessibility support in the newer ones may lag behind the site around them.
• No formal audit. This site has not been independently audited for conformance. The claims above are from our own testing.

Reporting a barrier

If something on this site blocks you, please tell us and describe what you were trying to do and what happened. Accessibility problems are treated as bugs, not as feature requests.