Tell me what you are trying to build, fix, govern, prove, or launch, and I will point you to the public Folium page that fits. It uses public routes only, so do not send private data here.
Accessibility
AI guidance should be usable by the people it is meant to help.
Folium's public site is designed to be responsive, readable, keyboard-aware, and honest about what has been tested. Accessibility remains a launch discipline, not a one-time checkbox.
Keyboard access
Core navigation, skip link, forms, buttons, and public tools should remain usable without a mouse.
Readable layouts
Responsive checks cover mobile, tablet, and desktop viewport sizes with horizontal overflow detection.
Clear structure
Pages use meaningful headings, landmarks, labels, and consistent navigation so people can scan and orient quickly.
Reduced friction
The public site avoids live AI surprises, hidden submission, or unexpected data collection in the public review surface.
Future audit
A full WCAG-style pass should be completed before broad launch, including screen-reader, contrast, focus, and Safari/iOS checks.
Current boundary
Browser matrix passed. Full assistive-tech review is still required before launch.
The current automated and visual checks verify route health, headings, canonical URLs, overflow, mobile menu behavior, interactive routes, screenshots, and public file availability across Firefox, Chromium, Brave, and multiple viewport sizes.
Before broad promotion, Folium should complete manual keyboard-only review, screen-reader review, contrast review, Safari/iOS validation, and reduced-motion behavior checks.
Start here
Accessibility is part of launch readiness.
The site should not just look impressive. It should help real people understand serious AI choices without friction.
- 01 Scope
- 02 Build
- 03 Prove
- 04 Operate