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, reduced-motion preferences and operating-system forced-color modes are supported.

Recent testing

On 25 July 2026, automated Lighthouse checks of the homepage, Chinese 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. Five representative pages passed 320 CSS-pixel reflow checks with no page-level horizontal overflow. A 200% text-only enlargement check also switched the header to compact navigation without page-level overflow; Escape closed the menu and returned focus.

Sitewide automated evidence: axe-core 4.10.3 scanned 180 generated HTML pages and recorded 0 violation-rule results and 6 incomplete results. Review the 55-criterion coverage matrix, method and machine-readable audit.

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, broader 200% text-only and 400% zoom coverage across every template, high-contrast task testing and 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. A dedicated public accessibility email has not yet been published; the local report builder below reduces reporting friction but does not send or upload data.

Prepare an accessibility barrier report

This tool prepares a report only in your current browser. It does not upload or send anything. Review the generated text, then share it through your existing contact channel with the publisher.