ADA accessibility triage is the practice of prioritizing remediation work based on risk, focusing first on the accessibility barriers that most directly block access to government services.
Most public agencies and universities approaching ADA Title II accessibility for the first time face the same problem. The audit comes back with hundreds of issues. The remediation list is overwhelming. The budget is limited. The staff capacity is limited. And the question that nobody in the room wants to say out loud is: if we cannot fix everything right now, what do we fix first?
That is not a bad question. It is the right question. And answering it well is actually what separates agencies that make meaningful compliance progress from agencies that spend remediation resources on the wrong things and end up more exposed than when they started.
Prioritization is not a compromise on accessibility. It is a governance discipline. The goal is not to fix the most issues. The goal is to fix the issues that matter most — the ones that create the most direct barriers to access, carry the most enforcement exposure, and represent the structural failures that generate downstream problems at scale.
This guide identifies the five categories of accessibility issues that, if addressed before anything else, produce the most significant and most defensible reduction in ADA Title II risk. These are not the only things that need to be fixed. They are the things that need to be fixed first.
Why Triage Matters More Than Volume
Before getting into the five categories, it is worth understanding why prioritization produces better outcomes than a volume-based approach.
An agency that fixes 200 low-impact accessibility issues — missing alt text on decorative images, minor heading hierarchy inconsistencies on low-traffic pages, cosmetic color contrast adjustments on secondary navigation elements — has done real work. Those issues are real. Fixing them is not wrong.
But an agency that fixes 200 low-impact issues while leaving its permit application inaccessible to keyboard users, its payment portal unnavigable by screen reader, and its most-downloaded public documents unparseable by assistive technology has spent significant remediation resources without meaningfully reducing its enforcement exposure. The barriers that actually generate complaints — the ones residents encounter when trying to complete transactions with their government — are still there.
Automated accessibility scanners tend to produce high counts of low-severity issues because they are good at detecting things that can be measured programmatically: missing attributes, color values below threshold, heading levels out of sequence. They are less good at detecting the barriers that matter most in enforcement contexts — keyboard navigation failures in transactional workflows, screen reader incompatibility in form interfaces, inaccessible error handling in service applications — because those require human testing to evaluate.
An agency whose remediation strategy is "fix everything the scanner flags in order of what it surfaces first" is optimizing for automated scan score rather than for compliance defensibility. Those are different things. Triage is the practice of optimizing for defensibility — fixing the right things in the right order based on actual impact and actual risk.
Fix 1: Transactional Workflow Barriers
If you fix only one category of accessibility issues before anything else, fix the barriers in your transactional workflows.
Transactional workflows are the digital services residents and students must complete to access something from your organization. Permit applications. Business license renewals. Tax payment portals. Utility service requests. Hunting and fishing license purchases. Financial aid applications. Course registration systems. Public records request forms. Any workflow where a person must complete a sequence of steps to receive a service or fulfill an obligation.
These workflows receive disproportionate attention in ADA Title II enforcement proceedings for one straightforward reason: when they are inaccessible, they constitute a direct denial of access to a government service. Not an inconvenience. Not a friction point. A complete barrier between a resident and something they are entitled to access.
The most common transactional workflow failures and how to identify them:
Unlabeled form fields. Tab to each form field using only keyboard navigation. Listen to what a screen reader announces when focus lands on the field. If it announces the field type without a meaningful label — "edit text" instead of "First Name, required" — the field is unlabeled. Every form field in a transactional workflow needs a programmatically associated label that tells the user what information is being requested.
Keyboard traps in interactive components. Navigate through the entire workflow using only keyboard. Specifically test any date picker, dropdown selector, file upload component, or modal confirmation dialog. If focus enters a component and cannot be exited using keyboard commands — typically Escape or Tab — the workflow has a keyboard trap that blocks completion for users who cannot use a mouse.
Inaccessible error handling. Submit the form with intentional errors — leave required fields empty, enter incorrectly formatted data, skip required checkboxes. When the error state appears, check whether the error is announced to assistive technology, whether the error message identifies which field failed and why, and whether the correction guidance is specific enough to act on. Error messages that appear visually but are not announced, or that say "Error" without identifying the field or the required format, block transaction completion for screen reader users.
Session timeout without accessible warning. If the workflow includes a session timeout, verify that users receive an accessible warning before expiration and that the session can be extended using keyboard only. A session that expires without warning while a user is completing a form, or that cannot be extended without mouse interaction, represents a complete service barrier.
Fixing transactional workflow barriers requires manual testing — a keyboard and a screen reader. Automated scanners will not catch most of these failures. The fix often requires developer intervention to correct the underlying markup, ARIA implementation, or JavaScript behavior. But the impact of those fixes on actual service accessibility and enforcement defensibility is greater than any other category of work.
Fix 2: Global Template and Navigation Issues
The second highest-leverage category of accessibility fixes is global template and navigation issues — accessibility failures baked into components that are shared across every page on the site.
Template-level issues are the highest-return accessibility work that exists. A single fix to a global navigation component, a skip link implementation, or a focus management issue in the site header resolves that issue simultaneously on every page that inherits from the template. A fix that takes a developer two hours to implement correctly can eliminate a class of accessibility failures across hundreds or thousands of pages at once.
The template issues that carry the most impact:
Missing or broken skip navigation links. A skip navigation link is the first focusable element on every page — a link that allows keyboard users to bypass the global navigation and jump directly to the main content. Without it, a keyboard user must tab through every item in the navigation menu on every single page before reaching the content they came to access. For a navigation menu with 40 items, that means 40 tab presses every time the user loads a new page. This is not a minor inconvenience. It is an exhausting, prohibitive barrier that makes keyboard navigation of a multi-page website effectively unusable.
Implementing skip navigation takes a competent developer a few hours. The impact is felt on every page of the site from the moment of implementation.
Invisible focus indicators. When a keyboard user tabs through a page, there must be a clearly visible indicator showing which element currently has focus. Many agency websites suppress the default browser focus outline for aesthetic reasons — the outline was considered visually intrusive during the design phase and was removed or hidden with CSS. When no custom focus indicator was implemented as a replacement, the result is a site that is visually navigable but completely disorienting for keyboard users who have no visual feedback about where they are on the page.
Restoring visible focus indicators requires CSS changes to the global stylesheet — changes that affect every interactive element across the entire site. The implementation is relatively straightforward. The impact is immediate and site-wide.
Global navigation keyboard accessibility. The primary navigation menu needs to be fully keyboard operable. This means every top-level item is reachable via Tab, every dropdown submenu can be opened and navigated using keyboard commands, and focus management when dropdowns open and close follows expected behavior. Navigation failures that require mouse interaction to access submenu items affect every page on the site that includes the global navigation — which is typically every page.
Consistent heading hierarchy in the global page structure. Screen reader users navigate pages using heading structure — jumping between H1, H2, and H3 elements to understand page organization and jump to relevant sections. If the global page template uses heading levels inconsistently — particularly if the page title is not the H1 or if the template introduces heading elements that disrupt the logical hierarchy of page-level content — every page on the site inherits that structural failure.
Fix 3: High-Traffic Public Documents and PDFs
The third triage priority is your highest-impact public documents — the PDFs and downloadable files that residents and students access most frequently and that carry the most direct civic or academic significance.
Document remediation is not glamorous work. It is not the kind of accessibility fix that shows up in an automated scan score improvement. But inaccessible documents are consistently among the most cited failure points in ADA complaints against public agencies, and for good reason. When an agency publishes a legally required notice, a permit application, a public meeting agenda, or a regulation document as a scanned flat image PDF, every resident who relies on a screen reader receives zero information from that document. That is a complete denial of access to information the agency is obligated to make accessible.
The documents to fix first:
Active service forms and applications. Any PDF that residents or students must complete to access a service — permit applications, license applications, public records request forms, grant applications, scholarship forms. These documents are both high-traffic and high-stakes. An inaccessible permit application form creates a service barrier that is impossible to work around without calling the office.
Public notices and legally required communications. Emergency notices, public hearing announcements, regulatory changes, environmental impact notices. These documents carry legal obligations for public access and public participation. Inaccessible public notices are the document accessibility failure most likely to generate a specific complaint.
Meeting agendas and board documents. The agenda packets, staff reports, and public comment documents published for board and council meetings are among the highest-traffic documents most public agencies publish. They are directly connected to civic participation. A resident who cannot access a meeting agenda cannot meaningfully participate in a public meeting.
Regulation and policy documents. Hunting and fishing regulations, zoning codes, fee schedules, compliance guides. These documents contain information residents need to understand their legal obligations and rights.
What document remediation actually requires: scanned PDFs need OCR processing plus accessibility tagging. Exported PDFs from Word or InDesign need heading structure, reading order, alternative text for embedded images, table header associations, and form field labeling. The going-forward standard needs to be established so that newly published documents are accessible at the point of publication rather than requiring remediation after the fact.
Fix 4: Color Contrast Across Primary Text and Interactive Elements
The fourth triage priority is color contrast — specifically the contrast between text and background on primary content areas, navigation, buttons, and form elements.
Color contrast is the accessibility failure that affects the largest number of users across the widest range of disability types. Approximately 8 percent of men and 0.5 percent of women have some form of color vision deficiency. A much larger proportion of the population — including many people who do not identify as having a disability — experiences meaningful vision changes with age, device screen variation, or environmental lighting conditions. Text that does not meet contrast requirements creates a real readability barrier for this broad population, not just for users with diagnosed low vision.
WCAG 2.1 AA requires a contrast ratio of at least 4.5 to 1 for normal-sized text and 3 to 1 for large text against its background. These are not arbitrary thresholds — they represent the minimum contrast at which text remains readable for users with moderate visual impairments.
Why contrast gets triage priority over other perceived failures:
It is detectable at scale through automated tools, which means it can be identified and prioritized without extensive manual testing. It affects every page where the contrast failures exist — which in many sites means it is a near-universal issue that a template-level fix can address comprehensively. And it is one of the most commonly cited failure points in automated accessibility reports, meaning it is the first thing an enforcement reviewer scanning for issues is likely to notice.
The contrast fixes to prioritize:
Primary body text against page backgrounds. This is the most fundamental readability issue and the one that affects every visitor to every page where it fails.
Navigation text against navigation background colors. If the navigation is inaccessible to users with color vision deficiencies, the navigability of the entire site is compromised.
Button and call-to-action text against button background colors. Buttons that do not meet contrast requirements create interaction barriers specifically at the points where users are expected to take action.
Form placeholder text. Placeholder text in input fields is frequently implemented with insufficient contrast against the field background. While placeholder text has other accessibility problems — it disappears when users start typing — contrast must be addressed while it is visible.
Error message text and status indicators. If error states or success confirmations rely on color changes that do not meet contrast requirements, users with color vision deficiencies cannot perceive the state change.
Fix 5: Missing or Incorrect Alternative Text
The fifth triage priority is alternative text — specifically for images that convey meaningful information rather than purely decorative images.
Alternative text is the most universally recognized accessibility requirement. It is also one of the most inconsistently implemented. The challenge is not that agencies do not know images need alternative text. It is that the alternative text that exists is frequently wrong — either missing entirely, populated with filename garbage like "IMG_4532.jpg," or written as a generic description that conveys none of the information the image is communicating.
Why this is a triage priority: alternative text failures are ubiquitous, affect every page where images appear, and the failures in high-visibility contexts — homepage hero images, infographics used as primary communication tools, charts and graphs in reports — can be among the most prominent accessibility barriers on an agency's primary web presence.
The images to address first:
Charts, graphs, and data visualizations. When an agency publishes a budget allocation chart, a population trend graph, or a public health data visualization as an image, the alternative text needs to convey the information the visualization communicates — not just describe the image. "Bar chart showing budget allocation by department" is not useful alternative text. The alternative text needs to convey the actual data, or the image needs to be accompanied by an accessible data table that provides the information in a form assistive technology can interpret.
Maps used for informational purposes. A map showing service district boundaries, construction detour routes, evacuation zones, or public facility locations needs alternative text that conveys the geographic information the map communicates. A description of what the map looks like is not sufficient. The information the map contains needs to be accessible through some means — either through detailed alternative text or through an accessible text alternative that accompanies the map.
Infographics. Infographics are frequently used by public agencies to communicate program information, process explanations, and statistical summaries in a visually engaging format. They are also frequently published as images with either no alternative text or alternative text that describes the visual design rather than the content. Every infographic published as an image needs either comprehensive alternative text or a text alternative that provides the equivalent information.
Photos with informational context. Not all photographs need detailed alternative text — a decorative photo of a public building used as a page background does not need to convey information. But a photo of road construction with a caption explaining the detour route, a photo of a public official at a signing ceremony, or a photo of a wildlife species in a management context all have informational value that alternative text should convey.
Logos and institutional marks used as links. A logo that is also a link back to the homepage needs alternative text that identifies the destination — "Return to City of [Name] homepage" — rather than alternative text that describes the logo image. A logo that is purely decorative and not linked should have empty alternative text so screen readers skip it.
The Sixth Thing: Start the Documentation Now
This guide is structured around five fix categories. But there is a sixth thing that is not a fix at all — it is the governance action that makes everything else defensible.
Start the remediation log now. Before the first fix is deployed. Open a spreadsheet, a project management tool, or whatever system your organization uses to track work. Create the fields that a defensible remediation log requires — issue ID, date identified, WCAG criterion, risk classification, affected surface, remediation plan, assigned owner, date remediated, validation method, verification date. And start logging every accessibility action from this point forward with timestamps.
Here is why this matters even before the fixes are complete: the documentation record starts the moment you start logging, not the moment you finish remediating. An agency that has fixed ten accessibility issues and documented all ten with timestamps is in a better position than an agency that has fixed fifty issues with no documentation. Because the first agency can demonstrate the beginning of an ongoing, structured effort. The second agency can only claim it.
The remediation log transforms triage activity into compliance evidence. It is the document that answers the enforcement question "what have you done and when did you do it" with specific, timestamped, organized detail instead of general assertions. Start it on day one. Maintain it every day after.
What Comes After Triage
Triage is the starting point, not the destination. The five categories in this guide represent the highest-return remediation work for agencies beginning from a standing start or working within tight resource constraints. They do not represent a complete compliance program.
After the triage priorities are addressed, the compliance program needs to expand into the full audit scope — lower-traffic pages, secondary documents, vendor tool testing, departmental sites — and needs to be sustained through the monitoring, documentation, and governance structures that prevent regression and create the ongoing defensibility record that ADA Title II requires.
The triage approach is appropriate as a starting point. It is not appropriate as a permanent operating mode. An agency that addresses the five categories and considers the work complete will find itself back at a similar starting point twelve to eighteen months later as new content, vendor updates, and template modifications reintroduce barriers across the environment.
What sustains the progress made through triage is the governance program. Monitoring. Remediation allocation. Documentation. Executive oversight. These are the structures that turn a triage response into a compliance program.
[Create an accessibility remediation log →]
[Understand WCAG 2.1 AA better →]
FAQ: ADA Accessibility Risk Triage
What are the highest-priority ADA accessibility fixes for public agencies? The highest-priority accessibility fixes are those that create direct barriers to core government services and carry the most enforcement exposure. In order of impact: transactional workflow barriers in permit applications, payment portals, and service request systems; global template and navigation issues including missing skip links and invisible focus indicators; inaccessible high-traffic public documents including scanned PDFs and meeting agendas; color contrast failures across primary text and interactive elements; and missing or incorrect alternative text on images that convey meaningful information. These five categories represent the greatest concentration of ADA Title II risk in most public sector digital environments.
Why is prioritization important in ADA accessibility remediation? Prioritization matters because remediation resources are finite and not all accessibility issues carry equal weight in terms of impact on users or exposure under ADA Title II. An agency that fixes high-volume low-impact issues while leaving core service workflows inaccessible has spent significant resources without meaningfully reducing its enforcement exposure. A risk-based prioritization approach focuses remediation on the barriers that most directly deny access to government services, affect the largest number of users, and receive the most scrutiny in enforcement proceedings. Prioritization produces more compliance value per dollar of remediation investment than a volume-based approach.
Can fixing five accessibility issues make a public agency ADA compliant? No. Addressing the five highest-impact categories of accessibility issues is a starting point that meaningfully reduces risk and begins building a defensible compliance posture — it is not a complete compliance program. WCAG 2.1 AA compliance requires satisfying all Level A and Level AA success criteria across the full digital environment. A triage approach is appropriate for agencies beginning with limited resources or needing to demonstrate immediate progress, but it must be followed by a comprehensive audit, full remediation of identified issues, and an ongoing monitoring and governance program to constitute defensible ADA Title II compliance.
How do I know which transactional workflows to test first? Prioritize transactional workflows by service criticality and transaction volume. The workflows that residents or students must complete to access core services — permit applications, tax payments, financial aid applications, license purchases, public records requests — take precedence over secondary or optional interaction points. Within that category, workflows that serve the largest number of users and are most directly connected to required government service delivery represent the highest priority for testing and remediation.
What is the fastest way to identify color contrast failures across a website? Automated accessibility scanning tools including axe, WAVE, Siteimprove, and others reliably detect color contrast failures that fall below WCAG 2.1 AA thresholds. Running an automated scan of the primary website and its most-trafficked pages will surface contrast failures quickly and comprehensively. Contrast failures in global components — navigation, headers, footers, button styles — can be addressed at the template level, resolving them across every page simultaneously. A browser extension like axe DevTools or the WAVE toolbar can be used to check contrast on specific pages without a full scanning subscription.
Should agencies fix accessibility issues before conducting a full audit? Addressing obvious, high-impact issues before a formal audit is not harmful and may demonstrate good faith effort. However, beginning remediation without a baseline audit creates two risks. First, resources may be spent on lower-priority issues while higher-risk barriers remain unaddressed. Second, the audit will be less useful as a baseline document if significant remediation has already occurred, because the starting point it documents will not reflect the agency's pre-program posture. The most efficient approach is to conduct the audit first, use the findings to build a risk-based prioritization model, and then execute remediation in the order the prioritization model prescribes. If time pressure requires immediate action before the audit is complete, focus on the five triage categories in this guide — they represent the most defensible use of pre-audit remediation resources.