I want to be careful with this piece. The ADA is a civil rights statute, the regulations implementing it run hundreds of pages, and the case law is alive — there are new settlements and court rulings every quarter. What follows is a plain-English summary of what the federal regulations and DOJ guidance say about museum audio guides, plus the implementation patterns I see most often inside the category. Where I cite a rule, I link to the source. Where I describe what museums do, I'm describing convention, not law. Treat this as a starting point for a conversation with your accessibility coordinator and your counsel, not a substitute for either.
Does the ADA cover museums at all?
Yes — under one of two titles, depending on whether the museum is public or private. Title II of the ADA covers state and local government entities, which includes municipal museums, public-university museums, and state historical sites. Title III covers "places of public accommodation," which expressly includes museums, galleries, and other places of public display or collection. The DOJ's Title III Technical Assistance Manual lists museums among the twelve categories of public accommodation that must comply.
The practical effect is that virtually every museum in the United States — public or private, large or small — has obligations under one of the two titles. The substantive duties are similar: nondiscrimination on the basis of disability, removal of architectural barriers where readily achievable, and the "effective communication" requirement that drives most of what museums do around audio guides. The procedural and enforcement details differ, and the new 2024 web rule applies only to Title II entities, which is the largest single divergence between the two paths right now.
What does "effective communication" mean for an audio guide?
It means the visitor with a disability gets a communication experience as effective as the visitor without one — through whatever "auxiliary aids and services" the situation requires. The DOJ's guidance on effective communication frames it as an outcome rather than a device list: the museum has to evaluate the nature, length, complexity, and context of the communication and provide aids appropriate to that context, giving primary consideration to the disabled person's stated preference.
For a museum audio guide, that translates into a recurring set of accommodations the category has converged on: a written transcript or captions for visitors who are deaf or hard of hearing; a verbal/audio description track for visitors who are blind or have low vision; an interface that works with the operating system's screen reader; and an assistive listening device or hearing-loop-compatible output for visitors who need amplification. None of those four are explicitly named in the ADA text — they're how the category implements "effective communication" in 2026.
The escape hatch in the rule is "undue burden" — defined as significant difficulty or expense relative to the entity's resources. An undue-burden defense is real but narrower than most institutions assume, and it does not relieve the entity of the duty to provide an alternative aid where possible. Phone-based audio guides have, in practice, made the undue-burden defense harder to invoke for things like transcripts, because the marginal cost of a transcript when the audio was generated from a script is effectively zero.
What does the 2024 DOJ web rule actually require?
The 2024 rule adopts WCAG 2.1 Level AA as the technical standard for web content and mobile apps of Title II entities — i.e., public museums and the public-university museums that fall under state government. Published as a final rule in April 2024 and effective in stages, the rule covers both web content and mobile applications "provided or made available" by state and local governments, including by contractors and vendors operating on the entity's behalf — which is the clause that pulls third-party audio guide platforms inside the museum's compliance perimeter when the museum is public.
Compliance dates were originally April 24, 2026 for entities with populations of 50,000 or more and April 26, 2027 for smaller entities and special districts. In April 2026, DOJ issued an interim final rule extending those by twelve months: April 26, 2027 for the larger group and April 26, 2028 for the smaller group.
The rule carves out specific exceptions: archived content kept unchanged for recordkeeping, conventional electronic documents (Word, PDF, Excel, presentations) posted before the compliance date, third-party user-generated content posted without entity involvement, password-protected individual account documents, and legacy social media posts predating the deadline. Most museum audio guides won't fit any of those exceptions, so a public-museum audio guide deployed on the museum's website or in its mobile app is squarely inside scope.
Private (Title III) museums are not covered by the 2024 web rule. They sit under the older Title III framework, where DOJ has long taken the position that public-accommodation websites are covered but has not adopted a formal technical standard. In practice, federal court settlements and DOJ consent decrees with private museums have repeatedly required WCAG conformance — the Museum of Crime & Punishment settlement, for instance, required WCAG 2.0 Level AA on the museum's website and audio descriptions for tours and exhibits. The legal posture is "no formal rule, but the de facto standard is WCAG 2.1 AA."
What does a museum have to provide for deaf or hard-of-hearing visitors?
At minimum, a transcript or captions for audio content in permanent exhibitions, plus an assistive listening path where amplification is the appropriate accommodation. Federal settlements with museums going back over a decade have repeatedly framed the obligation in those terms. The most-cited recent example is the Palm Springs Art Museum settlement, in which the museum agreed to provide captions or transcripts for all audiovisual programs in permanent exhibitions, captions or transcripts for temporary programs given at least five days' notice, and sign language or oral interpreters, assistive listening devices, or real-time captioning for public programs.
For an audio guide specifically, the operational implementation looks like this: every stop's narration has a synchronized transcript available on the same device the visitor is listening on, the transcript is reachable via screen reader, and the platform supports the visitor's own hearing aids or cochlear implants through the device they're carrying. Phone-native audio guides inherit the operating system's Live Captions and Bluetooth pairing for hearing devices, which is the structural reason the phone-based model has, by accident, made this dimension considerably easier than the handset model ever was.
A note on hearing loops: museums with installed hearing-loop systems in lecture halls or theaters typically maintain them as a separate program, not as part of the audio guide. The audio guide itself doesn't usually replace a hearing loop; it works alongside one.
What does a museum have to provide for blind or low-vision visitors?
An audio description path and a screen-reader-accessible interface — and increasingly, both as a default, not an opt-in. This is the dimension that has changed the most in the past five years. "Audio description" in a museum context is not the same as reading the wall label out loud; it's a separate script that describes visual elements — composition, color, scale, the position of figures, materials, technique — in language that doesn't presume sight. Programs like MoMA's Art inSight and the verbal-description tradition at the Smithsonian have been refining the practice for decades; the practical guidance from inclusive-museum researchers is consistent on the structure (subject and overview first, then composition and detail, then technique, with sensory vocabulary that doesn't rely on vision).
Major US institutions deliver this in different shapes. MoMA hosts verbal descriptions of works in its collection on the Bloomberg Connects app, alongside transcripts of standard audio guides and assistive-listening technology for artworks with sound. Smaller institutions typically deliver audio description as a parallel track inside the same phone-based guide that hosts the standard narration — selectable on stop, often signposted in the QR landing page so a visitor with low vision can land on the right track at the start of a visit.
The screen-reader requirement is structural. A web-based audio guide that fails to label its buttons, doesn't expose a logical heading hierarchy, or traps focus inside a play overlay will fail WCAG 2.1 AA on multiple criteria simultaneously. The right test isn't whether the page "supports" screen readers; it's whether a visitor using VoiceOver or TalkBack can land on the QR code, identify the tour, start the right stop, and pause when needed without a sighted assist.
Is "audio description" the same as a transcript?
No, and treating them as the same is one of the most common implementation mistakes in the category. A transcript is a written version of the narration — it serves deaf and hard-of-hearing visitors and visitors who prefer to read. An audio description is additional narration of visual content for blind and low-vision visitors — it conveys what a sighted visitor sees when standing in front of an object. The transcript supports the visitor who can see the object but can't hear the audio; the audio description supports the visitor who can hear the audio but can't see the object.
In practice, the two need different drafting. A transcript can be generated from the script and lightly cleaned. An audio description needs to be written separately, by someone trained in the convention, often in consultation with blind and low-vision visitors. Several Convo customers have asked us about this, and the honest answer is that good audio description is editorial work the platform can support but cannot fully replace — curators or trained describers write the description; the platform handles delivery, translation, and update. For a deeper treatment, see our companion piece on audio description for museum visitors.
How does this apply to a phone-based audio guide specifically?
A phone-based guide inherits the operating system's accessibility stack, which makes some things easier and some harder. Easier: VoiceOver, TalkBack, dynamic type, captioning, Bluetooth hearing-device pairing, and high-contrast modes are all present on the visitor's own device and "free" in the sense that the museum doesn't need to ship hardware to access them. Harder: web-based guides have to be built to WCAG 2.1 AA from the start, because the same web technologies that make a guide universally accessible also make it trivially easy to ship one that fails accessibility audits.
The dimensions a museum should ask any vendor about — and that a public museum's procurement team must ask under the 2024 web rule — include keyboard navigation through every stop, semantic HTML with proper landmark structure, ARIA labels on all interactive controls, focus management that doesn't trap the visitor in a player, color contrast that meets the 4.5:1 ratio for body text, and captions or transcripts available on the same surface as the audio. None of those are exotic; they're the WCAG 2.1 AA baseline. The piece on WCAG for museum audio guide web apps goes deeper on the technical criteria.
There's also a structural advantage worth naming: when audio is generated from a curator-approved script, the transcript is the script. There's no separate transcription workstream, no "we'll get to that next quarter," and no version skew between the audio and the text. The same is true for translation — the transcript exists in every language the audio exists in, on day one.
Where this article ends and your counsel begins
A short, important section. Nothing in this piece is legal advice. I run a platform in this category and I read the regulations carefully, but I am not your lawyer, and ADA interpretation is genuinely litigated territory. The federal court interpretations of Title III's website-accessibility obligations differ across circuits. The 2024 Title II web rule has already been extended once and could be modified again. State accessibility laws layer on top of federal ones, sometimes with stricter standards (Unruh in California, the New York State Human Rights Law, the Washington Law Against Discrimination). Your specific situation — your museum's structure, funding sources, contracts with audio guide vendors, and existing accessibility complaints — matters more than any general article on the regulations.
What this piece is for: the working vocabulary, the major rule changes, and the implementation conventions you'll want to know before a conversation with your accessibility coordinator, your in-house counsel, or the disability-rights consultant your board may ask you to engage. Use it as orientation, not as a basis for compliance decisions.
FAQ
The short version
For public museums, the 2024 DOJ web rule sets a clear technical floor (WCAG 2.1 Level AA) with extended compliance dates of April 2027 and April 2028 depending on entity size. For private museums, no formal technical standard has been adopted, but federal courts and DOJ settlements have made WCAG 2.1 AA the de facto baseline. For all museums, the underlying obligation is "effective communication," which for audio guides means a transcript track, an audio description path, a screen-reader-accessible interface, and an assistive listening path — all four, considered together, against the visitor populations you actually serve.
If you're building toward that bar, the companion pieces on WCAG for museum audio guide web apps and audio description for museum visitors go a level deeper. If you're orienting before a conversation with counsel, this article and ADA.gov are the two sources to start from. And for a broader category map, the accessibility hub collects the rest of the series.
About the author
Eric Duffy is the founder of Convo, a platform that lets museums and cultural institutions publish multilingual audio tours their visitors can have a conversation with. He writes about the practice of museum interpretation from inside the category, drawing on the regulations themselves, conversations with accessibility coordinators at US institutions, and the implementation patterns the AI audio guide category has converged on. He is not an attorney, and nothing he writes is legal advice. Reach him at eric@convo.app or on LinkedIn.