Accessibility

We aim at WCAG 2.2 Level AA. This page describes what is actually tested rather than claiming a conformance level, because "100% ADA compliant" is a claim a build cannot make and a statement of intent is not a substitute for a keyboard that works.

What is checked on every build

• An automated axe scan of the marketing page, sign-in, seller submission, and the overview, discover, deals, buy-box, buyer and settings screens. A serious or critical finding fails the build.
• Exactly one main landmark and one first-level heading per page, with no skipped heading levels.
• No informational text below 11px.
• A visible focus indicator on every control reachable by keyboard.
• Every form field programmatically labelled.
• No horizontal scrolling at 200% zoom or at a 390px viewport.
• No long or looping animation when the operating system asks for reduced motion.

What was fixed as a result

The first run of that scan found colour contrast below the required ratio on every screen — one muted grey-green used across roughly a hundred and thirty elements — and informational text as small as 7px. Both were corrected: the muted text colours were darkened to meet 4.5:1 against the surfaces they actually sit on, and the smallest text was raised to 11px. The data density the product depends on was kept; only the floor moved.

What automation cannot tell us

An automated scan catches roughly a third of accessibility problems — the mechanical ones. It cannot judge whether a focus order makes sense, whether an error message is useful, or whether a chart is understandable without its colours. Those are checked by hand, and the steps are written down so the check is repeatable rather than remembered.

Known limitations

• No audit by an external accessibility specialist has been performed.
• No testing with real assistive-technology users has been performed.
• Screen-reader testing has been by inspection of names, roles and states rather than by a person using JAWS or NVDA daily.
• Data-dense tables remain demanding to navigate even when technically conformant.

If something is unusable

Please write to accessibility@estatemvp.com and describe what you were trying to do and where it stopped working. A specific report is worth more than a general one, and we would rather fix the thing you hit than guess.