Accessibility Statement

Last updated: October 2026

Real26 is committed to making real26.com accessible to as many people as possible, including people with disabilities. We are working toward conformance with WCAG 2.2 Level AA and continuously test the site as it evolves.

Measures we take

Keyboard navigation: every action — including the Private Alpha application, the prompt bar and the privacy settings — works with the keyboard alone. Dialogs keep focus inside while open, close with Escape, and return focus to the button that opened them.
Focus visibility: every interactive element shows a clear focus outline.
Reduced motion: when your system asks for reduced motion, the animated world is replaced by a still image and other animations are switched off.
Color contrast: text colors are chosen to meet WCAG AA contrast ratios against the dark background.
Semantic headings and labels: one main heading per page, labelled landmarks, and visible labels for every form field.
Form error announcements: errors are written next to the field, the field is marked invalid, focus moves to the first field that needs attention, and the error is announced to screen readers. The application is split into four short steps, and the current step is announced.
Alternatives for animated content: the animated world on the home page has a text description, and everything it shows is also described in the page text. It pauses when it is not visible.
Zoom and reflow: the site works at 200% and 400% zoom and on small screens without horizontal scrolling.

Known limitations

The live labels inside the animated world (object names, the simulation clock and the scenario results) are visual only. The world is described as a whole in its text alternative instead.
The prompt bar on the home page is a demonstration. It replays the animation rather than generating a real result.

How we test

Automated checks with axe-core (WCAG 2.2 A/AA rules) on desktop and mobile layouts; keyboard-only walkthroughs; reduced-motion, 200% and 400% zoom checks; tested in current Chromium-based browsers. Manual testing with the NVDA and VoiceOver screen readers is part of our pre-launch review.

Feedback and contact

If something on this site is hard to use, please tell us and we will help and fix it. Accessibility coordinator: [ACCESSIBILITY COORDINATOR NAME], [email protected]. We aim to respond within five business days.

Last reviewed

This statement was last reviewed on October 2026.