Accessibility at Croft
How we build this website for people of every age and ability.
Accessibility is core to what we build
We build technology for older people living independently. Many of our customers are in their 60s, 70s and 80s, often researching help for a parent who is older still. Vision changes, hearing differences and motor challenges aren't edge cases for us. They're our primary audience. We aim to meet WCAG 2.2 Level AA and last checked this on 5 December 2025.
44px+
Minimum touch targets
4.5:1
Contrast ratio (minimum)
0
Keyboard traps
Our conformance level
- Standard
- WCAG 2.2 Level AA
- Last assessed
- 5 December 2025
Our last assessment, on 5 December 2025, found this website conforms to WCAG 2.2 Level AA. We keep testing as pages change, and we want to hear about anything that gets in your way.
Assessment method: Comprehensive automated and manual testing
How we meet the standards
Perceivable
Information and interface components must be presentable in ways users can perceive.
Perceivable
Information and interface components must be presentable in ways users can perceive.
- 1.1.1 Text Alternatives Level A
Every image has descriptive alt text. Decorative images are properly marked.
- 1.3.1 Info and Relationships Level A
Semantic HTML5 elements, proper heading hierarchy, labelled form fields.
- 1.3.4 Orientation Level AA
Fully responsive design works in any orientation.
- 1.4.3 Contrast (Minimum) Level AA
All text meets or exceeds 4.5:1 contrast. Large text meets 3:1.
- 1.4.4 Resize Text Level AA
Relative units throughout. Content reflows properly when zoomed.
- 1.4.10 Reflow Level AA
Mobile-first responsive design with no horizontal scroll.
- 1.4.11 Non-text Contrast Level AA
All buttons, icons, and form controls meet contrast requirements.
- 1.4.12 Text Spacing Level AA
No content loss when users override spacing styles.
- 1.4.13 Content on Hover or Focus Level AA
Tooltips and dropdowns can be dismissed and remain visible.
Operable
Interface components and navigation must be operable by all users.
Operable
Interface components and navigation must be operable by all users.
- 2.1.1 Keyboard Level A
Every interactive element is keyboard accessible. Tab order is logical.
- 2.1.2 No Keyboard Trap Level A
Users can always navigate away using standard keys.
- 2.4.1 Bypass Blocks Level A
Skip to main content link on every page.
- 2.4.3 Focus Order Level A
Logical tab order follows visual layout.
- 2.4.6 Headings and Labels Level AA
Descriptive headings and clear form labels throughout.
- 2.4.7 Focus Visible Level AA
High-contrast focus rings on all interactive elements.
- 2.4.11 Focus Not Obscured (Minimum) Level AA
No sticky headers or footers obscure focused elements.
- 2.5.3 Label in Name Level A
Button text matches accessible name for voice control users.
- 2.5.7 Dragging Movements Level AA
No drag-only interactions. All actions have click alternatives.
- 2.5.8 Target Size (Minimum) Level AA
All touch targets are 44x44px minimum, exceeding requirements.
Understandable
Information and interface operation must be understandable.
Understandable
Information and interface operation must be understandable.
- 3.1.1 Language of Page Level A
HTML lang attribute set to "en-GB" on all pages.
- 3.2.1 On Focus Level A
No automatic navigation or form submission on focus.
- 3.2.2 On Input Level A
Form changes only occur when explicitly requested.
- 3.2.3 Consistent Navigation Level AA
Same navigation structure on every page.
- 3.2.4 Consistent Identification Level AA
Consistent button labels, icons, and patterns throughout.
- 3.2.6 Consistent Help Level A
Contact and help links in same footer position on all pages.
- 3.3.1 Error Identification Level A
Form errors clearly highlighted with descriptive messages.
- 3.3.2 Labels or Instructions Level A
All form fields have visible labels and helper text.
- 3.3.3 Error Suggestion Level AA
Error messages include guidance on how to fix issues.
- 3.3.7 Redundant Entry Level A
Forms remember entered data and support autofill.
- 3.3.8 Accessible Authentication Level AA
No CAPTCHAs or memory-based authentication required.
Robust
Content must be robust enough for diverse user agents and assistive technologies.
Robust
Content must be robust enough for diverse user agents and assistive technologies.
- 4.1.2 Name, Role, Value Level A
ARIA labels and roles used correctly throughout.
- 4.1.3 Status Messages Level AA
ARIA live regions announce form submissions and errors.
How we test
We use a comprehensive testing approach combining automated tools and real-world manual testing.
- Automated testing Every commit
- axe-core, Lighthouse, and Pa11y run on every page during development.
- Screen reader testing Quarterly
- Manual testing with NVDA, JAWS, VoiceOver, and TalkBack.
- Keyboard navigation Quarterly
- Complete site navigation using only keyboard.
- Mobile accessibility Quarterly
- Testing on iOS and Android with accessibility features enabled.
Technical compatibility
Browsers
- Chrome (latest 2 versions)
- Firefox (latest 2 versions)
- Safari (latest 2 versions)
- Edge (latest 2 versions)
Screen readers
- NVDA (Windows)
- JAWS (Windows)
- VoiceOver (macOS/iOS)
- TalkBack (Android)
Assistive tech
- Screen magnifiers
- Voice control (Dragon, Voice Control)
- Switch devices
- Eye tracking systems
Technologies
- Semantic HTML5
- WAI-ARIA 1.2
- CSS with reduced motion support
- Progressive enhancement
Found an issue?
We take accessibility seriously. If you encounter any barriers, please let us know. We will respond within 2 business days.
Contact us
What to include
- Page URL where you experienced the issue
- Description of the accessibility barrier
- Browser and assistive technology (if applicable)
- Your preferred contact method
Alternative formats
This accessibility statement is available in alternative formats upon request:
To request an alternative format: [email protected]
Turnaround time: 3 business days