Our commitment
We want people with disabilities to be able to plan, pack, and participate without a second-class version of the trip. Accessibility is part of the product work, not a campsite we hope to reach someday.
Our current target
Camplist is being designed and tested toward the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. This page is a statement of direction and current work, not a claim that every page already fully conforms.
We also aim for plain language, predictable navigation, forgiving forms, and generous mobile targets because a checklist that is technically valid but difficult to use is still a poor checklist.
What is already in the pack
Keyboard access
Skip navigation, visible focus, native controls, keyboard-operable dialogs, and no drag-only planning action.
Screen-reader structure
Landmarks, headings, labels, status messages, descriptive control names, and decorative artwork kept out of the reading order.
Readable presentation
Strong text contrast, restrained colour roles, clear selected states, scalable type, and locally hosted fonts.
Flexible layouts
Responsive pages, 44-pixel touch targets in new work, horizontal alternatives for dense trip information, and no separate reduced mobile feature set.
Reduced motion
Animation and transitions are reduced when the device requests reduced motion. No flashing content is used.
Accessible access
A semantic one-time-code field supports paste, mobile autofill, and screen readers. Magic links offer another path.
Known limitations
- Dense planning tables and day grids may still require horizontal scrolling or extra navigation at high zoom.
- Browser-generated print or PDF output depends on the browser and may not carry the same landmark structure as the live page.
- Some older trip-management screens still need broader manual testing with multiple screen readers and voice-control tools.
- Access codes expire after 15 minutes for security. A fresh code can be requested without losing the trip.
These are active work items, not exceptions we consider finished.
How we check the route
New and changed flows receive keyboard review, responsive checks, automated accessibility scans, focus and dialog checks, reduced-motion review, and semantic-control tests. Camplist also tests core Host, Planner, and Camper journeys at desktop and mobile widths.
Automated checks catch useful problems, but they do not replace testing with people and assistive technology. Broader manual and user testing remains part of the path to a formal conformance claim.
Accessibility feedback
A public accessibility-feedback address or form is not being published yet. This means the statement does not currently provide the feedback channel recommended by W3C, and we do not want to hide that gap behind vague wording.
When the channel is ready, this page will list how to report a barrier, what information is helpful, and the expected response time. Until then, this page will continue to record known limitations and the date of its latest review.