All state guides » Georgia Title II accessibility
Georgia Title II accessibility: April 2026 deadline + GTA state-agency standard + Atlanta nondiscrimination ordinance
Georgia public-entity websites face the federal DOJ Title II rule (April 2024) with its April 24, 2026 WCAG 2.1 Level AA deadline for entities serving 50,000 or more (April 24, 2027 for smaller entities and special-purpose districts). Georgia adds two layers. The Georgia Technology Authority (GTA) maintains a state-agency accessibility standard that references WCAG conformance and feeds into the state IT procurement process. For entities operating in the City of Atlanta, the city's nondiscrimination ordinance covers disability discrimination in public services. Georgia does not have a damage-multiplier statute equivalent to California's Unruh Act; civil-rights remedies in Georgia rely primarily on federal causes of action.
Short answer: if your entity is a Georgia state agency, county, municipality, school district, public university (University System of Georgia or Technical College System of Georgia), library system, or special authority, you are covered by DOJ Title II and must meet WCAG 2.1 Level AA on your website by April 24, 2026 (population 50,000+) or April 24, 2027 (smaller). The Georgia Technology Authority standard applies to state agencies through procurement. The Atlanta nondiscrimination ordinance adds a city-level layer for Atlanta entities. No state damage-multiplier statute. Site Brace audits any Georgia public entity for $149 flat. Try a free single-page check on your homepage first.
The federal Title II deadlines:
- April 24, 2026: public entities serving populations of 50,000 or more.
- April 24, 2027: public entities serving populations under 50,000, and all special-purpose districts regardless of population.
Both deadlines apply to website content and mobile apps. WCAG 2.1 Level AA is the named conformance standard. Source: 28 CFR Part 35, published in the Federal Register April 24, 2024.
The rules that apply in Georgia
1. ADA Title II (federal)
The DOJ's April 2024 final rule is the load-bearing requirement for Georgia public entities. Coverage and deadlines as above. See the DOJ Title II primer for the federal-rule overview.
2. Georgia Technology Authority accessibility standard
The GTA, the state's enterprise IT authority, maintains accessibility expectations for Georgia state-agency information systems and digital services. These expectations are operationalized through the state IT procurement process: vendors selling to state agencies are expected to substantiate WCAG conformance, and state-agency contracts often incorporate accessibility language. The GTA standard applies to state agencies and the University System of Georgia procurement context; it does not directly cover counties, cities, school districts, or local authorities, which fall under the federal DOJ Title II rule for their own websites.
3. Atlanta nondiscrimination ordinance
The City of Atlanta has a nondiscrimination ordinance that covers disability discrimination in public services (Code of Ordinances, City of Atlanta, Part II, Chapter 94). For entities operating within Atlanta, the ordinance adds a local-enforcement layer through the Atlanta Office of Equity, Diversity, and Inclusion. The ordinance does not displace the federal Title II rule; both apply concurrently to Atlanta city government and other entities operating in the city.
4. State human-rights remedy
Unlike California's Unruh Act or New York's Human Rights Law, Georgia does not have a broad state civil-rights statute that creates an independent cause of action for disability discrimination by public entities. Plaintiffs in Georgia rely primarily on federal ADA claims and Section 504 of the Rehabilitation Act for state-and-local government accessibility cases.
For most Georgia public entities, the federal Title II rule is the load-bearing requirement. State agencies have the GTA procurement layer on top. Atlanta entities have the city ordinance on top of that.
Which Georgia entities are covered
Coverage is broad:
- All Georgia state agencies, departments, boards, and commissions
- 159 counties (Georgia has the second-most counties of any state, behind Texas)
- Approximately 530 incorporated cities and towns
- 180 school districts (county and independent city)
- 26 institutions in the University System of Georgia (including UGA, Georgia Tech, Georgia State, Kennesaw State, Augusta University, Georgia Southern, and the regional state universities)
- 22 colleges in the Technical College System of Georgia
- Public library systems (regional library systems serving multiple counties are common in Georgia)
- Special authorities (development, housing, hospital, water and sewer, transit including MARTA, port authorities, and others)
The federal population threshold determines which deadline applies. Fulton County (1.07M), Gwinnett County (980K), Cobb County (770K), DeKalb County (765K), and Atlanta (510K), Columbus-Muscogee (200K), Savannah-Chatham (300K combined), Augusta-Richmond (200K), and Macon-Bibb (155K) fall under April 24, 2026. Smaller rural counties and small cities have until April 24, 2027.
What we typically find on a Georgia public-entity site
The municipal CMS ecosystem in Georgia looks like the rest of the country, with CivicPlus, Granicus, Revize, OpenCities, and a meaningful share of cities running custom WordPress builds. Georgia's larger county and city sites have iterated on accessibility; small-county and small-city sites carry significant legacy debt.
| Finding | axe-core rule | Typical cause |
|---|---|---|
| Untagged PDFs (board agendas, RFPs, open-records requests, permit forms) | Manual finding | PDFs exported from Word without accessibility tagging |
| Color contrast on navigation, calls to action, and table cells | color-contrast |
Vendor CMS template colors that fail 4.5:1 |
| Form fields without labels on permit and open-records request forms | label |
Custom form builders and vendor form tools that style placeholder text as label |
| Spanish-language toggle generating inaccessible markup | label, color-contrast |
Translation tools inserted without accessibility verification; metro Atlanta and Dalton-area counties have meaningful bilingual populations |
| Small-county-site clutter from older CMS or legacy custom builds | Various | Georgia has many small rural counties on circa-2010 platforms with significant accessibility debt |
| Streaming-video board archives without captions | Manual finding | Live-streamed county-commission and city-council meetings posted without post-production captioning |
| aria-label on generic elements | aria-prohibited-attr |
CMS theme customizations or overlay injection. See aria-label on a div. |
| Heading hierarchy mistakes on department pages | heading-order |
CMS WYSIWYG editors that allow staff to skip heading levels |
Notes on the Atlanta metro
The Atlanta metro area accounts for more than half of Georgia's population. The City of Atlanta's web team maintains its own platform; Fulton, Gwinnett, Cobb, and DeKalb counties each run separate platforms; the metro authorities (MARTA, Atlanta Regional Commission, Atlanta-Region Transit Link Authority) maintain their own sites. The accessibility quality across the metro varies considerably. Each of these entities is responsible for its own Title II conformance regardless of any shared infrastructure or cross-entity coordination. The Atlanta nondiscrimination ordinance adds the city-level layer specifically for entities operating in Atlanta proper.
Why overlays are a poor fit for Georgia public entities
Accessibility overlays are heavily marketed to Georgia counties and cities. We have written about why accessibility overlays do not actually make sites WCAG-compliant in detail. For Georgia specifically: the GTA procurement standard is a substantiation regime for state agencies, and an overlay subscription does not substantiate. Local entities face the same Title II substantiation expectation. The FTC's April 2025 settlement with accessiBe makes overlay compliance claims a documented liability.
How Site Brace audits a Georgia public-entity site
The standard page mix for a Georgia public-entity audit:
- Homepage
- Department landing pages (top 4-6, varies by entity type)
- Governing body page (City Council, County Commission, Board of Education, etc.)
- Most-trafficked service pages (permits, utility billing, property tax, open-records requests)
- Public meeting calendar
- Document library or board-agenda archive
- Spanish-language toggle pages (metro Atlanta and Dalton-area entities)
- ADA accessibility statement (if one exists)
- Privacy policy, contact
That mix covers up to 25 pages depending on the entity. The audit runs axe-core 4.10, captures element-level screenshots of every contrast failure, and packages findings into a written report with copy-paste fix code and 12 re-scans included over 12 months.
Pricing is $149 flat, one-time. To see what the report looks like, view a sample report we built for a fictional municipality.
Want to check your own site first? Run a free single-page check on your homepage or your most-trafficked service page - one URL, about a minute, no signup needed to see the result.
Start a Georgia public-entity audit, $149
Related:
- Florida Title II accessibility - the neighboring Southeast state with a comparable framework
- Texas Title II accessibility - the comparable large state without a damage-multiplier statute
- DOJ Title II web rule primer
- Free single-page WCAG check
- Why accessibility overlays do not make sites WCAG-compliant