ADA Compliance in the Public Sector: A Step-by-Step Guide for 2025 Web Accessibility Readiness

Why Public-Sector Accessibility Matters in 2025

Websites and mobile applications have become essential channels for accessing government information and public services.

Residents use digital platforms to pay bills, apply for benefits, register for programs, review public records, access transportation information, submit forms, attend public meetings, and communicate with government agencies.

When those platforms are not accessible, people with disabilities may be prevented from receiving the same services and information available to other members of the public.

Web accessibility is therefore more than a technical requirement. It is an essential part of equitable public service.

For state and local governments, 2025 is an important readiness year. The Department of Justice issued a final rule in 2024 establishing specific technical accessibility requirements for websites and mobile applications under Title II of the Americans with Disabilities Act.

Public entities should use the remaining preparation period to evaluate digital properties, correct accessibility barriers, establish internal processes, and prepare for the applicable compliance deadline.

Understand the DOJ Title II Requirements

The Department of Justice’s 2024 final rule requires covered state and local government web content and mobile applications to conform to the Web Content Accessibility Guidelines 2.1, Level AA.

WCAG is organized around four foundational principles. Digital content should be:

• Perceivable
• Operable
• Understandable
• Robust

In practical terms, websites and applications should allow people with disabilities to locate information, understand content, navigate interfaces, complete transactions, and interact with public services using assistive technologies.

The requirements may affect:

• State and local government websites
• Public colleges and universities
• Public school systems
• Courts
• Public transportation agencies
• Libraries
• Public hospitals and clinics
• Parks and recreation departments
• Special-purpose districts
• Government mobile applications

The rule also applies when a public entity provides digital services through a contractor or other third party.

Know the Original Compliance Deadlines

As of 2025, the original DOJ compliance schedule provides different deadlines according to the population served by the public entity.

Public entities serving populations of 50,000 or more are scheduled to comply by April 24, 2026.

Public entities serving populations below 50,000 and special district governments are scheduled to comply by April 26, 2027.

These dates should guide accessibility planning, budgeting, procurement, remediation, and testing activities.

Organizations should not wait until the final months before the applicable deadline. Large websites may contain thousands of webpages, documents, forms, videos, applications, and third-party systems requiring review.

Step 1: Establish Accessibility Leadership

Accessibility responsibilities frequently cross several departments.

A public entity should designate an accessibility coordinator, project manager, or cross-functional working group with representation from areas such as:

• Communications
• Information technology
• Legal counsel
• Procurement
• Records management
• Human resources
• Program offices
• Website administration
• Mobile application management

Leadership should define responsibilities, approve priorities, allocate resources, and monitor progress toward compliance.

Without clear ownership, accessibility issues may remain unresolved because each department assumes another group is responsible.

Step 2: Inventory Digital Properties

An organization cannot remediate digital assets it has not identified.

Create an inventory of public-facing and internal digital properties, including:

• Main government websites
• Departmental websites
• Employee portals
• Public forms
• Online payment systems
• Scheduling applications
• Mobile applications
• Learning management systems
• Public documents
• Videos and audio recordings
• Third-party platforms
• Vendor-managed systems

For each item, record:

• Business owner
• Technical owner
• Platform
• Vendor
• Purpose
• Number of users
• Accessibility status
• Contract renewal date
• Remediation priority

The inventory should include content created or managed by contractors because public entities may remain responsible for services provided on their behalf.

Step 3: Conduct a Comprehensive Accessibility Audit

A complete accessibility assessment should combine automated testing, manual review, and assistive-technology evaluation.

Automated scanning tools can identify certain issues quickly, including:

• Missing alternative-text attributes
• Low color contrast
• Missing page titles
• Empty form labels
• Improper heading structures
• Certain HTML and ARIA errors

Automated tools cannot identify every barrier.

A tool may determine that an image has alternative text, for example, but it may not determine whether the description accurately communicates the purpose of the image.

Manual testing should evaluate:

• Keyboard navigation
• Visible keyboard focus
• Screen-reader output
• Form instructions
• Error messages
• Menus and interactive controls
• Modal windows
• Data tables
• Dynamic content
• Complete user workflows

Testing should include actual tasks that members of the public need to complete, such as submitting an application, paying a fee, registering for a service, or locating emergency information.

