Where Disability Rights Meet Real Life

One disabled complainant, one access request, and three very different responses from three places.


1. What I first asked for (April 30, 2026)

I filed a 64-page ADA technical-assistance package with the Georgia State ADA Coordinatorโ€™s Office. It was the first program-access complaint ever filed against the State Bar through that channel. I asked for three things any public entity is supposed to have: a visible ADA Coordinator, a published Title II grievance procedure, and public notice of Title II rights.

2. What the State ADA office did with it (May 6 – May 14, 2026)

The State office treated it as a legitimate access concern, called the Bar directly within days, and treated the matter as one involving access to the Barโ€™s programs, services, and activities. The State ADA Coordinator wrote:

The proper routing path for your ADA-related grievances as they relate to the programs, services and activities of the State Bar of Georgia would be to file a grievance with .

When I sent that office a thank-you, it answered in 19 minutes.

3. Where it stands now (June 2026)

The Barโ€™s final position: not subject to Title II. Still no published ADA Coordinator on its website. Still no posted grievance procedure. And the newest grievance, filed against one of the Barโ€™s own lawyers by the only route my disability left open, has gone four days with three emails and no confirmation it was ever received.

The State office answered a thank-you in 19 minutes. The Bar will not answer, in four days, whether a grievance arrived.

A state office that owed me nothing treated my access as real. The disciplinary authority I was forced to use, which owed me a process, treated it as a threat.


Source: State ADA Coordinator engagement record, April 30 – May 14, 2026, and Bar correspondence of record. Quotes verbatim; personal names redacted.

This is what one disabled complainant was sent and shown. You are not alone. Join the club.


[Español: pendiente]


Leave a Reply

Your email address will not be published. Required fields are marked *