Government websites are essential in daily life, providing residents access to critical services, information, and public resources. Each state and local municipality has a dedicated website connecting people to government activities.
As someone who is blind and relies on a screen reader to navigate websites, I depend on these sites just like anyone else. I recently used my state's website to apply for a new ID card and frequently visit my local county site to check public event listings, announcements from elected officials, and weather alerts. Unfortunately, despite their importance, many government websites contain accessibility barriers that make them challenging—or even impossible—for people like me to use independently.
Government websites serve various needs, from researching assistance programs to connecting with local officials on social media, finding public transit information, or accessing court records. Because they are used for many tasks, these websites must be accessible to all residents, including those with disabilities.
In this blog, I'll discuss three areas where government websites often lack accessibility. In preparation for this post, I explored several government sites—some local to me and others from different regions of the country that I'm familiar with. As always, I'll focus specifically on my experience using a screen reader as my assistive technology of choice.
It's crucial to note that the Department of Justice (DOJ) has established specific deadlines for state and local governments to ensure their websites and mobile applications are accessible to people with disabilities:
These deadlines emphasize the urgency for government agencies to address accessibility issues before they become legal liabilities. However, achieving compliance is not always straightforward, especially amid evolving regulations and political uncertainty. For a deeper understanding of these challenges, including insights into recent legal rulings and the impact of political shifts on ADA Title II enforcement, you can refer to UsableNet's article, "Navigating ADA Title II Compliance Amid Political Uncertainty."
To further assist government organizations in preparing for these requirements, UsableNet offers additional resources:
One thing that I discovered is that government websites utilize a lot of pop-ups. Because municipalities must follow specific legal requirements regarding web privacy, it is often necessary to warn the user that web cookies are being used to enhance the experience. These cookie pop-ups usually appear upon page launch and must be dismissed before the user can continue to the main website.
Websites will use Pop-ups to encourage enrollment in email lists that provide essential government updates to residents. I always encounter pop-ups on my local county website when there is bad weather. A pop-up will appear upon page launch, displaying published weather alerts and available government resources for anyone affected by the weather event. The website visitor must dismiss the pop-up to continue using the website.
I often have trouble doing this because the action buttons in the pop-up are not labeled, so my screen reader cannot access them. When this happens, I must either abandon my mission or repeatedly refresh the page, hoping the pop-up will fail to appear at some point. The irony is that the accessibility of the rest of the website is generally solid.
If pop-ups are used on a government website, there must be a clear and intuitive method for closing the window. All web elements in the window—including buttons, links, and images—must be labeled or described in the website's code.
Additionally, suppose a sighted user can dismiss a pop-up without taking action. In that case, screen reader dependents should be able to do the same. For example, a cookie notice pop-up may have an action button at the bottom labeled "Accept All Cookies." In the top right corner of the window is a small "X" button that allows the user to close the pop-up without opting into cookies.
A lot of times, while the "Accept All Cookies" button will be accessible to screen reader users, the "Dismiss" icon will not. As a result, we are either forced into allowing cookies, which could be a web privacy concern or compelled to not use the website at all.
From what I have observed on the government websites I have used, the design and structure of most of these sites seem relatively standard and consistent. In general, the homepage will have various sections. Each section typically has some text, an image or two, and a button or link that directs users to another site page with more information or an external website where visitors can complete their task.
For example, a section may be "Get A New State ID." That section will include links to the online applications for different levels of state ID or driver's licenses. Another example could be a section called "Things To Do In February," with content that includes images of fun activities in a specific area and links directing users to relevant external websites for more information.
The section titles are usually at heading level one or level two. This practice is key for screen reader navigation. When exploring a site that uses a design structure like the one described above, I set my screen reader to filter by heading and then move through the page, hearing only the content at each heading level.
Doing this lets me quickly navigate the page until I hear the information section category name I am searching for. Suppose the heading levels are unmarked in the code for the section titles. In that case, I must explore the page manually, moving only one web element at a time until I get to the desired category section. A lack of headings can drastically slow me down and make for a long, clunky, unintuitive experience.
Government websites should serve everyone, but too often, accessibility barriers make them frustrating or unusable for people who rely on screen readers. With DOJ deadlines fast approaching, state and local governments must take action now to ensure compliance.
The most significant issues I've encountered include:
These aren't minor inconveniences—they are real blockers that prevent equal access to public information and services. Accessibility isn't just a legal requirement—it's a fundamental right. Government websites need to do better.
For guidance on compliance and accessibility best practices, check out UsableNet's ADA Title II Compliance Guide and start making accessibility a priority today.