Step 4: Prioritize Critical Public Services

Large public-sector organizations may not be able to remediate every issue simultaneously.

A risk-based approach should prioritize digital services with the greatest impact on health, safety, legal rights, education, employment, transportation, finances, or access to government programs.

High-priority content may include:

• Emergency alerts
• Benefit applications
• Utility payment systems
• Court forms
• Public meeting notices
• Employment applications
• Election information
• Transportation schedules
• Student services
• Healthcare information
• Accommodation requests
• Complaint forms

Frequently used pages and services should also receive early attention.

Step 5: Create an Accessibility Roadmap

The results of the inventory and audit should be converted into a documented remediation roadmap.

For each issue, identify:

• The affected website or application
• The accessibility barrier
• The applicable WCAG criterion
• The impact on users
• The responsible department
• The required correction
• The target completion date
• The validation method
• The current status

The roadmap should divide remediation into manageable workstreams, such as:

• Website templates
• Navigation
• Online forms
• Mobile applications
• PDFs and documents
• Videos and captions
• Third-party platforms
• Procurement
• Staff training
• Accessibility policies

Intermediate milestones should be established well before the final compliance deadline.

Step 6: Correct Common Website Barriers

Website remediation should address both individual content issues and recurring problems within templates or shared components.

Common corrections include:

• Adding meaningful alternative text to informative images
• Marking decorative images appropriately
• Correcting heading structures
• Improving color contrast
• Making controls keyboard accessible
• Providing visible focus indicators
• Labeling form fields
• Writing clear error messages
• Providing captions for videos
• Correcting data tables
• Using semantic HTML
• Ensuring content works when enlarged
• Avoiding instructions based only on color

Correcting a shared template or reusable component may resolve the same accessibility problem across hundreds of pages.

Step 7: Review PDFs and Electronic Documents

Government websites often contain extensive collections of PDFs, forms, reports, presentations, spreadsheets, meeting packets, and scanned records.

Accessible document remediation may require:

• Correct reading order
• Proper headings
• Alternative text
• Accessible tables
• Form-field labels
• Document titles
• Language settings
• Bookmarks
• Searchable text
• Sufficient color contrast

Public entities should identify which documents are actively used, essential to public services, frequently downloaded, or legally required.

Creating accessible HTML versions of important information may sometimes provide a better user experience than relying exclusively on PDFs.

Step 8: Evaluate Mobile Applications

The DOJ rule applies to covered mobile applications as well as websites.

Mobile accessibility testing should examine:

• Screen-reader compatibility
• Touch-target size
• Text scaling
• Device orientation
• Form completion
• Error recovery
• Authentication
• Gesture alternatives
• Color contrast
• Status announcements

Testing should include both major mobile operating systems when applicable.

The organization should also evaluate mobile applications developed or operated by third-party vendors.

Step 9: Review Third-Party Platforms

Public entities often use outside providers for:

• Online payments
• Scheduling
• Permit applications
• Citizen portals
• Meeting platforms
• Employment applications
• Learning systems
• Recreation registration
• Public records requests

Using a third-party platform does not necessarily remove the public entity’s responsibility for accessibility.

Agencies should test vendor platforms and review contracts for accessibility obligations.

Contracts should address:

• Applicable accessibility standards
• Testing responsibilities
• Required documentation
• Remediation timelines
• Maintenance requirements
• Issue-reporting procedures
• Consequences for unresolved barriers

Vendor accessibility claims should be verified whenever possible.

Step 10: Strengthen Procurement Practices

Accessibility should be considered before technology is purchased rather than after a system has been deployed.

Solicitations and contracts should define:

• The required accessibility standard
• Acceptance-testing procedures
• Documentation requirements
• Remediation responsibilities
• Maintenance expectations
• Required conformance reports
• Rights to independently test the solution

Procurement personnel should be trained to review Accessibility Conformance Reports and Voluntary Product Accessibility Templates.

A vendor’s completed template should be treated as supporting information, not unquestioned proof that the product is accessible.

Step 11: Train Employees and Contractors

Accessibility problems are often introduced during routine content updates.

Training should be tailored to employee responsibilities.

Content authors should understand:

• Heading structures
• Descriptive link text
• Alternative text
• Accessible tables
• Document accessibility
• Video captions
• Plain language

