Accessibility
Last checked September 2026
We want everyone to be able to use this site, including people who use a screen reader, a keyboard instead of a mouse, zoom, or reduced motion. If something here gets in your way, we want to hear about it.
The standard we build to
We build and test this site to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That is the current international standard for web accessibility. We don't claim that any test makes a site "ADA compliant", because no test can promise that. What we can tell you is exactly what we checked.
What we check
- An automated scan of every page, in English and Spanish, at seven screen widths from phone to large desktop. It uses axe, a widely used testing tool, and the site doesn't go live with a single violation.
- Contrast is measured, not guessed: text against its real background, in its resting, hover and keyboard-focus states.
- Buttons and links are big enough to tap: at least 24 by 24 pixels, or spaced so they can't be hit by mistake.
- The layout works on a narrow screen down to 320 pixels wide, with nothing cut off or scrolling sideways.
- Keyboard focus is always visible, and a "skip to content" link comes first on every page.
- Reduced motion is respected: with it turned on, the homepage's moving showcase stops moving and shows its examples one after another.
- Each page is marked with its language, so a screen reader reads the Spanish pages in Spanish.
- A person has tested it by hand: keyboard only on every page type, NVDA with Chrome on Windows, and VoiceOver with Safari on iPhone, in September 2026.
Automated tools find only part of what matters, which is why the checks by hand are on this list too.
What we don't use
This site has no accessibility overlay or widget. Those tools don't make a site accessible, and they often get in the way of the assistive technology people already use.
Known limitations
None that we know of.
The example sites shown here are demonstrations. Their forms check what you type, but they don't send anything. To reach us, use our contact page.
Tell us what didn't work
Email hello@readyastro.com, or use the contact page. Tell us which page you were on, what happened, and what you were using (for example, the browser or screen reader). We reply within 24 hours. If something here doesn't work for you, we'll get you the information another way while we fix it.