New federal requirement

Digital Accessibility Requirements for Fire & Rescue Departments

In April 2024, the U.S. Department of Justice issued a final rule under Title II of the Americans with Disabilities Act (ADA) requiring all state and local government entities — including fire and rescue departments — to make their websites, mobile apps, and digital content conform to WCAG 2.1 Level AA accessibility standards.

Deadline: April 26, 2027 · Population served over 50,000 · WCAG 2.1 AA

Overview Deadlines WCAG 2.1 AA Requirements Action checklist Exceptions FAQ Resources Work with us

What changed

The Law Now Includes Your Website

The ADA has applied to Fire & Rescue departments since 1992 — covering facilities, programs, and services. What changed in 2024 is that the U.S. Department of Justice published a final rule making clear that websites, mobile applications, and digital content are public services too, and must be equally accessible.

If a resident uses the department website to find burn permit information, submit a public records request, view job openings, read evacuation guidance, or contact the department — that interaction is covered. The rule sets WCAG 2.1 Level AA as the technical compliance standard.

This is not an overlay issue — it’s a structural one

Accessibility overlay widgets (the kind that add a floating toolbar to a website) do not satisfy the Title II rule. The DOJ guidance is explicit that real conformance with WCAG 2.1 AA must be built into the site itself. Overlays have also been the subject of their own lawsuits.

Compliance Timeline

Deadlines by Jurisdiction Size

The DOJ rule sets different compliance dates based on the population served.

Large Governments

Populations greater than 50,000

April 26, 2027

Small Governments

Populations under 50,000

April 26, 2028

Special Districts

Special district governments

April 26, 2028

Having a later deadline than larger jurisdictions does not reduce the scope of the requirement — it provides time to plan and implement thoughtfully. Waiting until early 2027 to start is not a viable strategy.

The Technical Standard

What WCAG 2.1 Level AA Requires

WCAG — the Web Content Accessibility Guidelines — is published by the World Wide Web Consortium (W3C) and organized around four core principles. Level AA sits above the minimum (Level A) and is the real standard for government websites.

WCAG 2.1 AA is Built Around Four Core Principles

Known by the acronym POUR: Perceivable, Operable, Understandable, and Robust. These principles ensure digital content is accessible to people with a wide range of abilities.

P

Perceivable

Information must be presentable in ways users can perceive — including those who can’t see, hear, or distinguish color.

O

Operable

All functionality must work without a mouse. Keyboard-only navigation, no time traps, seizure-safe animations.

U

Understandable

Content and interface behavior must be predictable. Error messages must identify what went wrong and how to fix it.

R

Robust

Content must be compatible with assistive technologies — screen readers, braille displays, voice control software.

WCAG 2.1 AA may sound technical, but the goal is simple: make sure your website works for real people in real-world situations.

The Technical Standard

Specific Requirements for Fire Department Sites

These are the most common failure points when public safety websites are audited against WCAG 2.1 AA.

Image alt text

Every informational image — apparatus photos, station maps, event flyers — must have descriptive alt text. Decorative images must be marked so screen readers skip them.

Color contrast — 4.5:1 minimum

Normal text must achieve at least a 4.5:1 contrast ratio against its background. Large text (18pt or 14pt bold) requires 3:1. Red-on-white and gray-on-white combinations frequently fail.

Keyboard navigation throughout

Every menu, form, link, and interactive element must be usable without a mouse. This includes mobile-style hamburger menus and calendar widgets. A visible focus indicator is required.

Accessible forms

Burn permit applications, recruitment forms, inspection request forms, and any other public-facing form must have programmatically linked labels, clear error messages, and logical tab order.

Captioned video content

All pre-recorded video must include accurate synchronized captions. This includes public safety announcement videos, training recordings posted online, and meeting recordings. Auto-generated captions alone are usually insufficient.

Accessible PDFs and documents

PDFs posted for public download — including SOGs summaries, community risk reduction materials, annual reports, and public notices — must be tagged and readable by screen readers. Scanned image PDFs fail this test entirely.

Logical heading structure

Pages must use heading levels (H1, H2, H3) in a logical, nested order — not chosen for visual size. Screen reader users navigate by headings; a broken heading structure makes pages unusable.

Mobile app accessibility

If the department or county operates a mobile app — whether for emergency notifications, burn ban status, or community reporting — it must also conform to WCAG 2.1 AA.

Track Your Progress

Compliance Action Checklist

If your team wants to start improving accessibility on its own — make sure to check off tasks as they are completed. This checklist is not exhaustive, but covers the highest-impact steps for most fire department websites.

Audit & Planning

Run an automated audit (e.g. WAVE, Axe, or Lighthouse) on all public pages
Manually test site navigation with keyboard only (Tab, Shift+Tab, Enter, arrow keys)
Test with a screen reader: NVDA (Windows, free) or VoiceOver (Mac/iOS, built-in)
Create a prioritized issue list with WCAG criterion references for each finding

