Our goal
Pergola Wiki uses relevant WCAG 2.2 AA requirements as a design and testing baseline, aiming to provide an equivalent knowledge path for readers using a keyboard, screen reader, magnification, reduced motion or other assistive methods. This goal is not a legal certification.
Implemented features
- Skip-to-content, semantic headings, page language, descriptive links and visible keyboard focus.
- The search dialog supports focus entry, focus containment, Escape to close and focus return.
- Original technical diagrams include short alternatives, captions and expandable detailed text descriptions.
- Tool forms provide labels, keyboard operation and status updates perceivable to screen readers.
- Mobile reflow, browser text enlargement and reduced-motion preferences are supported.
Recent testing
On 24 July 2026, public Lighthouse checks of the homepage, an article and an interactive tool each scored 100/100 with no automated failures. A sitewide static audit confirmed that every article diagram has an associated detailed description. Automated results detect only part of the accessibility picture.
Known limits and next steps
The site has not published third-party WCAG certification and does not represent an automated perfect score as complete accessibility. VoiceOver, NVDA, 200%/400% zoom, high-contrast mode and task testing with disabled users remain necessary before a formal conformance claim. Linked source websites are third parties whose accessibility is outside Pergola Wiki's control.
What to include when reporting a barrier
Record the page URL, language, browser, device, assistive technology, intended task and specific barrier, then send it through your existing contact channel with the publisher. A dedicated public accessibility email has not yet been published; this remains an operational gap.