When Mootness Works and Fails in Web Accessibility Cases

At Converge, we work with a lot of attorneys who are representing companies that get sued for web accessibility. Most of them have the good sense to just settle their cases immediately—and then start making their sites accessible. This is almost always the best strategy. Yes, your client is being randomly shaken down by a plaintiff who likely never wanted to be their customer. On the other hand, your client’s website likely does have a number of real accessibility problems that could cause discrimination against people with disabilities down the road. Rather than focus on the unfairness of being targeted, wouldn’t it be better to just settle the case and spend your money on your website?

Thankfully, however, there are enough obstinate defendants out there that drag themselves through the mud to create a bunch of caselaw! This post summarizes how mootness works in web accessibility cases. It reviews all of the cases we’ve discussed over the past three years on mootness. Hopefully, in the future, I’ll remember to keep updating this post so you’ll always have the latest information about mootness.

Haynes v. Hooters (11th Cir. 2018)

As I noted almost three years ago, the most famous case addressing mootness in web accessibility is Haynes v. Hooters Restaurants of America, 893 F.3d 781 (11th Cir. 2018). In this case, Mr. Gomez sued the famous restaurant chain and settled the case a few months later. The settlement agreement required Hooters to make their website accessible within six months and the parties agreed to refrain from litigation for two years. Shortly after the six month period expired, a different plaintiff (Mr. Haynes) brought a nearly identical lawsuit against Hooters.

Hooters claimed that Mr. Hayne’s case was moot but the Eleventh Circuit Court of Appeals disagreed. First, while Hooters had made progress in updating their website, there was no evidence that their site was fully accessible. Second, the settlement agreement operated between Hooters and Mr. Gomes—and it had no effect on the relief that Mr. Haynes could pursue against Hooters. Third, because Mr. Haynes was not a party to that contract, he couldn’t enforce it.

Cases After Haynes v. Hooters

Cases after the Hooters case reinforce the idea that mootness usually doesn’t work in web accessibility cases. For instance,

On the other hand, mootness can work in a few cases

And then there are some really questionable decisions that have relied on mootness.

Wow! I thought we had little to say about mootness, but we've actually talked about it a lot!

Making Sense of It All

Looking back, I now notice that mootness has worked in a lot more cases than I thought it had. I still hold to my original claim, however, that mootness is really an uphill argument in web accessibility cases.

Why is that? It simply that websites are not simple, static creations. Physical barriers in the real world can be easily identified and, once removed, they tend to stay removed. Websites never stay the same because content is always being added and taken away. Also, unless an organization has really tight policies, there is also no guarantee that things will stay the same. Usually, all it takes is one part-time college intern adding inaccessible content to a website to mess everything up!

Putting aside the questionable decisions and focusing at the cases where mootness has legitimately worked bears out what a defendant needs to do to make a mootness claim work:

  1. completely remove the type of barriers that the plaintiff encountered and
  2. implement clear policies to make sure that new barriers of the same type are not created in the future

Note also that, in three out of the four cases where a mootness claim worked, the plaintiff’s allegations involved non-captioned videos. Removing a video from a website takes little to no skill, other than a passing familiarity with the content management system (CMS) editor. Hardly any of the cases that we see involved captioning, however.

Also note that, of the two elements to a good mootness claim, it’s the second element that is really hard to establish. If you have a competent audit performed by any accessibility consultant truly worth their salt, you’re going to know all of your existing barriers and you’ll be able to make your website accessible. The problem is implementing clear policies to keep it that way. Sure, you can try to use automated solutions (but they miss three-quarters of accessibility problems—and probably won’t catch the big blocking issues identified in your audit) or you can try periodic “light” manual testing (but you’ll likely have a lot of problems that keep slipping between the cracks), but those "solutions" really don't meet the bar because one of your content creators will inevitably create inaccessible content at some point unless your policies focus on them.

How Can Converge Make a Difference?

At Converge, we believe that our accessibility solutions are more robust than other accessibility consultants for one simple reason—we help you create the policies to keep your content accessible. While I really believe mootness is a tough argument for defendants to win, I believe we can get you a better solution for winning a mootness claim. Here's why.

Recently, we realized that the real source of the problem was a lack of rigorous training for content creators. Now, when we do an accessibility audit and review the results with developers, we try to separate (1) the errors that were created by content creators from (2) the errors that were part of the CMS infrastructure. This enables us to create a learning management system (LMS) based training course specific to the types of errors that those content authors created (and which landed you a lawsuit in the first place). And, because it’s in an LMS, supervisors can spot exactly who has taken the course and whether they’ve passed all the tests showing that they know exactly what to do based on the actual problems found on your website. In the world of web accessibility, this is as close to a “clear policy to make sure that new barriers of the same type are not created in the future” (see element number 2, above) as you're likely to find.

If you’re using a different accessibility consultant, chances are that they haven’t thought about solutions like this—or how they can help you avoid risk in the bigger picture. And they probably don’t offer solutions like WebAlign®, which can make your whole web development lifecycle revolve around WCAG-compliance. Instead, they probably just want to convince you to sign up for more of the same expensive audits or ineffective (but snazzy looking) automated testing tools. The difference is knowing what the law requires... and then creating technical solutions that get you as close as possible.

If you’d like to see how we can offer you really effective, innovative solutions that actually make a difference, reach out today!


Nothing in this post should be interpreted as legal advice or as forming an attorney-client relationship. It is offered for educational purposes only. You should always contact a qualified attorney in your area to discuss your legal rights and responsibilities.

Want to See More Content Like This?

Want the latest blog posts, videos, white papers, and announcements? Sign up for our mailing list and stay in the loop!

We're Here to Help When You're Ready

Take a deep breath. Then feel free to reach out to our team when you're ready to discuss your accessibility needs.

0 comments on “When Mootness Works and Fails in Web Accessibility Cases

Leave a Reply

Your email address will not be published. Required fields are marked *

Click to access the login or register cheese