Accessibility statement

Shop Madeira is a neighborhood program for Madeira, Ohio. We want every neighbor, anyone using assistive technology, anyone with low vision, anyone using only a keyboard, to be able to find a shop, check in, see their stamps, and read every word of our public copy. This page describes our commitments, what we’ve done, where we know we still have work to do, and how to tell us when we get it wrong.

1. Scope

This statement covers the following Shop Madeira surfaces:

• shop-madeira.com, public site, business directory, and resident wallet (desktop).
• m.shop-madeira.com, the same site, optimized for mobile web.
• The Shop Madeira iOS application (iOS 17 and newer).

The merchant portal at merchant.shop-madeira.com and the internal admin console at admin.shop-madeira.com are separate surfaces used by shop owners and our operations team. They are held to the same target, but this statement primarily covers the surfaces a neighbor uses.

2. Conformance target

Shop Madeira targets WCAG 2.2 Level AA. We design and ship against that target, audit ourselves against it before each public release, and treat any AA regression as a P1 bug.

We aim to be substantially conformant with WCAG 2.2 AA for both the web and iOS apps.

3. Measures we have taken

• The design system enforces 4.5:1 minimum text contrast for body copy and 3:1 for large text. Every color token is tested against the surfaces it can land on.
• The serif display face (Fraunces) and the body face (Inter) are paired so that the headline weight never drops below contrast thresholds at the sizes we ship.
• Every interactive component (button, chip, ticket, stamp) is implemented as a real focusable element with a visible focus-visible ring keyed to the copper accent.
• Pages are server-rendered so a screen reader can read the entire navigable tree before the client JavaScript hydrates.
• Forms (sign-up, claim, perk redemption) use real labels, real error messages, and announce error state via aria-live regions.
• The map view ships with a list-view alternative that contains the same shops, hours, and perks, no information is map-only.
• The QR check-in screen pairs the visual code with a six-character text fallback the cashier can type if the camera is unavailable.
• On iOS, every screen supports Dynamic Type up to the largest accessibility size, and every action surfaced in the live-activity widget is also reachable from the main app.
• Motion can be reduced from a single setting in the app, which respects the system “reduce motion” preference by default.

4. Known gaps

We do not yet meet WCAG 2.2 AA in the following places, and we are actively working on each one:

• A small number of AI-generated business cover photos do not have descriptivealt text. They render with a generic “Photo of {shop name}” fallback. We are replacing each one with a human-written description as merchants upload real photos.
• The map clustering animation does not fully respect “reduce motion” on the mobile web. The iOS app already does. A fix is targeted for the next public release.
• The legacy claim-form on Safari 16 has a focus order regression after submitting an ownership document. Safari 17 and Firefox are unaffected.

If you find a barrier that isn’t listed here, please tell us, see Section 7.

5. Compatibility

Shop Madeira is designed to be compatible with:

• The most recent two versions of Chrome, Safari, Edge, and Firefox on desktop.
• Safari and Chrome on iOS 17 and newer.
• Chrome and Firefox on Android 13 and newer.
• VoiceOver (macOS / iOS), TalkBack (Android), NVDA, and JAWS for screen-reader use.
• Keyboard-only navigation (Tab / Shift+Tab / Enter / Space / Escape) on every page.

Shop Madeira does not officially support Internet Explorer or browser versions released more than three years ago.

6. Assessment approach

• We run automated checks (axe-core, lighthouse-a11y) on every pull request as part of CI. A regression blocks the merge.
• We do a manual keyboard and screen-reader pass on every new public-facing page before it ships.
• We commission an external audit annually. The most recent audit was scoped to the resident wallet and the public directory; the next is scheduled for the iOS app.

7. Tell us when we get it wrong

If you encounter a barrier on any Shop Madeira surface, a screen reader cannot find a button, a form rejects a valid input, contrast is too low, a video lacks captions, or you simply cannot complete a task you wanted to complete, please email accessibility@shop-madeira.com with:

• The page or screen (a URL is ideal).
• The device and assistive technology you were using.
• A short description of what you tried and what happened.

We aim to acknowledge accessibility reports within two business days and to fix or schedule a fix for any AA-level barrier within thirty days. If a fix needs to wait longer than that, we’ll tell you why and offer a workaround.

8. Formal complaints

If we have not resolved your accessibility issue within thirty days and you would like to escalate, you may file a complaint with the U.S. Department of Justice under the Americans with Disabilities Act. We’d much rather hear from you directly first, please write to accessibility@shop-madeira.com and give us a chance to fix it.

9. About this statement

This statement is published by LeadTimber LLC, the operator of Shop Madeira. The statement is reviewed at least once a year and any time we ship a substantial change to the resident wallet, the public directory, or the iOS app.