Keyboard
All primary navigation and form controls are intended to work without a pointer.
Inclusive website use
Accessibility statement
The site is built to support keyboard navigation, readable contrast, responsive layouts, text alternatives and reduced motion, with final live testing still required.
Diagnosis before applianceThis page supports informed questions. It cannot examine you or determine treatment suitability.
The plain answer
Accessibility is an operating requirement, not a one-time certificate.
The source package targets WCAG 2.2 AA practices where practical, including semantic headings, visible focus, labelled forms, alt text, skip navigation and keyboard-operable menus.
Automated checks cannot prove complete accessibility. The deployed site should be tested with keyboard navigation, zoom, screen-reader workflows and real users, then corrected when barriers are found.
What matters
Key points before you act
Use these as a decision filter at a real consultation.
Visual
Colours, type size, spacing and focus states are designed for readability.
Responsive
Content reflows for mobile and high zoom without deliberate horizontal scrolling.
Known scope
This statement covers the static website package. External linked sites, browser controls and future embedded tools are outside this codebase.
PDFs or new third-party widgets added later require separate accessibility review.
Feedback
Use the contact form to report the page, control and barrier. Do not use it for a medical emergency.
Before launch, configure the receiving team and response timeline so accessibility reports are actually monitored.
Ongoing review
Re-test after content, CSS, scripts, forms, analytics, scheduling tools or practice widgets change.
A passing automated scan should never be treated as proof that the whole user journey is accessible.
Live-site accessibility checks
- Navigate every menu and form by keyboard.
- Test 200% and 400% zoom.
- Review headings, landmarks and link names with a screen reader.
- Confirm error messages are announced and understandable.
- Check colour contrast and reduced-motion behaviour.
Common questions
Questions patients ask
Does the site claim formal WCAG certification?
No. It states a target and requires ongoing manual and user testing.
How do I report a barrier?
Use the contact page after its recipient is configured and identify the page and control.
Are external websites covered?
No. Their owners control their accessibility.