Accessibility statement for readyaed.co

WCAG 2.2 AA conformance statement

ReadyAED builds this website for people aged 40 to 60, many reading on a phone in a field or a hallway. Accessibility is part of the build, not an extra step. This statement covers the readyaed.co website. The statement is public, so you can review the target and the current limits.

The target for this website is WCAG (Web Content Accessibility Guidelines) 2.2 Level AA. The build follows the criteria that the team can test today: one main heading per page, heading levels that do not skip, a text alternative on every image, a skip link to the main content, landmark regions and status that never relies on colour alone.

Motion respects the reader's reduced-motion setting, and every page renders its final state without animation. The site is light theme only, and body copy stays at 16 pixels or above for readers in the field. Text contrast targets 4.5:1 for body copy and 3:1 for large text and controls. The site works at phone and desktop widths. Touch targets aim for 44 pixels, and the known issues below record where that target is not met.

An independent audit is not complete. This page does not claim full conformance, and it lists the known issues below.

Known issues

This page tracks the known issues. Each item names the problem and the criterion it fails. The list is not a fixed count. An item joins when a test finds it and leaves when the fix ships.

• Form field borders are too faint. The border measures 1.61:1 on white. It fails the 3:1 target for user-interface components (WCAG 1.4.11, non-text contrast). The border is the only visible boundary on the field. The issue is site-wide. The fix is open.
• Keyboard focus on buttons inside the navy panels is hard to see. The focus ring shows, but its contrast is too low on that surface. It does not meet the 3:1 target (WCAG 1.4.11, non-text contrast).
• Links in the footer are smaller than the 44 pixel touch target that this site sets. The links are reachable, and the target size is the issue (WCAG 2.5.8, target size).

The issues sit in shared page furniture: form fields, the navy call-to-action bands and the footer. Every fix is open. Report a problem or ask about a fix through the Contact page.

How to report a problem

If a page does not work with your assistive technology, contact us through the Contact page. You do not need an account to report a problem. Tell us the page address, what you tried and the technology you use, for example a screen reader, a keyboard, a magnifier or voice control. That detail helps us reproduce the problem. If you use assistive technology and a page fails, that is a defect. Send it to us.