Morton Digital

2026-05-17 · 10 min read

Philadelphia County Pennsylvania Government Website Accessibility: City of Philadelphia, SEPTA, and the DOJ Title II Deadline

Abstract dark editorial illustration: a Philadelphia consolidated city-county compliance network rendered in fine copper line work on dark slate, with WCAG accessibility markers at city government, SEPTA transit, and School District of Philadelphia nodes. No text.

# Philadelphia County Pennsylvania Government Website Accessibility: What the DOJ Title II Rule Means for the City, SEPTA, and the School District

Philadelphia is the sixth largest city in the United States and the second largest on the East Coast. It is also a consolidated city-county: the City of Philadelphia and Philadelphia County are governed by a single unified government serving approximately 1.57 million residents. That consolidation matters for compliance planning — there is no separate county board to worry about, but there are multiple large independent entities across transit, education, and higher education that each carry their own obligations under the DOJ Title II Final Rule. [1]

This post covers who is covered in the Philadelphia compliance picture, the correct deadlines for each entity, what WCAG 2.1 Level AA actually requires, the most common failure categories for Philadelphia-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)

City of Philadelphia (consolidated city-county). Philadelphia is a consolidated city-county — the City of Philadelphia IS Philadelphia County. There is a single government entity, not separate city and county boards. With approximately 1.57 million residents, the City of Philadelphia is far above the 50,000-person threshold and faces the April 26, 2027 deadline. [3]

The scope for the city government is extensive: the phila.gov portal and all departmental subsites, L&I (Licenses and Inspections) online permitting, the Water Department's billing and payment portal, the Philadelphia Parking Authority digital services, the Office of Homeless Services and benefits-access portals, voter registration and election results systems, the Philadelphia Free Library digital services, Philadelphia Parks & Recreation registration systems, and all city-distributed mobile applications. Every system the city uses to deliver a service, program, or activity to residents is in scope. [11]

SEPTA (Southeastern Pennsylvania Transportation Authority). SEPTA is not part of the City of Philadelphia government. It is an independent multi-county transit authority serving Philadelphia and four surrounding counties — Bucks, Chester, Delaware, and Montgomery. SEPTA operates regional rail, subway, trolley, and bus systems throughout the region and is independently covered under the DOJ Title II rule as a public entity. [4]

SEPTA's digital compliance obligations include its main website, trip planning tools, real-time transit tracking, mobile app, station information pages, accessible services booking systems, schedule PDFs, and paratransit booking interfaces. As a transit authority serving well over 50,000 riders, SEPTA faces the April 26, 2027 deadline. Transit authorities are covered by Title II regardless of how their population-size question is measured — their independent entity status alone triggers coverage. [4]

School District of Philadelphia. The School District of Philadelphia serves approximately 115,000 students — far above the 50,000-person threshold — and is independently covered under the DOJ Title II rule. It faces the April 26, 2027 compliance deadline. [5]

The district's digital footprint includes the main district website, school-level pages and information portals, the parent and student portal, online enrollment systems, meeting minutes and board documents (which are typically PDFs), meal applications, and special education service documentation. Philadelphia's student population is one of the most linguistically and economically diverse in the country — accessible digital services are not an edge case, they are the default.

April 26, 2028 (population < 50,000)

Temple University. Temple University 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 an enrollment of approximately 35,000 students — below the 50,000-person threshold — Temple University has until April 26, 2028 to achieve WCAG 2.1 Level AA conformance. The technical requirement is identical to the 2027 entities; only the deadline differs. [6]

Temple's compliance scope includes the main university website, TUportal student services, Canvas course pages accessible to the public, library digital services, public event and research pages, and mobile applications distributed for student or public use.

Community College of Philadelphia (CCP). The Community College of Philadelphia is a public institution and covered entity under Title II. With an enrollment of approximately 15,000 students — below the 50,000-person threshold — CCP has until April 26, 2028. CCP's website, student registration portal, course catalog, financial aid information, and published course materials must all reach WCAG 2.1 Level AA by that date. [7]

Not Covered by Title II

Drexel University. Drexel University is a private research university — not a state or local government entity. It is not covered by the DOJ Title II Final Rule requiring WCAG 2.1 Level AA conformance. [8]

Thomas Jefferson University. Thomas Jefferson University (formed through the merger of Philadelphia University and Thomas Jefferson University) is a private institution. It is not covered by the DOJ Title II rule. [8]

---

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 Philadelphia and SEPTA, that includes:

Third-party portals are in scope. If the City of Philadelphia or the School District contracted a vendor to build an enrollment system, benefits portal, or permitting platform, that system must conform to WCAG 2.1 AA. The government entity holds the compliance obligation. Vendor-provided accessibility statements do not transfer liability. Renewed and new technology contracts should require WCAG 2.1 AA conformance as a 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 all prerecorded video with audio. 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 scrolling. No information conveyed by color alone.

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

Understandable — page language declared in the HTML. Forms with visible labels, clear error messages in text (not just color), and correction suggestions when a format error occurs. Navigation patterns 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. Custom widgets use ARIA in ways that match their actual behavior.

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%). Philadelphia government sites follow this same national pattern.

---

The Most Common Failure Categories for Philadelphia Government Sites

1. Permitting and licensing portals. Philadelphia's L&I (Department of Licenses and Inspections) permitting platform is a high-traffic, high-stakes digital service. Online permit applications, contractor licensing, code violation notices, and zoning information are all accessed through web-based portals. These types of systems are among the most consistently inaccessible in government: complex multi-step forms frequently lack proper labels (WCAG 1.3.1), error messages fail to identify the specific error field (WCAG 3.3.1), custom dropdowns lack proper ARIA markup (WCAG 4.1.2), and keyboard focus management breaks between form steps. Remediating these portals typically requires both code-level fixes and developer engagement with the underlying platform.

2. SEPTA's transit digital ecosystem. SEPTA operates one of the largest and most complex transit systems on the East Coast, with regional rail, subway, trolley, bus, and paratransit services. The SEPTA website, trip planner, real-time tracking interfaces, and mobile app are all in scope. Real-time transit applications are among the most failure-prone government digital services: they load dynamic content via JavaScript, integrate third-party map widgets, and use timed refresh cycles that can create keyboard traps, disrupt screen reader announcements, and lose focus position. These failures are structurally difficult for automated scanners to detect and require manual testing with NVDA on Windows and VoiceOver on iOS.

3. School district parent and enrollment systems. The School District of Philadelphia's parent and student portal, online enrollment system, and special education documentation portals are front-line services for more than 100,000 families. Parent portals across the country are among the most commonly inaccessible government systems: they frequently have missing form labels, inaccessible error messages, broken keyboard navigation, and PDF documents that exist as scanned images without accessible tag structure. For a district as large and diverse as Philadelphia's, these failures create real barriers to service access.

4. PDF and document accessibility. The City of Philadelphia, City Council, the school district, SEPTA, and every covered entity generates large volumes of PDFs — ordinances, budget documents, board meeting minutes, transit schedules, permit applications, court forms, special education plans. Many of these exist as scanned image files or digitally created PDFs without accessible tag structure, reading order, or alt text for embedded charts. Government PDFs are explicitly in scope under the rule when they provide access to services, programs, or activities. [11]

5. Video captioning for public meetings. Philadelphia City Council meetings, school board sessions, SEPTA public hearings, and Philadelphia mayoral press events 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 to meet WCAG 1.2.2. Philadelphia's large Deaf community and significant non-native-English-speaking population makes captioning quality a front-line equity issue, not just a compliance checkbox.

6. GIS and interactive mapping tools. Philadelphia's planning department, water department, and property assessment tools rely heavily on GIS-based interactive maps. Philadelphia's property data viewer and zoning maps are key public services. GIS-based interfaces frequently fail keyboard accessibility and assistive technology parsing — screen reader users and keyboard-only users cannot navigate map-based interfaces without ARIA patterns and keyboard interaction support explicitly built in. WCAG 2.4.1 (bypass blocks), 2.1.1 (keyboard), and 4.1.2 (name, role, value) are the primary applicable criteria.

---

Compliance Timeline for Philadelphia Entities

The City of Philadelphia, SEPTA, and the School District of Philadelphia have until April 26, 2027 — roughly 11 months from now. A realistic compliance program:

Temple University (April 2028) and Community College of Philadelphia (April 2028) have an additional year. Beginning a compliance program now rather than in 2027 is still the right decision — it avoids timeline compression and allows for proper remediation of complex portals.

---

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 account for a significant share of formal government enforcement actions.

Philadelphia's size, political visibility, and profile as a major East Coast city place it in the higher-scrutiny tier of DOJ enforcement attention. Pennsylvania has active disability rights organizations with established federal complaint practices. A city government this large with this many services touching residents at high frequency — permitting, utility billing, transit, schools — carries above-average enforcement exposure.

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. 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 Philadelphia city, Pennsylvania — "Philadelphia city, Pennsylvania — Population estimates, July 1, 2023: 1,567,258"
  4. [4] 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."
  5. [5] 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."
  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 — "State and local governments with a total population of less than 50,000 must comply with this rule by April 26, 2028."
  8. [8] 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."
  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] Federal Register — DOJ Title II Final Rule (April 24, 2024) — "Each State and local government entity covered by title II of the ADA has an independent obligation to comply with the requirements of this rule."

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