For years, digital accessibility lived in an uncomfortable gray area for state and district IT leaders. Everyone knew it mattered. But the rules were vague, the standards fragmented, and accountability often fell to whoever, “owned the website.”

A new era is here.

With the Department of Justice’s Title II ADA ruling, accessibility now has clear requirements for state and local governments—including education systems. The question for CIOs is no longer whether to act, but how to collaborate across the district to respond in a way that is realistic, scalable, and defensible.’

A graphic highlighting how CIO's Must Lead The Way with A school and the US Capitol next to each other.

What Title II Actually Requires (Without the Panic)

Let’s cut through the noise.

Title II does not say:

  • “Fix every PDF you’ve ever published by tomorrow.”
  • “Buy a single tool and call yourself compliant.”
  • “Put this entirely on your web team.”

What it does say is far more consequential.

  1. Digital Accessibility Is No Longer Optional

When the ADA passed in 1990, the internet didn’t yet exist as a public platform. So, while Title II required equal access, it did not include technical or digital requirements. For years, the DOJ has been stating that websites and apps must be accessible; however, there was no technical standard. The Title II ruling provided a technical standard so that state and local governments have clear criteria for websites, mobile apps, and digital services using Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the standard. For the first time, DOJ has removed the guesswork around what compliance means—bringing clarity and accountability.

For public education, this puts K–12 districts, community colleges, and higher education institutions squarely in scope, with accessibility expectations extending across learning platforms, student services, and public‑facing systems.

“Accessibility is a necessary component in the fight against exclusion. The new accessibility rule isn’t about compliance. It’s about building a shared culture across every aspect of the school division that promotes meaningful belonging.” Christopher Bugaj, Assistive Technology Specialist, Loudon County Schools, Virginia.

  1. The Clock Is Real

Deadlines for meeting Title II requirements are set and based on the population served:

  • April 24, 2026, for entities serving 50,000+ people
  • April, 2027, for smaller entities (serving fewer than 50,000 people) and special districts

This is why leadership matters now. Even if you are behind in conducting an audit or training educators on how to develop accessible content and present in accessible ways, it is not too late. The time is now to review your procurement requirements for accessibility, require conformance reports from vendors and work with curriculum and instruction to provide professional development.

  1. Process Matters as Much as Remediation

Perhaps the most misunderstood aspect of Title II is : DOJ expects evidence of progress and a plan for continued improvement.

That means:

  • Documented processes for accessibility requests and complaints
  • A plan to prioritize high impact ‑impact services
  • A transition strategy for legacy content

In other words, intentional execution beats reactive scrambling.

Why This Can Land Squarely on the CIO’s Desk

No single department can solve this challenge alone, and the CIO is uniquely positioned to orchestrate the coordinated, enterprise-wide response it requires. This isn’t a web problem, nor is it solely a legal or communications issue. It is, fundamentally, an area of growth to support inclusive technology systems. Unified leadership, shared responsibility, and cross-functional alignment to ensure sustainable, organization‑wide solutions for accessibility will drive change and establish new practices.

Accessibility under Title II cuts across:

  • Enterprise platforms and architecture
  • Content and document workflows
  • Vendor procurement and contract language
  • Security, risk, and compliance reporting
  • Instructional and administrative systems.
  • Professional Learning
  • Content Creation

How the CITES Framework Brings Order to Title II

The reason many organizations struggle with accessibility isn’t lack of effort—it’s lack of structure. The Center on Inclusive Technology & Education Systems (CITES) framework provides that structure in a way that aligns naturally with Title II expectations.

Culture: Setting the Non-

Title II compliance fails fastest when accessibility is seen as “someone else’s job.”

CITES starts by establishing accessibility as a shared responsibility across IT, academics, communications, procurement, and leadership. That cultural signal—set by the CIO—determines whether accessibility is sustained or sidelined.

CIO takeaway: If accessibility isn’t part of how decisions get made, it won’t survive the next budget cut or staff turnover.

Quote:  

“Accessibility becomes sustainable when it is part of culture, not just policy. The CITES framework has provided our district with a systems-based approach that aligns naturally with Title II expectations and has helped us at Jenks Public Schools build shared ownership across Technology, Teaching, and Learning, Communications, and leadership. That structure is what turns good intentions into lasting impact for students and staff.”

Samantha Reid, District Educational Technology Coordinator Jenks Public Schools, Oklahoma

Infrastructure: Designing for Accessibility by Default

Accessibility cannot be bolted on at scale. When infrastructure choices align with standards event. CITES encourages organizations to evaluate:

  • Procurement practices
  • Content Management Systems (CMS) and document platforms
  • Identity and authentication flows
  • Third-party tools and integrations

CIO takeaway: Platform decisions made today will either compound risk—or quietly eliminate it.

Training: Reducing Single Points of Failure

One accessibility expert is not a strategy. CITES emphasizes role-based training so . This is essential for districts and states where turnover is constant and expertise is thin.

CIO takeaway: Training is risk mitigation, not overhead.

Execution: Progress You Can Defend

Title II does not demand perfection—it demands progress with purpose. Create the paper trail and operational discipline DOJ expects to see.

CITES supports:

  • Prioritized remediation based on usage and impact
  • Clear ownership and timelines
  • Coordinating, project management and reporting structures

CIO takeaway: A credible plan beats a last-minute scramble every time.

Sustainability: Making Accessibility Stick

The real risk isn’t failing once—it’s fixing everything and slipping back out of compliance. CITES treats accessibility as an ongoing operational standard, embedded into procurement, content lifecycle management, and vendor oversight.

CIO takeaway: Sustainability is what keeps you compliant after the headlines fade.

The Leadership Opportunity Hidden in Title II

Title II ADA compliance is fundamentally about access to public services. But for CIOs, it’s also a chance to:

  • Strengthen enterprise governance
  • Reduce long‑term legal and operational risk
  • Improve digital service quality for everyone

Frameworks like CITES give CIOs a way to respond calmly, credibly, and strategically—without burning out teams or blowing up budgets. You can find out more at cites.cast.org.

The mandate is clear. The deadlines are real. And the leadership moment is now.

Additional Resources

Authors:
Mia Laudato, CITES Co-Project Director
Christine Fox, Chief Growth and Innovations Officer; Co-Project Director, CITES

Published on: March 5, 2026

CoSN is vendor neutral and does not endorse products or services. Any mention of a specific solution is for contextual purposes.