Accessibility statement

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across startuphelms.com. "Partially conformant" means some parts may not yet fully meet the standard. We will change this status only after an audit confirms it.

What we have built in

• Text contrast of at least 4.5:1, and at least 3:1 for focus rings and other non-text UI, checked against our color tokens.
• Visible focus on every link, button and field (2px blue outline).
• Touch and click targets at least 44 by 44 pixels.
• One H1 per page, no skipped heading levels, and header, navigation, main, aside and footer landmarks.
• Zoom is never blocked, and pages reflow at 320px wide without sideways page scrolling.
• Accordions and FAQs use native disclosure elements, so they work with the keyboard and without JavaScript.
• Pros and cons have hidden "Pro:" and "Con:" prefixes, and labels such as Sponsored are always words, never color alone.
• Esc closes menus and sheets; focus is held inside an open sheet and returned when it closes.
• No auto-playing media, no auto-advancing carousels, and reduced-motion settings are honored.

Known limitations at launch

• Wide comparison tables scroll sideways inside their own area on small screens. Each has a "Scroll sideways for more columns" hint and is keyboard-focusable, but it can still be harder to follow with a screen magnifier.
• Our own product screenshots are not published yet. When they are, each will carry a caption and alt text; until then the frames show a text placeholder.
• The logo files use live text in the display font and may render inconsistently in some assistive tools until they are converted to outlines.
• Vendor websites we link to are outside our control and may not be accessible.
• The cookie banner, forms and newsletter sign-up are built to the standard but have not yet been tested with every major screen reader.

How we test

Before launch we check templates with automated tools and keyboard-only use. We plan a manual review with screen readers and an external audit after launch, and we will update this page with the date and results: [Audit date and provider].

Feedback and alternative formats

If you meet a barrier, or need content in another format, email [email] or write to [Legal entity name], [Registered address]. Tell us the page URL, what you were trying to do and the device or assistive technology you use. We acknowledge messages within [response time to confirm] and tell you what we will fix and when.