Accessibility

Accessibility statement

This documentation site is built for everyone who ships CSS: keyboard users, screen reader users, people who zoom or override colours, and teams who care about inclusive defaults. We aim for WCAG 2.2 Level AA for the site chrome and reading experience, while being honest about where technical content (code samples, demos) is harder to make fully equivalent.

What we commit to

Structure. Semantic HTML, landmarks, and headings that reflect the page outline so navigation and reading order stay predictable.
Keyboard and focus. Interactive controls are reachable in a sensible tab order, with visible focus styles that meet contrast expectations.
Readable text and UI. Body copy and primary interface colours are chosen for comfortable reading in light and dark presentation where the site offers both.
Orientation. Unique page titles and meta descriptions so each route is identifiable in tabs, history, and search results.
Ongoing improvement. Accessibility is treated as a backlog of real issues, not a one-off audit badge. Reports from readers carry weight.

Where the experience can still fall short

The primary navigation collapses behind a menu control on small and coarse-pointer viewports; when opened, long nested lists still require scrolling, which is intentional for touch discoverability but can be tiring. Code blocks use syntax highlighting that may not expose token semantics consistently across assistive technologies. Some interactive reference material may assume a pointing device for parts of the UI even when the rest of the page is keyboard-accessible. If something blocks you from reading or using a page, tell us—we treat that as a defect.

Methodology vs this site

LSCSS itself is a way to organise CSS in production codebases. How you apply accessibility in your product is broader than this brochure site. For accessibility in the context of CSS architecture, see the guide on Accessibility and CSS and the summary on Accessibility (apply).

Report a problem

Email or contact via Crayons and Code with the page URL, what you were trying to do, your browser and version, and any assistive technology (including version if you know it). Screenshots or short screen recordings help. We cannot promise an instant fix, but we will acknowledge genuine barriers and track them like any other bug.