2026-05-17 · 10 min read
Maryland Government Website Accessibility: What the DOJ Title II Rule Means for Your Agency
# Maryland Government Website Accessibility: What the DOJ Title II Rule Means for Your Agency
Maryland state and local governments are now operating under a federal compliance deadline. The Department of Justice's Title II Final Rule — published in March 2024 and codified at 28 CFR Part 35 — requires every covered state and local government entity to bring its websites and mobile apps into conformance with WCAG 2.1 Level AA. For jurisdictions serving populations of 50,000 or more, the deadline is April 26, 2027.
Maryland has no exemption. The Maryland Department of Information Technology is covered. MDOT is covered. The Maryland Transit Administration is covered. Montgomery County's government, its school district, and its transit system are each independently covered. So are Prince George's County, Baltimore County, Anne Arundel County, Howard County, and Frederick County.
This post covers who is covered under the Maryland compliance picture, the deadlines that apply to each major jurisdiction, what Maryland government sites most commonly get wrong, the enforcement environment specific to Maryland, and what a compliance program looks like with the April 2027 deadline approaching.
---
Who Is Covered
April 26, 2027 deadline (population ≥ 50,000):
Maryland state government — all executive agencies, the General Assembly web presence, the Maryland judiciary, the University System of Maryland, and Maryland's state transportation agencies — is covered at the state level regardless of population tier.
Major Maryland counties above the 50,000 threshold include:
- Montgomery County (~1,062,000) — Maryland's most populous county, bordering DC
- Prince George's County (~967,000) — second most populous, also bordering DC
- Baltimore County (~854,000) — surrounding Baltimore City but an independent county
- Anne Arundel County (~590,000)
- Howard County (~340,000)
- Frederick County (~280,000)
- Baltimore City (~585,000) — independent city under Maryland law, covered separately
- Carroll County (~170,000)
- Harford County (~260,000)
- Charles County (~175,000)
- St. Mary's County (~115,000)
- Washington County (~155,000)
- Wicomico County (~105,000)
Transit authorities independently covered regardless of population tier include the Maryland Transit Administration (MTA), Ride On (Montgomery County), TheBus (Prince George's County), the Ride (Howard County), Corridor Bus (Carroll County), and Washington County Commuter Bus.
School districts — each a separate public entity — are independently covered. Maryland's 24 local school systems include some of the largest in the United States: Montgomery County Public Schools (~165,000 students), Prince George's County Public Schools (~135,000 students), and Baltimore City Public Schools (~77,000 students) are all independently subject to the April 2027 deadline.
April 26, 2028 deadline (population < 50,000):
Maryland's smaller incorporated municipalities, towns, and special taxing districts with populations under 50,000 have an additional year. However, many operate web properties that route through county infrastructure — the coverage analysis for smaller Maryland jurisdictions depends on whether the entity is served by county web systems or maintains independent digital infrastructure.
---
What Is Covered
Covered entities must make the following accessible at WCAG 2.1 Level AA:
- Main websites, subdomains, and all government web applications
- Mobile applications (iOS and Android) that deliver government programs or services
- PDFs and other documents posted on government websites
- Third-party portals procured to deliver government services — the government entity remains responsible even when an outside vendor operates the interface
- Social media accounts and web presences maintained by the agency
Limited exceptions under the rule: Archived web content not actively used, preexisting documents that have not been updated since the effective date, and third-party content over which the entity has no editorial control (such as a public comment submitted by a resident). These exceptions are narrow and do not apply to content the agency actively maintains, links to as part of a service, or controls through vendor contract.
---
Maryland's Digital Compliance Picture
Maryland's proximity to Washington DC creates a compliance environment that differs from most other states. Several factors elevate enforcement risk across Maryland covered entities.
Federal Contractor Workforce
Montgomery County, Prince George's County, and Anne Arundel County host large concentrations of federal government employees and federal contractors. Section 508 of the Rehabilitation Act has governed federal information technology accessibility for decades. The federal workforce in these counties has direct, ongoing experience with accessible digital government tools — and will notice when county portals, school district platforms, and transit applications fall short.
National Disability Rights Organizations in the DC Region
The National Federation of the Blind, headquartered in Baltimore, is one of the most active disability rights organizations in the United States and has historically been involved in web accessibility litigation and advocacy. The National Disability Rights Network and the American Council of the Blind maintain significant operations in the DC region. Disability Rights Maryland, the federally designated Protection and Advocacy organization, has legal standing to file administrative complaints and federal lawsuits on behalf of Maryland residents with disabilities.
This combination — a sophisticated disability advocacy ecosystem with legal standing — means that non-compliant Maryland government websites are more likely to generate formal complaints than comparable sites in other regions.
Maryland DoIT and Statewide Policy
Maryland's Department of Information Technology (DoIT) oversees statewide technology policy and the Maryland.gov portal. The rule's scope extends to every executive branch agency that delivers services through the state portal infrastructure. DoIT's compliance posture has downstream implications for agencies that rely on shared state infrastructure. Agencies that have not received clear direction from DoIT about the Title II compliance obligation should not wait — the federal rule applies directly to each covered entity regardless of whether the state has issued implementing guidance.
MDOT and MTA
The Maryland Department of Transportation (MDOT) and its subsidiary the Maryland Transit Administration (MTA) operate digital infrastructure that spans the full geographic footprint of the state. MTA's bus, Metro SubwayLink, Light RailLink, MARC Train, and Mobility paratransit services each have digital touchpoints: schedules, trip planning tools, real-time arrival displays, fare payment systems, and mobile applications. Each is subject to WCAG 2.1 AA.
Transit digital content is disproportionately used by people with disabilities — people with visual impairments use screen readers to access schedules; people with mobility disabilities rely on paratransit booking systems; people with cognitive disabilities need clearly structured route information. Inaccessible transit digital tools create direct barriers to transportation access.
Maryland Courts
The Maryland Judiciary operates a significant public-facing web presence: case search, e-filing, fee payment, court forms, and self-help resources used by unrepresented litigants. Court digital content is among the highest-stakes government web infrastructure — inaccessibility can directly limit access to justice. The Maryland courts are a covered entity under the rule.
---
Common Failure Patterns in Maryland Government Websites
Scanned PDF documents. County council meeting minutes, planning commission documents, zoning ordinance packages, budget books, and audit reports are routinely posted as image-based scanned PDFs across Maryland county governments. A scanned image of a document is completely inaccessible to screen reader users. WCAG 2.1 requires information in documents to be presented in a way that assistive technology can read. Maryland's active board meeting culture — and the volume of supplemental documents posted to support public participation — makes PDF accessibility one of the highest-volume remediation tasks.
Third-party payment portals. Property tax payments, utility bill payments, permit fees, court costs, and school fee payments frequently route through third-party payment processors. The DOJ rule holds the government entity responsible for the accessibility of third-party content used to deliver government programs. County government contracts with payment vendors that predate the April 2024 final rule should be reviewed; new procurements must include WCAG 2.1 AA conformance requirements.
School district parent and student portals. Maryland's large school systems — MCPS, PGCPS, Baltimore City Public Schools, Baltimore County Public Schools — operate parent communication platforms, student information systems, grade portals, enrollment tools, and school selection applications. These platforms handle communications parents cannot substitute for. Form labeling failures, keyboard navigation gaps, and screen reader incompatibility are the most common failure categories in school district web applications.
Transit digital tools. MTA's web presence, mobile applications, and real-time information displays carry WCAG 2.1 AA obligations. Color contrast failures in dynamic arrival information, missing text alternatives for map-based route displays, and screen reader incompatibility with trip planning tools are among the most common transit accessibility failures. Ride On, TheBus, and the county transit systems face the same obligations.
GIS and mapping applications. Maryland county governments are heavy users of GIS for property records, zoning lookups, flood plain mapping, election precinct maps, and development tracking. Interactive map canvases provide no accessible text alternative in most standard implementations. Property owners, attorneys, developers, and residents who rely on these tools cannot access the underlying information if the interface is not accessible.
Court self-help and e-filing portals. The Maryland Judiciary's public-facing tools — eCourts, case search, the Self-Help Center, and court form libraries — are used by unrepresented litigants who often cannot substitute an attorney. Accessibility failures in these tools disproportionately affect litigants with disabilities who are already navigating the system without legal representation.
---
The Enforcement Picture
DOJ Title II enforcement is complaint-driven. Any individual who encounters a barrier on a covered Maryland government website can file a complaint with the DOJ Civil Rights Division. The DOJ investigates, pursues voluntary compliance where possible, and can initiate litigation if an entity fails to remedy violations.
Maryland's enforcement environment has several characteristics that elevate risk:
The National Federation of the Blind, headquartered in Baltimore, has been involved in web accessibility cases and provides legal resources and advocacy support to members. Disability Rights Maryland, as the state's federally designated P&A organization, has independent legal standing to file complaints. The proximity of national advocacy organizations in the DC region — within the direct service area of many Maryland government entities — means complaint infrastructure is closer to Maryland residents than in most other states.
Maryland's history of ADA enforcement more broadly — including consent agreements involving Prince George's County on housing and civil rights matters — has given county leadership and legal staff direct experience with how federal civil rights enforcement proceeds. That institutional familiarity cuts both ways: it makes the compliance obligation legible, and it makes the enforcement consequence more credible.
An agency that has not begun a compliance assessment by late 2026 faces real risk of being in an enforcement proceeding with no defensible remediation timeline to offer investigators.
---
Compliance Timeline
Working backward from the April 26, 2027 deadline:
| Date | Milestone | |---|---| | Now (May 2026) | Commission accessibility audit; inventory all web properties, apps, PDFs, vendor portals | | July 2026 | Complete audit; severity-prioritized findings report | | August 2026 | Initiate vendor review; confirm third-party portals have WCAG 2.1 AA commitments | | September 2026 | Begin remediation; start PDF remediation workflow | | November 2026 | Developer remediation complete for critical and serious findings | | January 2027 | Verification re-testing | | March 2027 | Final conformance testing; draft accessibility statement | | April 1, 2027 | Publish DOJ-compliant accessibility statement | | April 26, 2027 | Deadline |
Agencies that begin this process now have enough runway to complete it without emergency procurement. Agencies that begin in January 2027 face a serious timeline problem.
---
Maryland County and City Guides
Detailed compliance guides for Maryland's major government entities:
- Montgomery County Maryland government website accessibility — Montgomery County (1.06M), MCPS (165K students), Montgomery College, Ride On Transit; Maryland's largest county with the highest Section 508-familiar population and elevated enforcement risk
- Prince George's County Maryland government website accessibility — Prince George's County (968K), PGCPS (135K students), Prince George's Community College, TheBus; consent decree history amplifies enforcement credibility
For context on how neighboring states are approaching the same federal compliance timeline, see Virginia government website accessibility and North Carolina government website accessibility.
---
The Parallax WCAG Audit
Morton Technology Consulting offers the Parallax WCAG audit at a fixed fee of $9,500.
The audit covers 200 representative pages across the agency's digital footprint. Testing combines automated scanning with axe-core against the full WCAG 2.1 Level AA ruleset and manual testing with NVDA on Windows and VoiceOver on macOS — the two most common screen readers used by government website visitors with disabilities. Keyboard-only navigation testing is conducted separately from screen reader testing to surface failures that automation cannot detect.
Automated scanners detect approximately 57% of WCAG failures on average. The remaining 43% — including keyboard traps, screen reader announcement failures, logical reading order problems, and complex form interaction failures — require manual expert testing. The Parallax audit covers both.
Deliverables include a full findings report with severity ratings (critical, serious, moderate, minor), a remediation roadmap prioritized by impact on service access, and a DOJ-compliant accessibility statement draft ready for legal review and publication.
At $9,500, the Parallax audit fits within most Maryland government agency written-quote thresholds without a full competitive bid process.
More information: morton-digital.com/products/parallax
Sample audit report: morton-digital.com/parallax-sample-audit
Contact: [email protected]
---
*Morton Technology Consulting LLC, Tallahassee, FL. Mid-Atlantic and Southeast government website WCAG 2.1 compliance audits for the April 2027 deadline. [email protected]*
Sources
- [1] U.S. Department of Justice, Civil Rights Division — ADA.gov — "State and local governments with a total population of 50,000 or more must comply with the rule by April 26, 2027. State and local governments with a total population of less than 50,000 must comply with the rule by April 26, 2028."
- [2] Federal Register — 28 CFR Part 35, Final Rule, April 24, 2024 — "The Department of Justice is amending its regulation implementing title II of the Americans with Disabilities Act (ADA) to provide more specific requirements to clarify the obligations of state and local governments to make their web content and mobile apps accessible to people with disabilities."
- [3] W3C Web Accessibility Initiative — Web Content Accessibility Guidelines (WCAG) 2.1 — "Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible."
- [4] U.S. Census Bureau — QuickFacts: Montgomery County, Maryland — "Population estimates for Montgomery County, Maryland"
- [5] U.S. Census Bureau — QuickFacts: Prince George's County, Maryland — "Population estimates for Prince George's County, Maryland"
- [6] U.S. Census Bureau — QuickFacts: Maryland Counties — "Population estimates for Maryland counties from the 2020 Census and subsequent estimates."
- [7] Maryland Transit Administration — "The Maryland Transit Administration (MTA) provides bus, Metro SubwayLink, Light RailLink, MARC Train, and Mobility paratransit services."
- [8] WebAIM — The WebAIM Million: An annual accessibility analysis of the top 1,000,000 home pages — "95.9% of home pages had detected WCAG 2 failures"
- [9] U.S. Department of Justice, Civil Rights Division — ADA.gov — "A public entity that uses a third party's web content or mobile app to offer services to the public must ensure that such content or app is accessible."
- [10] Disability Rights Maryland — "Disability Rights Maryland is Maryland's Protection and Advocacy organization — federally mandated to protect the rights of Marylanders with disabilities."
- [11] Maryland Department of Information Technology — "DoIT serves as the primary technology partner for Maryland state government."
- [12] Montgomery County Public Schools — Enrollment Statistics — "MCPS is among the largest school systems in the nation."
Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →