Built to work for everyone who visits.

Our commitment

AMAGID wants everyone to be able to use this site, including people who use screen readers, keyboard navigation, magnification, voice control or other assistive technology. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

We treat accessibility as part of how the site is built and tested, rather than something added on top.

How we build for it

• Semantic HTML. One H1 per page, headings in order, landmarks for the header, navigation, main content and footer, and real buttons and links.
• Keyboard access. Every menu, form, tab and accordion works with a keyboard. Focus is always visible, and a “Skip to content” link is the first thing on every page.
• Contrast. Text and interface elements are designed to meet AA contrast ratios. Our team colors have darker, text-safe versions for use on white.
• Motion. A “Reduce motion” switch in the footer turns animation off, and the site follows your system’s reduced-motion setting automatically.
• Forms. Every field has a visible label. Errors are announced and explained in text, not only by color.
• Content without scripts. Page content is in the HTML, so it stays readable if JavaScript fails or is turned off.
• Media. Videos have captions, and images that carry meaning have text alternatives. [Confirm for video testimonials before launch.]

Why we don’t use an overlay widget

Some sites add a third-party “accessibility overlay”: a toolbar that claims to fix problems automatically. We don’t. Overlays don’t repair the underlying code, they can conflict with the screen readers and settings people already rely on, and they don’t make a site conform to WCAG. We fix issues in the site itself instead.

How we test

Before launch and after significant changes, we check pages with:

• Automated tools such as [axe, Lighthouse]
• Keyboard-only navigation
• Screen readers: [VoiceOver on macOS and iOS, NVDA on Windows]
• Zoom to 200% and 400%, and narrow mobile screens

[Optional: independent audit by a third party, with date.]

Known limitations

We know about these issues and are working on them:

• [Third-party embeds, such as the scheduling widget, may not fully meet WCAG 2.2 AA. An email and phone alternative is always available.]
• [List any other issues found in testing before launch.]

Other ways to reach us

If any part of the site doesn’t work for you, you can do everything it offers another way. Call or text (XXX) XXX-XXXX, email [email protected], or ask for any page, report or document in another format.

Feedback

If you find a barrier on this site, please tell us. It helps to include:

• The page address
• What you were trying to do
• The browser, device and assistive technology you use

Email [email protected] with “Accessibility” in the subject, call (XXX) XXX-XXXX, or write to [Legal entity name], [US mailing address]. Every report goes to the team that builds the site, and we’ll tell you what we changed. [Counsel to confirm whether a designated accessibility contact is required.]

Scope of this statement

This statement applies to amagid.com. It does not cover client websites we build, which have their own statements, or third-party sites we link to.

Last reviewed: [date of last accessibility review].