Accessibility statement

Last reviewed: 7 August 2026. This statement is updated when a known limitation is fixed or a new one is found.

Our conformance target

We build this site to conform to the Web Content Accessibility Guidelines (WCAG) version 2.2 at Level AA, the standard most public bodies and courts reference. WCAG 2.2 AA includes the earlier 2.1 AA criteria and adds several of its own, and we treat the whole set as a release condition rather than an aspiration. Conformance is a claim about specific, testable success criteria, so this page lists the ones that matter most for a form-driven tool instead of offering a badge with nothing behind it.

Concretely, we hold the interface to these WCAG 2.2 AA success criteria, among others:

• 1.4.3 Contrast (Minimum). Body text is designed to meet at least a 4.5:1 contrast ratio against its background, and large text at least 3:1. The site header is deliberately opaque so the effective text background is defined and the ratio is actually measurable.
• 2.1.1 Keyboard. Every control, including the estate navigator and both calculators, is operable from the keyboard alone, without a pointing device.
• 2.4.7 Focus Visible. The element with keyboard focus shows a visible focus indicator, so a keyboard user can always see where they are.
• 2.4.11 Focus Not Obscured (Minimum), new in WCAG 2.2. A focused control is not fully hidden behind sticky content when it receives focus.
• 1.4.11 Non-text Contrast. Interactive boundaries, such as input borders and buttons, meet at least a 3:1 contrast ratio so they are perceivable.
• 2.5.8 Target Size (Minimum), new in WCAG 2.2. Interactive targets are sized, or spaced, so they are not difficult to activate on a touch screen.

A “skip to main content” link is the first focusable element on every page, each page carries exactly one first-level heading that names its subject, and the primary navigation wraps rather than scrolling off-screen on a narrow phone, so no section becomes undiscoverable at small widths.

Known limitations

Naming what is imperfect is part of a truthful statement, so here is what we are still working on. If any of these blocks you, the report channel below is the fastest way to get it prioritised.

• The calculators render their results as live-updating text. We test them with common screen readers, but complex assistive-technology and browser combinations may announce a recalculated result inconsistently.
• Some source documents we link to are hosted by courts and legislatures as PDFs we do not control. Those files may not meet the same standard as our own pages, and their accessibility is the publisher’s responsibility, not ours.
• Long source and comparison tables can be demanding to read with a magnifier at high zoom. We are continuing to review table markup and small-screen reflow.
• We have not yet completed a full manual audit with every major screen reader on every template, so a specific control on a specific page may fall short of the criteria above.

How to report a barrier

If you hit something on this site that you cannot use, tell us and we will treat it as a correction. Email the site operations address atprivacy@estatesettlementcost.com, or use the contact page. To help us reproduce the problem, please include the page address, the browser and assistive technology you were using, and what you were trying to do when the barrier appeared. We aim to acknowledge accessibility reports and describe a fix or a workaround, and we will not ask you to send any private case details to report a barrier — the tools keep your entries in your browser and we do not need them.