Designers should understand:

• Color contrast
• Focus visibility
• Text resizing
• Responsive layouts
• Accessible interaction patterns

Developers and testers should understand:

• Semantic HTML
• Keyboard interaction
• ARIA
• Accessible forms
• Screen-reader testing
• Automated and manual testing

Training should also be provided to contractors who create or manage digital content on behalf of the organization.

Step 12: Publish an Accessibility Policy

An internal accessibility policy should establish the organization’s expectations and responsibilities.

The policy may address:

• Applicable standards
• Governance
• Procurement
• Website development
• Content publishing
• Document accessibility
• Testing
• Remediation
• Training
• Vendor oversight
• Monitoring
• User feedback

A public accessibility statement should explain the organization’s commitment and provide a clear method for reporting barriers or requesting assistance.

The reporting method should itself be accessible.

Step 13: Document Accessibility Activities

Public entities should maintain records demonstrating how accessibility is being managed.

Documentation may include:

• Digital asset inventories
• Audit reports
• Test results
• Remediation plans
• Completed corrections
• Training records
• Vendor communications
• Procurement evaluations
• Accessibility requests
• User complaints
• Policy approvals
• Retesting results

Documentation supports management oversight and helps demonstrate that accessibility is an ongoing organizational responsibility.

Step 14: Retest Remediated Content

A remediation task should not be considered complete until the correction has been tested.

Retesting should confirm that:

• The original barrier has been resolved
• The correction did not create another problem
• Keyboard navigation remains functional
• Screen-reader output is appropriate
• Mobile and desktop workflows remain usable
• Supporting documentation has been updated

Testing by people with disabilities can identify usability issues that may not appear in automated reports.

Step 15: Monitor Accessibility Continuously

Accessibility is not a one-time project.

New webpages, documents, videos, software updates, and third-party features can introduce new barriers after the initial remediation effort is complete.

An ongoing monitoring program may include:

• Scheduled automated scans
• Periodic manual audits
• Document reviews
• Content spot checks
• Vendor evaluations
• User feedback
• Regression testing
• Refresher training
• Annual policy reviews

Accessibility should be incorporated into the organization’s normal website, application, procurement, and content-management processes.

Do Not Depend on an Overlay Alone

Accessibility widgets and AI-assisted tools may provide useful interface adjustments, scanning, or monitoring capabilities.

However, one automated script should not replace accessible design, source-code remediation, manual evaluation, document remediation, assistive-technology testing, and human oversight.

A layered accessibility program provides stronger and more dependable results.

Use 2025 as a Readiness Year

For many public entities, 2025 represents the most important planning and remediation period before the original DOJ compliance deadlines.

Organizations should use this time to:

• Identify digital assets
• Establish ownership
• Audit critical systems
• Correct high-impact barriers
• Review third-party platforms
• Update procurement practices
• Train employees
• Document progress
• Establish continuous monitoring

Starting early allows public entities to spread costs across budget cycles, coordinate accessibility with planned modernization projects, and avoid rushed remediation near the deadline.

How SingTone Technologies Can Help

SingTone Technologies supports public-sector organizations with accessible website development, testing, remediation, documentation, and long-term maintenance.

Our accessibility services may include:

• Website and application inventories
• Automated and manual accessibility assessments
• WCAG 2.1 Level AA testing
• Section 508 support
• Keyboard and screen-reader testing
• Accessibility remediation
• Accessible website development
• Document accessibility coordination
• Vendor and platform reviews
• Remediation tracking
• Staff training support
• Continuous monitoring

We shall work with agency stakeholders to develop an accessibility roadmap aligned with operational priorities, technology environments, budgets, and applicable deadlines.

Prepare Accessible Public Services for the Future

ADA readiness involves more than passing an automated website scan.

A sustainable accessibility program requires leadership, clear ownership, accurate inventories, meaningful testing, code-level remediation, accessible procurement, employee training, user feedback, and continuous monitoring.

Public entities that act in 2025 can improve access to essential services, reduce long-term remediation costs, strengthen public trust, and prepare responsibly for the upcoming Title II compliance deadlines.

SingTone Technologies shall help government agencies create accessible digital services that are inclusive, maintainable, and ready to serve every member of the public.