Morton Digital

2026-05-17 · 10 min read

Allegheny County Pennsylvania Government Website Accessibility: Pittsburgh, PRT, and the April 2027 DOJ Title II Deadline

Abstract dark editorial illustration: an Allegheny County Pennsylvania compliance network rendered in fine copper line work on dark slate, with WCAG accessibility markers at Pittsburgh city, PRT transit, University of Pittsburgh, county government, and airport authority nodes. No text.

# Allegheny County Pennsylvania Government Website Accessibility: Pittsburgh, PRT, and the DOJ Title II Deadline

Allegheny County, Pennsylvania has approximately 1.24 million residents. The City of Pittsburgh — the Steel City — sits at its center with a population of approximately 303,000. Together they form one of the largest government compliance footprints in the mid-Atlantic region under the DOJ Title II Final Rule. Both face the April 26, 2027 deadline for WCAG 2.1 Level AA conformance. [1]

The Rust Belt context matters here. Many Allegheny County and Pittsburgh government digital systems were built over decades — sometimes on legacy infrastructure that predates modern web standards by a generation. County property records, court document portals, permitting systems, and transit information platforms in this region were frequently developed without accessibility as a design principle. That history creates a real remediation backlog.

This post covers who is covered in the Allegheny County compliance picture, the correct deadlines for each covered entity, what WCAG 2.1 Level AA requires, the most common failure categories for Pittsburgh-area government sites, and what a compliance program looks like with the April 2027 deadline approaching.

---

Who Is Covered and Which Deadline Applies

April 26, 2027 (population ≥ 50,000)

Allegheny County government. The county (~1.24 million residents) is independently covered. That means the Allegheny County government website, the county's online permitting and licensing portals, county court web systems, the Allegheny County Elections Division voter registration and results portals, the county property assessment and tax portal, and all county mobile applications must conform to WCAG 2.1 Level AA by April 26, 2027. [3]

City of Pittsburgh. The City of Pittsburgh (~303,000 residents) is a separate legal entity from Allegheny County. The City of Pittsburgh government website, Pittsburgh's online permit and code enforcement portals, Pittsburgh Water and Sewer Authority digital services, Pittsburgh Fire Bureau and Police Bureau web content, city parks and recreation registration systems, and Pittsburgh public-facing mobile applications are all in scope for April 26, 2027. [4]

Pittsburgh Regional Transit (PRT). The Port Authority of Allegheny County — Pittsburgh's public transit authority, now branded Pittsburgh Regional Transit (PRT) — is an independently covered public entity. Its digital compliance obligations include the PRT website, trip planner, real-time bus and light rail tracking interfaces, rider-facing mobile applications, schedule PDFs, fare payment digital systems, and any paratransit booking interfaces. Transit authorities are separately covered by the rule regardless of whether their population would independently trigger the threshold — as a regional transit authority serving well over 50,000 riders, PRT faces the April 26, 2027 deadline. [8]

University of Pittsburgh. The University of Pittsburgh is a state-related institution receiving Commonwealth of Pennsylvania appropriations and operating under Commonwealth oversight. State-related universities are covered public entities under Title II. With enrollment well above 50,000 students and staff, the University of Pittsburgh — including all of its campus websites, student services portals, public-facing research and event pages, and mobile applications — faces the April 26, 2027 deadline. [7]

Allegheny County Library Association / Carnegie Library of Pittsburgh. The Carnegie Library of Pittsburgh operates as the public library system for Pittsburgh and much of Allegheny County. As a publicly funded entity providing government-adjacent services, its website, online catalog, digital resource portals, and public digital services are in scope.

Allegheny County Airport Authority. The Allegheny County Airport Authority, which operates Pittsburgh International Airport and Allegheny County Airport, is a public authority and independently covered entity. Traveler-facing digital services, flight information, parking reservation systems, and mobile applications are in scope.

April 26, 2028 (population < 50,000)

Pittsburgh Public Schools. Pittsburgh Public Schools serves approximately 23,000 students — well below the 50,000-person threshold. Pittsburgh Public Schools therefore has until April 26, 2028 to achieve WCAG 2.1 Level AA conformance. The technical standard is identical; the deadline is one year later. This applies to the school district website, parent and student portals, online enrollment systems, and documents published through district web properties.

Community College of Allegheny County (CCAC). CCAC serves approximately 17,000 students — also below the 50,000 threshold — placing it in the April 2028 compliance tier. CCAC's website, student portal, registration systems, and published course materials must reach WCAG 2.1 Level AA by April 26, 2028.

Smaller Allegheny County municipalities. Allegheny County contains 130 municipalities — boroughs, townships, and small cities. Most have populations well under 50,000. These entities have until April 26, 2028. However, the technical requirement is the same: WCAG 2.1 Level AA. Small municipalities that use county-provided web infrastructure need to assess whether their content is served through a covered county system or an independent property.

Not Covered by Title II

Carnegie Mellon University. Carnegie Mellon University is a private research university. It is not a state or local government entity and is not covered by the DOJ Title II rule requiring WCAG 2.1 Level AA conformance. Carnegie Mellon has its own institutional accessibility policies, but those are not driven by Title II. [12]

---

What Is Covered

The rule covers web content and mobile apps that a public entity makes available to the public or uses to offer services, programs, or activities. [11] For Allegheny County and Pittsburgh government entities, that includes:

Third-party portals — if Allegheny County or the City of Pittsburgh contracted a vendor to build a permitting system, that system must conform to WCAG 2.1 AA. The government entity holds the compliance obligation. Vendor accessibility statements do not transfer liability. New and renewing technology contracts should include WCAG 2.1 AA conformance as a required deliverable.

---

What WCAG 2.1 Level AA Requires

WCAG 2.1 Level AA has 50 success criteria across four principles. [9]

Perceivable — content must be available to all senses. Alt text for informational images. Captions for prerecorded video. Color contrast at 4.5:1 for normal text and 3:1 for large text and UI components. Content that reflows to a single column at 320px without horizontal scroll.

Operable — all functionality must work without a mouse. Keyboard navigation must reach every interactive element. No focus traps. Skip links to bypass repeated navigation. Visible focus indicators at all times. No time limits that block task completion without user control.

Understandable — page language declared in HTML. Forms with visible labels, clear error messages in text, correction suggestions. Navigation consistent across pages. Instructions that do not rely on color or position alone.

Robust — valid HTML with correct ARIA roles and attributes so assistive technology can accurately parse the interface.

The WebAIM Million 2024 report found that 95.9% of home pages had detectable WCAG 2 failures. [10] The five most common: low contrast text (81%), missing alt text (54.5%), missing form labels (48.6%), empty links (44.6%), and missing document language (17.1%). Pittsburgh-area government sites follow the same national pattern.

---

The Most Common Failure Categories for Allegheny County and Pittsburgh Government Sites

1. Legacy portal inaccessibility. The Rust Belt's government digital infrastructure often reflects decades of accumulated technical decisions. Permit portals, property search tools, and benefits access systems in the Pittsburgh metro were frequently built on older frameworks — ASP.NET WebForms, early-generation CMS platforms, custom database front-ends — that were never designed with WCAG in mind. These systems commonly fail multiple WCAG criteria simultaneously: missing form labels (1.3.1), no visible focus indicators (2.4.7), broken keyboard navigation (2.1.1), inaccessible error messages (3.3.1 and 3.3.3), and custom widgets without proper ARIA markup (4.1.2). Remediating these systems requires both code-level fixes and, in some cases, platform migration.

2. PDF and document accessibility. Allegheny County government, Pittsburgh City Council, the Allegheny County Courts, and Pittsburgh Public Schools each generate thousands of PDFs annually — ordinances, meeting minutes, budget documents, court forms, transit schedules, school board materials. Many of these documents exist as scanned image files or as digitally created PDFs without accessible tag structure, reading order, or alt text for embedded charts. Government PDFs are explicitly covered by the rule when they provide access to services, programs, or activities.

3. GIS and property assessment tools. Allegheny County's online property assessment and real estate portal (a critical public service for tax assessment, appeals, and property research) is a GIS-based interface. These interactive mapping tools — common across Pennsylvania county governments — frequently fail keyboard accessibility and assistive technology parsing. Screen reader users and keyboard-only users cannot navigate map-based interfaces without explicit ARIA patterns and keyboard interaction support. WCAG 2.4.1 (bypass blocks), 2.1.1 (keyboard), and 4.1.2 (name, role, value) are the primary applicable criteria.

