Accessibility

This course is designed to be usable by everyone, including people using screen readers, keyboard navigation, or assistive technology. Accessibility is part of the lesson, not polish applied afterward.

Keyboard navigation

Every interactive element is reachable and operable via keyboard. Tab order follows visual order. Focus is visible with a 2px ring matching the ink color, with a 2px offset. Skip-to-content links appear on every page. The lesson index and all navigation can be used without a pointing device.

Reduced motion

All animations and scroll-reveal effects respect the prefers-reduced-motion media query. When reduced motion is requested, content appears immediately without transition. The Probability Forge interaction has a data-table mode that replaces animated chart bars with a static table.

Screen reader support

Every section uses semantic HTML with proper heading hierarchy. Lesson plates use aria-labelledby to connect section headings to their content. Interactive controls have descriptive labels and instructions. Live regions announce draw results in the Probability Forge. Generated artwork has descriptive alt text.

Colour and contrast

The design targets WCAG 2.2 AA contrast ratios. The palette uses dark ink on ivory paper for body text, with vermilion reserved for accents and focal points. Forced colors mode is supported: the site falls back to system colors with CanvasText backgrounds and borders.

Responsive design

Pages reflow at 320 CSS pixels without horizontal scrolling. The shoji grid background is removed on mobile to reduce visual noise. The lesson layout switches from a sidebar-plus-content grid to a single stacked column below 72.5rem. Touch targets meet the 44x44 pixel minimum.

No JavaScript

All lesson content, module pages, glossary, patterns, and resources render as static HTML. The course is fully readable without JavaScript. Client-side enhancements (scroll reveals, the Probability Forge interaction, progress tracking) are progressive enhancements that degrade gracefully.

Reporting issues

If you encounter an accessibility barrier, please report it. Include the page URL, the assistive technology you are using, and a description of the issue. Every report is treated as a bug, not a feature request.