Accessibility is considered across structure, content, colour, keyboard interaction, focus, forms, motion and responsive layouts. The target applies to the complete experience, not only an automated score.
Measures in the current build
- Semantic landmarks and a skip link
- One H1 and a logical heading structure on indexable pages
- Visible keyboard focus and keyboard-operable navigation
- Persistent form labels, error messaging and status regions
- Reduced-motion support
- Responsive layouts that do not depend on hover
- Purpose-based text alternatives for meaningful images
Testing approach
Release checks combine automated analysis with manual keyboard, zoom, contrast, responsive and form testing. Formal WCAG conformance also requires complete-page evaluation and should include assistive technology and disabled-user testing appropriate to the service.
Known limitations
No material limitation is intentionally accepted in the current build. External live project websites and third-party destinations are outside this site’s control and may not meet the same standard. If testing identifies a barrier, it should be recorded here with an owner and expected resolution.
Feedback
If something prevents you from using the site, email info@codezela.co.uk. Include the page, what you were trying to do and any assistive technology or browser information you are comfortable sharing.
Standard
WCAG 2.2 is a W3C Recommendation organised around perceivable, operable, understandable and robust experiences.