Accessibility

We want this site to be usable by everyone, including people who browse with a screen reader, navigate by keyboard, need magnification, or find motion uncomfortable.

We are working to the Web Content Accessibility Guidelines 2.2, Level AA. We believe the site substantially conforms, but it has not yet been audited by an independent third party, so we do not claim full conformance. Where we fall short, we would rather say so here than let you find out.

• Target standard — WCAG 2.2 Level AA.
• Current status — partially conformant. Most of the standard is met; the known exceptions are listed in section 04.
• Assessment method — internal review during development, including contrast measurement of the full palette against both surfaces and keyboard testing of every interactive component. No external audit has been carried out.
• Planned audit — no date has been published yet. This statement will be updated when one is set.

Reading and contrast

• Body text is 17px at a 1.65 line height. Nothing that carries meaning is set in a light weight at small sizes.
• Text contrast was measured rather than estimated: body copy runs about 8.4:1 on the dark surface and 6.8:1 on the cream one, against a 4.5:1 requirement.
• Wide letter-spacing is reserved for short labels and never applied to paragraphs, where it harms reading for dyslexic users.
• Layouts reflow to 320px without horizontal scrolling, and text can be resized to 200% without loss of content.

Motion

• Every animation honors the operating system's reduce-motion setting. The hero background stops, scroll reveals become instant, and no parallax runs.
• Nothing flashes, and no animation loops faster than three seconds in the reader's field of view.
• No content moves or auto-advances in a way that cannot be paused — the one auto-scrolling element, the client logo wall, pauses on hover and carries no information.

Keyboard and focus

• Every interactive element is reachable and operable by keyboard, in a logical order.
• A visible focus indicator is drawn on keyboard focus, offset from the element so it is never obscured.
• A skip link is the first focusable item on every page.
• Accordions, tabs, and the intake form are built from real buttons, labels, and fieldsets rather than styled divs.

Structure and assistive technology

• One h1 per page, with headings in order and no levels skipped.
• Landmarks — header, nav, main, footer — are marked up semantically.
• Expandable sections expose their state with aria-expanded and aria-controls.
• Every chart carries a text alternative describing what it shows, and every value plotted also appears as text on the page, so no figure is available only by hovering.
• Decorative images and background layers are hidden from assistive technology.
• Form fields have persistent visible labels, not placeholder text standing in for them.

We are aware of the following and intend to address them. If one of them is blocking you, tell us and we will prioritize it.

• The charts have text alternatives and on-page labels, but no tabular view of the underlying series. A screen reader user gets the summary and the labelled values, not a cell-by-cell table.
• The unit chart comparing 500 touches with 50 conveys a ratio visually. It has a text alternative stating both counts and the reply rate, but the density itself is not conveyed non-visually.
• The site has not been tested with every combination of assistive technology and browser.
• Third-party content embedded in future — video, scheduling widgets, a chat tool — may not meet this standard, and we will assess anything before adding it.
• PDFs and documents sent during an engagement are not yet produced to a tested accessibility standard.

If something on this site stopped you, we want to know. A description of what you were trying to do and what happened is enough — you do not need to know which guideline it relates to.

• Email accessibility@mogul.com.
• If you would rather write, ask at the same address for our postal address.

We aim to acknowledge promptly and to tell you what we intend to do and when. If you need information from this site in another format, ask and we will provide it.

If you are not satisfied with our response, you may escalate to the body responsible for accessibility enforcement in your jurisdiction.We would rather resolve it directly, and we will not treat a complaint as adversarial.