Legal
Accessibility statement
A public summary of how WPFlow aims to meet WCAG 2.2 AA expectations across the public site, with visible focus states, keyboard support, and reduced motion handling.
Current accessibility posture
Accessibility is treated as product quality rather than a late compliance step.
- Semantic HTML and keyboard-usable navigation are expected across the site.
- Visible focus states and contrast-safe dark surfaces are part of the visual system.
- Reduced motion preferences should be respected.
How the site is designed
The design system is built to reduce common dark-theme failures.
- Touch targets stay large enough to use comfortably.
- Sticky UI should not obscure focus or headings.
- Accordions and overlays should remain understandable without motion.
Feedback
If something is hard to use, the best route is to report it clearly.
- Send accessibility feedback to support@wpflow.io.
- Include the page URL and a short note on the problem observed.