Accessibility
Accessibility statement
CampKit is designed to target WCAG 2.2 Level AA across its first-party interface.
What this release supports
- Keyboard access to navigation, forms, packing actions, native disclosure sections and dialogs.
- A visible high-contrast keyboard focus indicator and a “Skip to main content” link.
- Programmatic labels for form controls, including packing-list search.
- Text alternatives or accessible names for icon-only and state-changing controls.
- Filter state exposed with
aria-pressedand polite announcements when filtering changes the visible inventory. - Progress indicators with text values and accessible progress semantics rather than relying on colour alone.
- Native modal dialogs with labelled headings, keyboard dismissal and focus returned to the control that opened them.
- Responsive reflow at narrow widths and zoom, with enlarged interactive targets for touch use.
- Reduced-motion support for users who request it at operating-system or browser level.
- Accessible authentication that permits password managers and paste and does not require a puzzle, memory test or CAPTCHA.
Conformance and testing status
CampKit v2.4.1 has been remediated against WCAG 2.2 AA requirements that apply to this interface and has been reviewed at source level for common accessibility failures.
This is not an independent accessibility certification. Browser-native controls, hosting customisations and user-entered content can affect the final experience, so an operator making a formal conformance claim should also test the deployed site with keyboard-only navigation, zoom/reflow and representative assistive technology.
Known limitations
No deliberate first-party blocker is known in this release. Native date, select and dialog presentation can differ between browsers and operating systems. User-created item names, notes and other content may also affect clarity.
Report an accessibility problem
If you cannot use part of CampKit, contact the administrator of this CampKit installation. Include the page or action you were using, what went wrong, your browser/device and—if relevant—the assistive technology you were using. Do not include passwords or sensitive packing information in the report.
Accessibility reports should be investigated as product defects rather than requiring the user to work around an inaccessible control.
Statement preparation
This statement was prepared on 25 August 2026 for the CampKit v2.4.1 accessibility baseline and should be reviewed whenever substantial interface or authentication changes are released.