Content & Structure

Add descriptive alt text to all informational images; mark decorative images as presentational
Verify each page has one H1; confirm heading hierarchy is logical and nested correctly
Create a prioritized issue list with WCAG criterion references for each finding
Remediate or replace all inaccessible PDF documents (recreate as tagged PDFs or HTML)
Add accurate synchronized captions to all pre-recorded video content

Technical & Ongoing

Add a “Skip to main content” link as the first element in the page
Confirm all form fields have programmatically associated labels and clear error messaging
Publish an accessibility statement page with a feedback mechanism and contact
Establish a policy for reviewing new content for accessibility before publication
Schedule periodic re-audits (recommended: quarterly or when major site changes occur)

Narrow Carve-outs

When Exceptions May Apply

The rule includes limited exceptions — but they are narrow and carry documentation requirements. Assuming an exception applies without going through the required analysis creates its own legal exposure.

Undue burden & fundamental alteration

A department may argue that specific conformance requirements impose an undue financial or administrative burden, or would fundamentally alter the nature of the program. This determination must be made by the department head in writing, must consider all available resources (not just the IT budget), and the department must still provide an accessible alternative means of accessing the content or service.

Other limited exceptions

Archived content — web content archived for reference only, not actively maintained, created before the compliance date, and clearly labeled as archived may be exempt. Content that is updated even occasionally does not qualify.

Third-party content — content posted by third parties (e.g., a vendor’s embedded map) may not be required to conform, provided the department did not procure or control that content. However, the department should prioritize accessible vendor choices going forward.

Pre-existing conventional electronic documents — documents (PDFs, Word files, etc.) posted before the compliance deadline may be exempt unless the department still actively uses them to provide services or information.

Important

No exception relieves a department of the obligation to provide effective communication. If a document is exempt, an accessible alternative method of providing that information is still required.

Common Questions

Quick Answers

What are the consequences of not complying by April 26, 2027?

The DOJ can investigate complaints, conduct compliance reviews, and initiate litigation against non-compliant public entities. Civil penalties for violations under Title II can reach $115,231 for a first violation and $230,464 for subsequent violations. Individuals may also file private lawsuits. Beyond legal exposure, a non-compliant site represents a failure of public trust — particularly for a department whose mission is to protect all residents.

Does this apply to us even if we don’t have many residents with disabilities?

Yes. Title II applies to all public entities regardless of how many residents with disabilities are known to use their services. The DOJ rule does not include a population or usage threshold. Additionally, roughly 1 in 4 adults in the United States has some form of disability — and many more benefit from accessible design, including older residents, people with temporary injuries, and those on mobile devices.

We have a phone number on the site. Doesn’t that satisfy the “alternative access” requirement?

Not under the new rule. The DOJ has been clear that providing a phone number or an in-person alternative does not substitute for making the website itself accessible. The standard is equivalent access — the digital experience must be as effective for people with disabilities as it is for everyone else. A TTY number is a separate accommodation, not a substitute for an accessible website.

Can we put an accessibility widget on the site and call it done?

No. Overlay widgets — the floating toolbars that promise instant compliance — have been explicitly rejected as a compliance solution by accessibility experts, civil rights organizations, and increasingly by courts and regulators. The DOJ rule requires actual conformance with WCAG 2.1 AA, which must be built into the site structure itself. Overlays have also been the target of their own ADA lawsuits.

Our website is managed by a county-wide vendor. Who is responsible for compliance?

Each department remains legally responsible for the accessibility of its web content regardless of who manages the platform. If a third-party vendor manages the site, the department should ensure the contract includes WCAG 2.1 AA conformance requirements and that the vendor can demonstrate compliance. Procurement decisions made going forward should prioritize accessible platforms.

Official sources

Need Help Getting There? We Design and Develop Websites for Fire Departments.

Creative Reload works with Fire & Rescue departments to design and develop accessible websites for WCAG 2.1 AA compliance — before the April 2027 deadline. We understand the operational tempo, the public accountability, and the unique content needs of public safety agencies.

Fire Department Websites

Purpose-built websites designed for public safety — fast, mobile-first, and built accessible from the ground up so you never need a retrofit.

WCAG 2.1 AA Compliance Audit

A full audit of your existing site against WCAG 2.1 Level AA — every failure documented with its criterion reference, severity, and a recommended fix.

ADA Remediation

We fix what the audit finds — from broken heading structure and inaccessible PDFs to keyboard traps and color contrast — and verify the result.

Ongoing Support

Compliance isn’t a one-time event. We offer quarterly re-audits and review of new content so your site stays conformant as it grows and changes.

Ready to get Compliant?

Don’t wait for lawsuits and fines. Make your website accessible and ADA compliant to mitigate risks now.

Schedule a Free Consultation