U.S. AA Meeting Accessibility Report

Executive summary

Broad directory reach; incomplete proof of real-world access

The directory provides national geographic navigation and can carry useful access signals such as transit context, a “Wheelchair Access” meeting label, online meeting URLs, and conference-phone details. The data does not support a national estimate of wheelchair-accessible venues, ADA compliance, current public-transit service, meeting capacity, language accommodation, or whether a person can successfully attend at a particular time.

Findings

What the current site can establish

Interpretation

Accessibility is more than a nearby map point

For a meeting seeker, access can depend on several separate questions:

• Information access: Can the person find a current time, place, format, and source link?
• Transportation access: Can the person reach the location at the scheduled time?
• Physical access: Can the person enter, move through, and use the venue?
• Remote access: Is there a working online link or dial-in option?
• Communication access: Are language, hearing, vision, and other accommodations described?
• Program fit: Is the meeting open or closed, and do its format and audience labels match what the attendee needs?

The current MyMeetings data model addresses parts of information, transportation, remote, and program-fit discovery. It does not contain enough standardized, audited fields to score physical or communication accessibility nationally.

Methodology

How the metrics were produced

1. Snapshot date: August 17, 2026.
2. Jurisdiction count: counted JSON files in src/data/locations/states and checked the city API directory contract, which rejects responses that do not contain 51 jurisdictions.
3. Route count: counted <url> entries in the generated city sitemap. We separately confirmed 51 entries in the state sitemap.
4. Enriched-place count: parsed every city object in the 51 local state JSON files: 611 records.
5. Transit context: counted a record when its transitInfo field was non-empty: 603 of 611, or 98.690…%, rounded to 98.7%.
6. Service-office references: counted non-empty local intergroup objects (455) and those with a URL (230). The 37.6% figure is 230 divided by 611, rounded to one decimal place.
7. Feature support: inspected the meeting type mapping and meeting interface used by city and detail pages for wheelchair, online URL, and conference-phone fields.

Limitations

What these numbers must not be used to claim

• The 32,075 routes are not 32,075 meetings, venues, cities with active meetings, or verified accessible locations.
• The 611 enriched records are an editorial subset, not a random or representative sample of U.S. communities.
• A transit note may name a system without proving that service runs near a venue or at meeting time.
• A missing wheelchair label does not prove inaccessibility; a present label does not independently verify current ADA compliance.
• Online links, phone numbers, addresses, and schedules can change after the snapshot.
• The audit does not measure meeting quality, recovery outcomes, anonymity practices, safety, cost of travel, broadband availability, or digital literacy.

Practical recommendations

Verify the access details that matter to you

Before traveling, review the meeting detail page and follow its source listing when available. Contact the local group, intergroup, central office, or venue when you need confirmation about step-free entry, elevators, accessible restrooms, service animals, hearing or language accommodations, parking, public transit, or online access.

For general U.S. public-accommodation requirements, see the U.S. Department of Justice’s ADA Title III guidance. For AA’s own meeting and service-office search, see Find A.A.. These links provide context; neither source validates the MyMeetings metrics.

Citations & audit trail

Sources used

1. MyMeetings meeting directory: public national directory and jurisdiction framing.
2. MyMeetings state sitemap: 51 state-level route entries in the snapshot.
3. MyMeetings city sitemap: 32,075 city/community route entries in the snapshot.
4. MyMeetings company and meeting-data methodology: sourcing, refresh, verification, and correction process.
5. U.S. Department of Justice, ADA Title III: general public-accommodation context.
6. Alcoholics Anonymous, Find A.A.: official AA service-office search.