Our Commitment to an Accessible Website
This is a website about vision, built by a practice whose patients frequently have impaired vision. Treating accessibility as an afterthought here would be indefensible, so it is not. This statement sets out the standard we build to, what has actually been implemented rather than merely intended, the limits we know about, and exactly how to tell us when something does not work for you.
On this page
The Standard We Build To
We aim to conform to the Web Content Accessibility Guidelines version 2.1 at Level AA, published by the World Wide Web Consortium. WCAG is the reference standard for accessible web content and Level AA is the level most commonly cited in policy and procurement. We treat it as a floor rather than a target.
Accessibility on a site like this is not a compliance exercise. A parent researching myopia control at 11 PM on a phone with the text size turned up, an adult with reduced contrast sensitivity, and someone navigating by keyboard after eye surgery are all part of the actual readership. The design decisions below exist for them.
What Has Been Implemented
- Semantic HTML throughout. Real headings in a correct hierarchy with no skipped levels, real lists, real tables with header cells, and landmark regions so assistive technology can navigate structure rather than guess at it.
- One h1 per page, with heading levels that descend in order. This is enforced by an automated content check that blocks a build if it is violated, so it cannot quietly drift.
- Full keyboard navigation. Every interactive element can be reached and operated with a keyboard alone, in a logical order, with no keyboard traps. A skip link lets keyboard and screen reader users bypass the navigation and land on the main content.
- Visible focus indicators. Focus is always clearly shown, never removed, and has sufficient contrast against the surface behind it.
- Color contrast at AA. Body text, headings, links, and interface controls meet or exceed AA contrast ratios in both light and dark appearance, and the site respects your system color scheme preference.
- Color is never the only signal. Links are distinguishable without relying on color alone, and status information is conveyed in text as well as visually.
- Descriptive alternative text. Every meaningful image and diagram carries alt text that conveys the information the image is there to convey. Decorative images are marked so that screen readers skip them.
- Readable, resizable text. Text scales to 200 percent without loss of content or function, and the layout reflows rather than requiring horizontal scrolling.
- Tables that make sense read aloud. Data tables carry captions and header cells so screen reader users get row and column context.
- Respect for reduced motion. Where motion is used, it is subdued and honors the operating system preference for reduced motion.
- Descriptive link text. Links describe their destination rather than saying click here, which matters when a screen reader user lists links out of context.
Known Limitations
Stating limitations honestly is part of an accessibility statement worth reading. We test regularly, but no site is perfect and we would rather tell you where the gaps are likely to be.
- Third-party content. Where the site embeds or links to material we do not control, such as mapping and review platforms, we cannot guarantee that content meets AA.
- Complex diagrams. Illustrations of corneal optics carry alternative text, but a diagram is inherently visual. If a diagram is not conveying its point to you, ask us and we will explain it in prose.
- Documents. Any downloadable document we add in future will be checked for tagging and reading order before publication.
- Ongoing changes. Content is added and revised regularly. A newly published page may occasionally contain an issue that our checks did not catch.
How We Test
- Automated checks in the build. Heading hierarchy, alt text presence, and content structure are validated automatically, and failures block publication rather than producing a warning nobody reads.
- Keyboard-only passes. Pages are navigated end to end using only a keyboard.
- Screen reader spot checks. Key journeys, particularly the contact and scheduling pages, are checked with a screen reader.
- Contrast verification. Color pairs are measured rather than eyeballed, in both light and dark appearance.
- Zoom and reflow. Pages are checked at increased text size and at narrow viewport widths.
How to Report a Barrier
If any part of this site is difficult or impossible for you to use, please tell us. We treat accessibility reports as defects, not as feedback, and we would much rather hear about a problem than have you go without the information.
- Email hello@bettersightovernight.com with the subject line Accessibility. Tell us the page, what you were trying to do, and what happened.
- Or call (480) 706-3937, Monday to Friday from 9:00 AM to 5:00 PM, and describe it to us. You do not need technical vocabulary.
- Tell us what you use if you can, such as the browser, the screen reader, or whether you were navigating by keyboard. It helps us reproduce the problem.
- We will acknowledge your report and tell you what we intend to do about it and roughly when.
- We will get you the information another way in the meantime, by phone or in whatever format works for you. That happens immediately, not after the fix.
Accessibility in the physical office, including step-free access and parking, is described on our location page. How we handle information you send us is set out in the Privacy Policy.
Last updated .