Why Parks and Recreation Agencies Should Stop Relying on Accessibility Overlays

Every January, recreation agencies open summer camp registration and brace for the rush. Parents refresh the page at 8 a.m., forms load, payments process, spots disappear in minutes.

Now imagine a parent who uses a screen reader trying to complete that same registration. The overlay toolbar loads first and takes over focus. The program calendar announces nothing. The submit button sits outside the tab order. By the time they work around it, the camp is full.

That parent is not an edge case for a parks and recreation department. They are the mission.

Most agencies that buy an accessibility overlay are trying to do the right thing with a limited budget. The pitch is compelling: one line of code, instant compliance, lawsuit protection. The problem is that the pitch is not true, and the agencies that serve people with disabilities most directly are the ones who pay for it.

What Is an Accessibility Overlay?

An accessibility overlay is a third-party JavaScript widget that loads on top of your website and attempts to correct accessibility problems in the visitor’s browser. Vendors include AccessiBe, UserWay, and AudioEye. The overlay cannot change your source code, your CMS templates, or your registration vendor’s portal. It can only attempt fixes after the page loads, which means the underlying barriers remain for anyone using assistive technology.

Do Accessibility Overlays Make a Parks and Recreation Website ADA Compliant?

No. An overlay does not make a recreation website ADA compliant, and no vendor can make that claim honestly. The Department of Justice has been explicit that compliance depends on the underlying code and content, not on a widget. Automated tools and overlays together catch a fraction of WCAG failures, and they cannot fix the ones that matter most in a transaction: keyboard traps, missing form labels, unannounced error messages, and focus order.

Here is the gap between the sales deck and the audit report:

The legal record backs this up. In 2025, the Federal Trade Commission fined AccessiBe $1 million over false and deceptive compliance claims. The Overlay Fact Sheet, signed by hundreds of accessibility professionals and disability organizations including the American Foundation for the Blind and the National Federation of the Blind, states plainly that no overlay can make a website fully accessible. When the organizations representing the people these tools claim to help have formally rejected them, that is not a marketing disagreement. It is a consensus.

Why Parks and Recreation Sites Are Especially Vulnerable

Recreation agencies have a digital footprint that is harder to remediate than most, and that is exactly why an overlay feels like a shortcut. Here is where the shortcut fails.

Registration systems you do not control

Most agencies run registration through third-party platforms such as RecTrac, CivicRec, ActiveNet, or CLASS. Those portals live on the vendor’s domain. An overlay installed on your main site does nothing for them. The transaction where a family actually signs up for a program, and where most accessibility barriers concentrate, sits entirely outside the widget’s reach.

Program guides, schedules, and forms published as PDFs

Recreation departments are document factories. Seasonal program guides, pool schedules, facility rental packets, waiver forms, and medical release forms are usually published as PDFs. Overlays do not read, tag, or restructure documents. A screen reader hitting an untagged program guide hears nothing useful, and the visitor has no path forward.

Adaptive and special recreation program pages

Here the stakes are higher than anywhere else in local government. Adaptive programs exist to serve people with disabilities, and their registration pages are often the least accessible part of the site because they inherit the same broken templates as everything else. A barrier on a camp page is a barrier to the program’s own purpose.

An audience that skews older and disabled

Recreation centers serve large numbers of older adults, veterans, and people with mobility, vision, and cognitive disabilities. Accessibility problems here are not hypothetical usability complaints. They directly reduce participation among the residents these agencies were created to serve.

Multi-step forms for rentals, waivers, and permits

Facility rentals, shelter reservations, and program scholarships involve multi-step forms with date pickers, file uploads, and payment screens. This is precisely where overlay scripts break tab order, drop focus, and trap keyboard users in loops. A form that works with a mouse can be impassable without one.

What the Law Requires of Recreation Agencies

Public parks and recreation departments are public entities under ADA Title II. The DOJ’s 2024 web rule requires WCAG 2.1 Level AA conformance for web content and mobile apps, with compliance dates of April 26, 2027 for entities serving populations of 50,000 or more and April 26, 2028 for smaller entities. Buying an overlay does not move that date.

Special recreation associations need to check how they are structured. Many are formed through intergovernmental agreements among park districts, which makes them public entities under Title II. Others operate as standalone nonprofits, which places them under ADA Title III, where there is no fixed deadline but steady litigation. In 2025, plaintiffs filed 3,117 federal website accessibility lawsuits, a 27% increase over 2024, and 46% of federal cases targeted organizations that had already been sued once.

State law can add requirements on top of the federal floor. Colorado’s HB21-1110 is the clearest current example, and several other states are moving in the same direction. Our state-by-state guide maps what applies where.

What an Overlay Actually Does to a Registration Transaction

Walk through one real transaction with the overlay running. A parent opens your camp page. The overlay injects a toolbar and moves focus to it. Their screen reader now announces widget controls instead of your program content. The parent tabs toward “Register,” but the widget has inserted elements into the tab sequence, and the link they need comes after nine unrelated controls.

They reach the registration portal, which the overlay cannot touch. The portal’s form fields have visual labels but no programmatic labels, so the screen reader announces “edit text” six times. The date picker requires a mouse. The error message after submission is red text with no announcement, so the parent does not know their child’s date of birth was rejected.

That is not a hypothetical failure mode. Independent testing by the WebAIM team and others has documented overlay toolbars introducing their own barriers, including focus problems, duplicate controls, and conflicts with screen reader settings. The widget adds a second accessibility problem while leaving the first one in place.

What Works Instead: Fix the Source

Source-code remediation produces a durable, documented fix. That means auditing real user journeys, correcting the actual HTML, CSS, and content, remediating your documents, addressing vendor portals with your registration provider, and monitoring continuously so each seasonal launch does not reintroduce barriers.

The practical sequence for a recreation agency:

1. Audit the journeys that matter. Registration, facility rental, program search, and contact. Not every page, the ones where people transact.
2. Fix the agency site at the source. Semantic structure, keyboard operability, form labels, focus management, contrast, and announcements for errors.
3. Engage your registration vendor. Ask for their VPAT or accessibility conformance report, document the response, and push for a remediation timeline. You cannot fix their platform, but you can hold them accountable in writing.
4. Remediate the documents. Tag program guides and forms properly, or publish them as accessible HTML instead.
5. Monitor before every launch. New programs, new pages, and new forms create new barriers. Catch them before registration opens, not after a complaint.

If the budget is the obstacle, there are funding paths. Federal programs, Digital Equity Act funds, and foundation grants can all support this work, and the total is usually smaller than three years of overlay subscriptions plus one legal response.

What Building It Right Looks Like: A Special Recreation Case Study

South Suburban Special Recreation Association serves people with disabilities across several park districts, which means their website is not a brochure. It is the front door to programs their participants depend on.

In early 2026, SSSRA launched a new site built to WCAG 2.1 AA. Accessibility was handled in the build: semantic structure, keyboard-operable navigation, proper heading hierarchy, and content patterns their staff can maintain without calling a developer for every update. No overlay was installed, because there was nothing to patch over.

That is the practical difference. An overlay is a promise that someone else will handle it, and the promise expires the moment a visitor tries to register. A site built to standard keeps working after launch, through every new program and every seasonal update, because the accessibility lives in the code and in the content process rather than in a script.