Accessibility Statement
Most people who find this site arrive with an eye that won’t close, blurred vision, ringing ears, or a room that won’t stop spinning. Accessibility isn’t an abstract compliance exercise here. It’s the whole audience.
5.1Why this page is not boilerplate
This site was built for people whose bodies have just stopped cooperating. A reader might be holding one eye closed with a finger. They might be nauseated by movement on a screen. They might be reading at 3 a.m. because the vertigo won’t let them sleep, or squinting through an eye that hasn’t produced a tear in weeks.
So we treat accessibility as a design requirement rather than an afterthought, and we would genuinely rather hear that we’ve got something wrong than never find out.
5.2The standard we’re aiming for
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C).
This site is built to meet WCAG 2.1 Level AA, and based on our own testing we believe it substantially does. Because it’s built and maintained by one person, this is a self-assessment, not a certified third-party audit — so we describe our status as substantial, self-assessed conformance, and we keep testing and fixing as the site grows rather than treating accessibility as a finished box to tick.
5.3What we’ve actually built in
- Motion respects your settings. If your device requests reduced motion, our animations and transitions turn themselves off. For readers with vertigo or vestibular symptoms, this is the single most important thing on this list.
- No autoplay. Nothing moves, plays, or flashes at you without your asking.
- Contrast. Body text and headings are set against their backgrounds to meet or exceed WCAG AA contrast ratios. We deliberately avoid low-contrast grey-on-grey styling, because a lot of our readers are reading with one working eye.
- Keyboard navigation. The site can be operated without a mouse, and focus indicators are visible rather than suppressed.
- Semantic structure. Real headings in a logical order, real landmarks, real lists — so screen readers such as VoiceOver, NVDA, and JAWS can navigate the page properly.
- Text alternatives. Meaningful images carry alternative text; decorative ones are hidden from assistive technology so they don’t add noise.
- Resizable text. Text scales with your browser’s zoom and font-size settings without breaking the layout.
- Plain language. Short sentences, no jargon, no textbook. This is an accessibility feature too — brain fog is a real symptom of this condition, and dense prose is a barrier.
We do not use a third-party accessibility overlay or widget. We have chosen to build accessibility into the site’s markup instead.
5.4Known limitations — stated plainly
We would rather tell you where we fall short than pretend we don’t:
- No formal audit. We have tested with browser tools and manual keyboard and screen-reader checks, not with a certified accessibility auditor.
- Photographs of facial paralysis. Progress photos are inherently visual. We are working to write alt text that genuinely describes what changed, rather than “photo of a face.”
- Third-party content. Pages we link to — hospitals, foundations, retailers — are outside our control, and their accessibility is their own.
- Older content. As the site grows, some earlier pages may lag behind our current standards until we go back through them.
5.5If you can’t use part of this site, we’ll fix it or send it to you another way
If any page, guide, or document on this site isn’t accessible to you, email us and we will get you the content another way at no cost — as plain text, as a large-print document, read aloud, or in whatever form works for you. You do not need to explain your disability or justify the request.
5.6Tell us what’s broken
If you hit a barrier, please tell us. It is the fastest way this gets better, and we’re grateful for it. Email hello@ramsayhuntsyndrome.com and, if you can, include:
- The page you were on (the web address, if it’s easy).
- What you were trying to do, and what happened instead.
- The browser, device, or assistive technology you were using — if you know.
We aim to reply within five (5) business days. If something is a genuine blocker for you, say so and we’ll move it to the front of the line.
5.7Compatibility
The site is designed to work with current versions of Chrome, Safari, Firefox, and Edge, on desktop and mobile, together with the assistive technologies commonly used with them. It may not work as well on browsers that are no longer supported by their makers.
5.8Ongoing effort
This statement was last reviewed on July 20, 2026. Accessibility is not a box we intend to tick once. As pages are added and rebuilt, we test as we go, and we will update this page — including the limitations above — as things genuinely change.
This statement is provided in the spirit of the Americans with Disabilities Act (ADA), Section 508, and comparable international standards. It is not a legal warranty of conformance.