Accessibility Statement
Last reviewed: July 25, 2026
RealizedAI is committed to making realizedai.ai accessible to everyone, including people with disabilities. We work to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the standard most widely recognized for web accessibility compliance.
What we've done
In July 2026 we redesigned the site: a new color palette, new layouts, and new interactive components. A redesign replaces the pages an earlier audit covered, so we treated it as a reset and audited every public page again using axe-core, the same test engine behind the axe browser extension, together with manual keyboard, zoom, and screen reader testing. The audit found 41 issues, nearly all introduced with the new design. Most were color contrast in the new palette, including two buttons whose labels lost contrast only while the mouse was over them. The rest were a new control that could not be reached with a keyboard, a panel that hid the rest of its page from screen readers, and animation that ignored the reduced motion setting. Every one was fixed and deployed on July 25, 2026.
The July audit closed the color contrast question left open by our previous review. We measured every text and background pair in our design system and recorded the results. Where a color fell short, we replaced it with a darker tone from the same palette. Links inside paragraphs are now underlined, so they no longer depend on color alone.
We audited the site in March 2026 as well. That review found 51 issues across four severity levels, and all 51 were fixed and deployed on March 24, 2026.
Work from both reviews includes:
- Labels on every form control, so screen readers can identify their purpose
- Keyboard access to every interactive element, including the savings calculator and site navigation
- Skip navigation links so keyboard users can bypass repeated content
- ARIA landmark regions (main, navigation, complementary) on all pages
- Focus management on dialogs, including Escape key support
- Live region announcements, so screen readers are told when content changes
- Autocomplete attributes on contact, login, registration, and password forms
- Text that meets AA contrast on every background in our palette
- Animation that respects your operating system's reduced motion setting, and no animation that loops or runs longer than five seconds
- Pages that reflow without horizontal scrolling at 320 pixels wide and at 200 percent zoom
- aria-hidden on decorative icons and images
- External links that announce when they open a new tab
How we test
Our test suite runs automated accessibility checks against every page, and we run it before shipping any change to a page, a form, or our styling. Automated tools catch roughly a third of what the guidelines cover, so we also test by hand: keyboard navigation, browser zoom, page reflow at narrow widths, and reduced motion.
Known limitations
We would rather tell you where we fall short than claim we are perfect:
- Our logo: the gold "AI" in our wordmark sits below the contrast threshold that body text must meet. The guidelines exempt logos from that threshold, so we have left it as it is. Automated scanners will still report it.
- Third-party payment pages: payments are handled by Stripe's hosted pages. Their accessibility is outside our control.
- Third-party scripts: Google Analytics and Google Fonts load from external origins. We do not control the accessibility of these services.
Ongoing commitment
We review accessibility as part of every new page or feature we build. We aim to respond to accessibility concerns within 5 business days. If a fix is required, we commit to addressing it in the next development cycle.
Feedback and contact
If something on this site stops you from reading content or finishing a task, please tell us. We take every accessibility report seriously, and a report from someone using the site is worth more to us than any test we can run ourselves.
Technical approach
realizedai.ai is built with semantic HTML5, with ARIA attributes applied where native semantics are insufficient. The site is tested for keyboard navigation and is designed to be compatible with common assistive technologies including screen readers.
All accessibility remediation work is version-controlled in our codebase. A detailed compliance record documenting every issue found and the specific fix applied is available upon request.