Accessibility at MantelMarketing — part of the craft, not an add-on.
A handmade website should work for every visitor — including people using screen readers, keyboards, magnification, or reduced motion. This page is our standard in plain language: what we hold our own surfaces to, what every site we build ships with, where the gaps are, and how to reach a real person when something is in your way. Write to hello@mantelmarketing.com any time.
Effective
Our commitment
We design and build the MantelMarketing marketing site and customer dashboard to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. That is a target we test against — not a certificate someone handed us. We audit our own surfaces, fix what the audit finds, and publish the honest result here.
Accessibility work is never finished. We treat AA as the floor, aim past it on body-text contrast, and re-test whenever the design system changes.
What we practice today
These are not aspirations — each one was verified in our most recent full accessibility audit (June 10, 2026) across the marketing site, the onboarding wizard, and the dashboard:
Every control works without a mouse — a skip link on every page, visible focus rings, dialogs built on the native element with focus trapped and restored, and menus that close on Escape or a click outside.
One main landmark per page, labeled navigation, an ordered heading outline, and data tables with scoped headers — so a screen reader can map a page before reading it.
Every animation routes through a single reduced-motion check, in CSS and in script. If your system asks for less motion, you get the finished state instantly.
Color comes from a fixed token palette we test with our own contrast script against WCAG AA targets — and where type sits on our terracotta brand color, it stays large enough to keep the ratio honest.
When an audit finds a gap — and audits exist to find gaps — fixes ship ahead of new feature work. The June audit’s accessibility fixes landed before this statement was published.
What every customer site gets
Every site we build ships with the same accessibility baseline — it is part of the build, not an upgrade:
- Semantic HTML with an ordered heading structure and named landmarks.
- Text alternatives on meaningful images.
- Labeled forms, with errors announced to assistive technology.
- Keyboard-navigable menus and controls, with visible focus.
- Color choices checked against WCAG AA contrast targets.
- Reduced-motion preferences respected on every animation.
- Responsive layouts that hold up on small screens.
One honest boundary: this baseline is a build standard, not a compliance service. We don’t certify customer sites against the ADA, Section 508, the European Accessibility Act, or any other statute — legal obligations depend on your industry, your region, and the content you add after launch. If your business carries specific requirements, commission a formal audit — and we’ll gladly fix anything it finds in the work we control.
Known limitations
We would rather name the gaps than pretend there aren’t any:
- Third-party surfaces. Checkout and sign-in run on our payment and identity vendors’ hosted interfaces. We chose vendors with their own published accessibility work, and we pass reported issues along — but we can’t patch their UI directly.
- This statement is a snapshot. It reflects our June 10, 2026 audit. We ship continuously, and a regression can slip in between reviews — when one does, the fastest fix starts with a report.
- Concept previews. The example sites on our marketing pages are openly fictional concept builds. Each preview carries a plain-text description for screen readers, but the preview itself is an illustration, not an operable website.
Report an accessibility issue
If anything on our site or in your dashboard is hard to use with a keyboard, a screen reader, magnification, or any other assistive technology, tell us — email hello@mantelmarketing.com. We answer within one business day. Accessibility reports are triaged like bugs, prioritized by how badly they block you.
It helps to include the page address, what you were trying to do, and the browser and assistive technology you were using — but none of that is required. A one-line “this is broken for me” is enough to start.
For everything else, our contact page has the rest.
This statement
Prepared , based on a full audit of every surface completed June 10, 2026. We review this statement — and re-audit the surfaces behind it — at least every six months, and sooner after any major release or design-system change. The date below moves when the words do.