Accessibility statement

Statement prepared October 3, 2026.

Conformance status

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Today the site partially conforms: some parts don’t yet meet the standard, and they’re listed under known issues below. Manual testing with screen readers is still to be done; we’ll update this page with the results and dates.

What we built in

• Structure you can navigate: real headings, landmarks, lists and tables, a skip link, and link text that says where it goes.
• Keyboard access: every control works without a mouse, with a visible focus outline. Menus close when focus leaves them, so they don’t cover what you’re working on.
• Readable text: body text is 18 to 22 pixels, interface text is at least 14, and the layout adapts when you enlarge text or zoom.
• Meaning beyond color: diagrams have a text title, a description and a plain-English line nearby; readings outside the target are hatched as well as tinted; results such as PASS are written out.
• Forms that forgive: visible labels, required fields marked for screen readers, error messages that say how to fix the problem, no time limits and no CAPTCHA puzzles.
• Text-first contact: text, call and email appear together in the header, the footer and the contact page; on phones, a bar at the bottom offers Text first. Relay calls are welcome, and we can meet by video with live captions.
• No overlay widgets: we don’t use accessibility overlay plugins. They don’t fix the underlying code and can get in the way of the screen readers and settings people already rely on.

What we’ve tested, and when

• October 3, 2026: Automated checks with axe-core (WCAG 2.2 A and AA rules) on every page, at desktop and phone widths, with every expandable answer open and closed. Result: No violations.
• October 3, 2026: Reflow at 320 and 390 pixels wide, and text spacing increased per WCAG 1.4.12 at 1280 and 1366 pixels. Result: No sideways scrolling found.
• October 3, 2026: Keyboard checks of the header menus: focus leaving a menu closes it, and Escape closes only the menu you’re in. Result: Passed in the automated test script.

Still to do before launch, by hand: VoiceOver on iPhone and on a Mac, NVDA on Windows, a keyboard-only walk through every page type, and completing the inquiry form with a screen reader. Automated tools catch only part of what matters, which is why those passes are listed here until they’re done.

Known issues

• Small labels inside some diagrams. On phones, some drawings keep their labels readable by scrolling sideways inside their frame, but a few labels inside drawings are still smaller than 14 pixels at some widths. The legend, the plain-English line and the caption under each one carry the same information.
• No site search yet. The resources page has a table of contents and a glossary; text or email us if you can’t find something.
• Documents: our printable sheets are web pages, so they work with screen readers. If you need something in another format, ask.
• Our software (Hearing Loop Designer and BroadcastPlan Pro) runs in a web browser on its own sites and isn’t covered by this statement. If you need something from it in another format, ask us.
• Sending the form passes your message through Web3Forms, a delivery service. If the form doesn’t work for you, email or text us and we’ll take it from there.

Tell us about a barrier

If something on this site is hard to use, we want to know, and we’ll fix it or get you the information another way. Text is often easiest:

• Text 847-212-4216
• Email dave@equalaccessaudio.com
• Call 847-212-4216 (Relay calls welcome; text works too)

It helps to tell us the page, what you were trying to do, and, if you’re comfortable sharing it, the device, browser or assistive technology you use. We reply within 2 business days.