Website accessibility
A site about accessible playgrounds has an obligation to be accessible itself.
Short answer
Playbright aims to meet WCAG 2.2 Level AA. Pages are plain HTML with semantic headings, visible focus, keyboard-operable controls, text that reflows on small screens and at high zoom, and no content that depends on color alone. Interactive tools work without JavaScript wherever the underlying content allows.
What this site aims for
Playbright targets WCAG 2.2 Level AA. In practical terms that means:
- Semantic HTML. One h1 per page, headings in order, real lists, real tables with header cells and captions, and landmark regions for the header, the main content and the footer.
- Keyboard operation. Everything that can be clicked can be reached and operated with a keyboard, focus is always visible, and a skip link jumps straight to the main content.
- Text that reflows. Pages are readable at 200 percent zoom and on a narrow phone without horizontal scrolling. Wide data tables scroll within their own region rather than forcing the page sideways, and that region is reachable by keyboard.
- Contrast and color. Text contrast is checked in both light and dark themes, and no information is carried by color alone.
- Motion. Animation is minimal and respects the reduced motion setting.
- No interruptions. No pop-ups over the content, no auto-playing media, no scroll hijacking.
Known limitations
- The calculators need JavaScript to compute. The explanation, the tables and the underlying figures on each tool page are readable without it.
- The saved checklists store their state in your own browser, so progress does not transfer between devices, and it is cleared if you clear site data.
- Search needs JavaScript. Without it, the page links to the full topic index, which is a plain list of every page.
- Some source documents linked from pages are third party PDFs, and their accessibility is outside our control.
Reporting a problem
Email editor@playbright.org with the page URL, what you were trying to do, your browser and any assistive technology you use, and what happened. Access problems are treated as bugs, not as feature requests, and they are prioritized accordingly.
Frequently asked questions
Does the site work without JavaScript?
Yes for all content. Every guide, table, glossary entry and index is plain HTML and readable with scripting turned off. The calculators and the saved checklists need JavaScript to compute and to remember state, and the search page falls back to a link to the full topic index.
Does the site work with a screen reader?
It is built to. Pages use one h1 and a correct heading order, tables have real headers and captions, form controls have labels, landmarks are marked up, and there is a skip link to the main content. If something reads badly with your setup, please report it with the page URL.
Is there a dark mode?
Yes, and it follows your system setting rather than a toggle on the page, so it matches whatever the rest of your device is doing. Both themes are checked for text contrast.