Accessibility

This site should work for everyone who visits it.

Our target is WCAG 2.2 Level AA. This page records what we have done, what we know is still imperfect, and how to tell us when something blocks you. Last updated September 2026.

What we have done

Page content renders without depending on JavaScript or scroll animation, so nothing is invisible while scripts load. Motion effects are removed entirely when your device requests reduced motion.

Body and supporting text meets or exceeds the 4.5:1 contrast requirement on our navy background, and supporting text has a 14 pixel floor. Every interactive element has a visible keyboard focus indicator.

The mobile menu is a real dialog: it can be opened and closed from the keyboard, traps focus while open, closes on Escape, returns focus to the menu button, and is fully removed from the page and from screen readers when closed. Icon-only controls carry text labels, and primary tap targets are at least 44 by 44 pixels.

Pages use one main landmark, ordered headings, semantic lists and tables, and text alternatives for meaningful images. Decorative graphics are hidden from assistive technology. Forms use real labels, correct input types, and inline error messages that are announced rather than shown only by color.

What we know is still imperfect

Some data-dense charts in our research reports communicate through position and color. Each one is accompanied by the underlying numbers in a table or a downloadable dataset, but the charts themselves are not fully described.

Our scheduling and analytics tools are third-party embeds. We chose providers that publish accessibility documentation, but we do not control their markup. If a booking embed blocks you, email us and we will schedule by email instead.

Long guides use in-page anchors and a sticky table of contents. It is keyboard-reachable, but the reading experience on a small screen with magnification is not as good as it should be yet.

How we test

We test with keyboard-only navigation, automated audits in Chrome Lighthouse and axe, contrast checks against our published color tokens, reduced-motion and no-JavaScript renders, and mobile viewport review. Automated testing does not catch everything, which is why the report path below matters.

Tell us about a problem

Email sales@momentence.com with the page address, what you were trying to do, and the browser or assistive technology you were using. We reply within four business hours during the week, and we will tell you plainly whether we can fix it quickly or need longer.

If something on this site prevents you from getting information you need, we will provide that information another way, by email, phone, or a plain-text document, at no cost.