eladalon.com
Accessibility statement
Last updated: 15 September 2026
I want everyone to be able to read this site, including people who use screen readers, keyboards only, magnification, or reduced-motion settings. This page says what has been done, what is known to be limited, and how to tell me about a problem.
Standard
The target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. The site has been checked against it by its developer, not audited by an independent third party.
What has been done
- Every page works with a keyboard. Focus is visible as a solid outline. A "Skip to main content" link is the first item on every page.
- Headings are in order (one h1 per page, then h2, then h3). Navigation and landmarks are labelled, and the menu works on phones.
- Photographs have descriptive alternative text. Purely decorative marks are hidden from assistive technology.
- Text can be zoomed to 200 percent without horizontal scrolling.
- The site uses motion by design: an opening counter, smooth scrolling, a custom cursor on mouse devices, and photos and text that ease in as you scroll. When your system asks for reduced motion, all of it is switched off: no counter, normal scrolling, no cursor effect, and every element shown at once.
- The reel plays muted in the background; it contains no speech and no sound track, so it has no captions. The "Play Reel" button shows the video with normal controls.
- No accessibility overlay or plugin is used.
Known limitations
- Several chapter images are photo collages. Their alternative text summarises the collage; it does not describe every photo inside it.
- Some small labels on photos are set in light text over a dark gradient; on very bright photos the contrast can drop below the recommended ratio.
- The reel is a silent slideshow of photographs and has no audio description track. The photos in it are the same ones shown, with alternative text, on the chapter pages.
Tell me about a problem
If something on this site does not work for you, email eladalon@icloud.com and say which page and what happened. I will reply and try to fix it.