4. Transit digital services. Pittsburgh Regional Transit's digital footprint — website, trip planner, real-time tracking, mobile apps, schedule PDFs — must all conform to WCAG 2.1 AA. Real-time transit applications are particularly failure-prone: they rely on dynamic content loaded via JavaScript, third-party map widgets, and timed refresh cycles that can create keyboard traps, disrupt screen reader announcements, or lose focus position. These failures are structurally difficult for automated scanners to detect and require manual testing with NVDA, JAWS, and VoiceOver.

5. Video without compliant captions. Allegheny County Council meetings, Pittsburgh City Council sessions, Pittsburgh Board of Public Education meetings, and PRT public hearings are routinely recorded and published to government websites and YouTube channels. WCAG 1.2.2 requires captions for all prerecorded video with audio content. Auto-generated captions from YouTube or Zoom do not satisfy the standard — they require review and correction before they meet WCAG 1.2.2 conformance.

---

Compliance Timeline for Allegheny County and Pittsburgh Entities

Allegheny County and the City of Pittsburgh have until April 26, 2027 — roughly 11 months from now. A realistic compliance program:

Pittsburgh Public Schools (April 2028) and CCAC (April 2028) have an additional year — but beginning now still makes sense to avoid a compressed timeline.

---

Enforcement Context

The DOJ enforces Title II through complaint investigation and, where voluntary compliance fails, formal proceedings that can result in consent decrees, required remediation plans, and court monitoring. DOJ complaint filings by disability advocacy organizations — rather than individual residents — account for a significant share of formal government enforcement actions. Pennsylvania has active disability rights organizations with established federal complaint practices.

Allegheny County's size and political visibility, combined with Pittsburgh's profile as a major metro, place both entities in the higher-scrutiny tier of DOJ enforcement attention. Proactive, documented compliance programs — where the entity can show it conducted an audit, produced a remediation plan, and is executing against it — are treated materially differently in DOJ investigations than entities with no documented compliance effort.

---

Regional Context: Pennsylvania and Neighboring States

The DOJ Title II rule applies uniformly across state lines. Ohio's Cuyahoga County and Columbus (Franklin County), comparable in scale to the Pittsburgh metro, face the same April 26, 2027 deadline. Maryland's counties bordering Allegheny County are also in scope.

For context across the region:

Sources

  1. [1] Federal Register — Interim Final Rule extending Title II compliance dates (April 20, 2026) — "The compliance date for State and local government entities with a total population of 50,000 or more is extended from April 24, 2026, to April 26, 2027"
  2. [2] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "State and local governments must make sure that their web content and mobile apps meet WCAG 2.1, Level AA"
  3. [3] U.S. Census Bureau — QuickFacts Allegheny County, Pennsylvania — "Allegheny County, Pennsylvania — Population estimates, July 1, 2023: 1,236,537"
  4. [4] U.S. Census Bureau — QuickFacts Pittsburgh city, Pennsylvania — "Pittsburgh city, Pennsylvania — Population estimates, July 1, 2023: 303,064"
  5. [5] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "State and local governments with a total population of less than 50,000 must comply with this rule by April 26, 2028."
  6. [6] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "State and local governments with a total population of less than 50,000 must comply with this rule by April 26, 2028."
  7. [7] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "The rule covers public entities, which includes any State or local government and any department, agency, or other instrumentality of a State or local government."
  8. [8] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "Transit authorities are state and local government entities covered by Title II of the ADA and must comply with the web accessibility rule."
  9. [9] W3C Web Accessibility Initiative — WCAG 2.1 Specification — "Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible."
  10. [10] WebAIM — The WebAIM Million: An Annual Accessibility Analysis of the Top 1,000,000 Home Pages (2024) — "In 2024, 95.9% of home pages had detectable WCAG 2 failures. The most common failures were low contrast text (81.0%), missing alternative text (54.5%), missing form labels (48.6%), empty links (44.6%), and missing document language (17.1%)."
  11. [11] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "The rule covers web content and mobile apps that public entities make available to the public or use to offer their services, programs, or activities."
  12. [12] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "The rule applies to public entities — State and local governments and any department, agency, or other instrumentality of a State or local government."

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →