Keyboard
Navigation and interactive controls should remain usable without a mouse.
Accessibility
Accessibility Statement
The site is built to support keyboard navigation, semantic headings, text alternatives for meaningful images, readable contrast and responsive use across common devices. Accessibility should be treated as an ongoing QA responsibility, not a one-time declaration.
Explore by topic
Find the part of orthodontics you need
Understanding this topic
Accessibility Statement
The site is built to support keyboard navigation, semantic headings, text alternatives for meaningful images, readable contrast and responsive use across common devices. Accessibility should be treated as an ongoing QA responsibility, not a one-time declaration.
Decision points
Website information
Images
Meaningful images need descriptive alternative text; decorative images should not create noise.
Responsive layout
Content should remain usable on narrow screens and at browser zoom.
Feedback
Accessibility defects should be corrected when identified.
Questions about this topic
Common questions about Accessibility
Is the site guaranteed to meet every accessibility standard?
No website should make an absolute claim without ongoing auditing.
Can users report a problem?
Yes. Accessibility issues should be reported through the site contact pathway.
Does mobile accessibility matter?
Yes. Navigation, tap targets, text scaling and focus behaviour all require mobile testing.
References