Up until this last weekend, I had very little to report on—then came the Supreme Court’s decision in Loper Bright Enterprises. But first things first…
TL;DR
I never expected or wanted this post to go on as long as it does. If you're a legal geek, have at it. If you're in hurry, here's the essential points.
- California AB 1757 is back. If it passes into law, it could make life uncomfortable to any company that makes web-based solutions for others.
- Think politics don't matter with web accessibility? The Supreme Court's opinion in Loper Bright just came down and may threaten any new web accessibility regulations-- including the DOJ's recent Title II regulation.
- Using a consent decree to avoid future litigation is a clever idea. Don't be a fool, however, and brag about it to the judge before he signs it.
California’s Senate Amends Assembly Bill 1757
On June 12, the California Senate substantially amended AB 1757. Back in April, I was premature in reporting that AB 1757 had been replaced by SB 1486. Instead, AB 1757 is very much alive and was carried over to the current session. I won’t get into all the details of the new bill because it affects too many aspects of web accessibility liability. Some of the highlights that jumped out to me, however, included,
- The bill dropped the idea of using an IAAP-certified reviewer’s report as a defense to an ADA lawsuit. The new bill creates a defense based on posting a “digital accessibility report” but it doesn’t specify the qualifications of the tester and instead outlines other qualities of the report and where it needs to be posted.
- The new bill maintains liability for “resource service providers.” The new bill maintains liability on such companies if a defendant “reasonably relied” on them to maintain a portion of their website to be accessible. There was something about this section that seemed targeted towards overlay providers—or other companies that may have historically made bold marketing promises that their tools guaranteed WCAG conformance.
- Liability for “resource service providers” now extends to any such entities who “in exchange for money or any other form of remuneration, to intentionally, negligently, recklessly, or knowingly… construct, license, distribute, or maintain for online use any resource or part of an internet website that, when used by the entity in accordance with any instructions provided by the resource provider, causes an entity’s internet website to be inaccessible.”
It's that last point that has potentially has the biggest impact. Most organizations rely on other vendors to create the content management systems, online courses, and other web content. Our website, for instance, relies on WordPress and countless plug-in’s to make it easy to deliver content like this blog that you are reading. I thought it would be interesting to run through some scenarios about how liability under AB 1757 would work.
- Scenario 1 (Company Uses Cloud-Based Solutions). Let’s assume that a company uses a cloud-based solutions (e.g. Google Docs or Microsoft Office 365) to deliver content to the public. If this solution wasn’t accessible, then Microsoft or Google could be sued by a member of the public who couldn’t access the content. In addition, the company relying on Google or Microsoft could also sue them.
- Scenario 2 (Employee of Company in Scenario 1). An employee of the company could also potentially sue Google or Microsoft in Scenario 1. This wouldn’t be based on traditional employment law—instead, it would be based on the resource service provider’s liability under AB 1757.
- Scenario 3 (State Agency in Scenario 1). Now things get interesting. Let’s assume that it was a state agency that was using the cloud-based solution. AB 1757 as currently written allows government attorneys to sue under the bill. This could be a very powerful tool for public entities that are trying to comply with the new ADA Title II web accessibility regulation.
The bill includes some commonsense limitations. For instance, if the resource service provider created an update that solved the accessibility problems, they would be absolved of liability—regardless of whether their customer chose to install the update or not.
AB 1757 is highly controversial. I think the current set of amendments makes a bit more sense than the version last year but it will inevitably ruffle a lot of feathers in the IT world.
The Supreme Court Overturned Chevron!
The biggest news in digital accessibility this month has nothing to do with digital accessibility: on Friday, June 28th, the Supreme Court overturned Chevron U.S.A., Inc. v. Natural Resources Defense Council, Inc., 468 U.S. 837 (1984). A quick search of our site reveals that I have talked a lot about Chevron—and what overturning it would mean for digital accessibility. In fact, just two weeks ago, I talked about it extensively in the context of the Supreme Court’s decision in Garland v. Cargill, 144 S. Ct. 1613 (2024). All of my earlier posts presaged the inevitable which happened on Friday—the Chevron decision is now overturned in its new decision Loper Bright Enterprises v. Raimondo, 2024 U.S. LEXIS 2882 (2024)
Unless you’ve been living under a rock for the last 20 years, you’ll know that there has been frustration at our government. A lot of that frustration has to do with the complex regulations created by “the swamp”—the administrative state of government attorneys and policy officials in federal agencies who try to make our government function. Whether you see yourself on the political left or right side of the spectrum, federal agencies serve an important function of administering the laws that Congress creates. Because laws are always vague, that means that they have to “fill in the gaps.”
Need proof? Just look at the ADA, as written by Congress. While you’re looking over the statute, try searching for basic concepts like, “service animal” or “sign language” and see what you come up with. Answer? Zilch. Zero. Nada. All of the basic protections that we take for granted were provided by the Department of Justice in its implementing regulation. Into the basic ADA requirement to “make reasonable modifications in policies,” DOJ’s regulation added a requirement to accommodate service animals. And into the phrase “auxiliary aids and services,” DOJ added the requirement for effective communication, which included sign language interpreters.
The Loper Bright decision dealt with another ambiguous law. The case concerned the power of the National Marine Fisheries Service (NMFS), an agency under the Department of Commerce, to implement and enforce the Magnuson-Stevens Fishery Conservation and Management Act (MSA), which enabled the NMFS to set specific limits on fishing in coastal waters. The MSA also required several groups of fishermen to bear a portion of the costs of maintaining “observers” onboard ships to ensure that the rules were followed but Atlantic herring fishermen were not included in this group. The NMFS created a regulation that required Atlantic herring fisherman to pay for similar observers and the herring fisherman challenged the regulation.
The herring fisherman would lose if the court followed its earlier Chevron case. The Chevron case applies where Congress is silent or ambiguous about a specific issue—just it was with not covering herring fishermen in the MSA. In such cases, Chevron requires courts to ask two questions. First, courts must ask if the law was clear or if it left ambiguity or a gap. There was a gap because the law did not specify who paid for observers for herring fishermen and NMFS had the clear authority to implement the MSA. Second, the court must ask if the rule or interpretation is “rational” or “reasonable.” This generally means asking whether the agency’s interpretation is not inconsistent with the clear statutory language. This second requirement was also met because imposing an extra fee to cover the cost of onboard observers was not inconsistent with the statute’s language. If both tests are met, then the court must defer to the agency’s interpretation even if the court disagrees with it.
Of course, in Loper Bright, the Supreme Court rejected Chevron. Instead, Chief Justice Roberts stated that the courts were to be the final interpreters of laws and that they never had to defer to federal agencies' interpretations. According to the Chief Justice, courts should only “respect” agency interpretations and use them to help inform the court’s independent interpretation of statutes.
Fundamentally, Justice Robert’s opinion belies a basic mistrust of federal agencies. The entire opinion comes down to a pair of sentences in the middle of the opinion.
Perhaps most fundamentally, Chevron’s presumption is misguided because agencies have no special competence in resolving statutory ambiguities. Courts do.
Loper Bright Enterprises, at *45. There are two huge problems with this analysis. The first problem, of course, is that it is undemocratic; it allows one (unelected) federal court judge to substitute her interpretation of how a statute can be read for the democratic notice-and-comment rulemaking process that federal agencies go through when they create a regulation. After all, agencies don’t just develop regulations out of thin air. Instead, they publish a draft regulation, receive dozens (or maybe hundreds) of thoughtful comments from the public, and publish a regulation that explains how they came to their decision. The second problem is that the Loper Bright opinion invites every federal court judge to inject their own (separate) opinions over every regulation, potentially bringing our federal government to a standstill. Remember all that nonsense of having mifepristone banned across the country (based on the opinion of one district court) only to have it allowed later when the case made it up to the Supreme Court? Overturning Chevron could make this a daily occurrence for every federal regulation. The Supreme Court may have drained the swamp in the federal agencies, but it created a far, far worse one in the federal judiciary.
How Does Loper Bright Affect Digital Accessibility?
When I first heard that Chevron might be overturned, I immediately thought about DOJ’s web accessibility regulations. Now that the Loper Bright has come down, here’s my take.
First, I think that DOJ’s Title II regulation is relatively safe. As I mentioned earlier, no one questions that Title II covers web-based programs, services, and activities offered by state and local governments. While the Loper Bright opinion discarded Chevron deference, the last paragraph in the Court's opinion offers the ADA regulations a glimmer of hope.
Chevron is overruled. Courts must exercise their independent judgment in deciding whether an agency has acted within its statutory authority, as the APA requires. Careful attention to the judgment of the Executive Branch may help inform that inquiry. And when a particular statute delegates authority to an agency consistent with constitutional limits, courts must respect the delegation, while ensuring that the agency acts within it. But courts need not and under the APA may not defer to an agency interpretation of the law simply because a statute is ambiguous.
Loper Bright, at *61-62 (emphasis added). Congress didn’t tell the NMFS to create regulations implementing the MSA; instead, the NMFS created a regulation to fill a gap left in the statute. By contrast, Congress very clearly told the Department of Justice to create implementing regulations under Title II when it passed the ADA. This means that the courts should defer to the DOJ’s regulation—so long as its regulation is consistent with the delegation of authority.
That last clause may be the Achilles’ heel of the new Title II web accessibility regulation, however. This is because Congress tends to be very clear when it wants an agency to create technical standards—such as when it directed the Access Board to create the ADA design standards or when it directed the Access Board to create the Section 508 technical standards. Congress included a special paragraph directing the Attorney General to create regulations and "include standards applicable facilities and vehicles" consistent with the Access Board's regulations. A clever attorney could argue that Congress never delegated authority to DOJ to create technical standards for websites because websites are neither "facilities" nor "vehicles." When it adopted the Web Content Accessibility Guidelines (WCAG) for state and local government websites, DOJ was setting standards for something completely different. Because Congress didn't tell DOJ to issue standards beyond vehicles and facilities, its adoption of WCAG falls in a gap or ambiguity that Loper Bright covers-- and that a clever attorney could use that fact to have the regulation invalidated.
A Title III web accessibility regulation for private sector websites would also be vulnerable for the same reason if it included WCAG or any other specific standard because Congress used the same language as in the Title II regulation directing the Department of Justice to create regulations and "include standards applicable to facilities and vehicles. However, a Title III web accessibility regulation is far more vulnerable than a Title II web accessibility regulation because the Department of Justice would also have to decide whether websites are "places of public accommodation." That's a huge ambiguity under the ADA and the cause of a major split in the circuit courts. It's easy to imagine a defendant arguing that this question was outside Congress’s delegation of authority.
In both cases, the Department could argue that it wasn't creating a website standard when it adopted WCAG. Instead, WCAG is a set of guidelines and state and local governments don't have to meet WCAG if they can show that doing so has "minimal impact on access" for people with disabilities. This argument will likely not succeed because the regulation first requires WCAG compliance and then allows entities to avoid WCAG compliance if they can show doing so has minimal impact on access. A safer (but less effective) DOJ could have written the regulation would have been to require websites to provide effective communication, and that conformance with a set of guidelines like WCAG would be considered a "safe harbor" in providing effective communication.
The Department might also try to argue that "adopting" WCAG isn't the same as "issuing" standards. I also don't think that argument is a winner because rulemaking agencies frequently adopt or incorporate by reference standards (e.g. ISO, ANSI, etc) created by other bodies.
How Will Loper Bright Affect Future Federal Digital Accessibility Laws?
When I first read the Loper Bright opinion, I thought any regulations were fair game for litigation. Instead, the Loper Bright opinion applies mainly to regulations where Congress either doesn't tell an agency to create implementing regulations (so-called "implicit delegation") or doesn't do a very good job explaining where regulations are needed (badly defined gaps and ambiguities). Loper Bright doesn't apply where Congress specifically directs an agency to develop regulations.
This means that Congress must be much more detailed in future statutes and outline exactly when regulations are needed and what they must cover. I don't see that happening in this age of deeply partisan politics. History should show that Loper Bright only yielded two unpleasant outcomes: either more political logjams as Congress bickers over where to draw the line delegating authority to federal agencies or endless litigation where those lines weren't precisely drawn.
This Shouldn't Be a Political Decision
It's sad that the Loper Bright decision came down to politics (the 6-3 decision was split on political lines) because agency deference shouldn't come down to politics. After all, the Chevron opinion was originally hated by liberals because it reinforced Reagan-era cuts to the Clean Air Act. You can also be certain that, should the Republicans win the presidency in November, Democrats will happily use Loper Bright to dismantle or limit any changes to regulations that the Republicans make. The net effect is that the federal government will become much less efficient. The federal government isn't going away; now, the inefficiency of our government will loom larger than ever before.
If You Want to Use a Consent Decree to Avoid Future Litigation, Try to be Subtle About It
One of the few cases that came across my Lexis radar this month was Cruz v. JKS Ventures, Inc., 2024 U.S. Dist. LEXIS 109827 (S.D.N.Y. 2024). This opinion should have been completely without controversy: it was just a judge reviewing and approving a consent decree. This case demonstrates, however, that the parties can blow an easy opportunity if they’re not careful.
In previous blog posts, I’ve mentioned that a huge benefit to consent decrees is their res judicata effect in avoiding subsequent litigation. But if you’re a defendant, that’s not the motive you want to tell the judge. In the JKS Ventures case, however, the defendant stated that, “"the purpose of the Consent Decree is to provide protection to Defendant[], . . . against potential copycat lawsuits by other plaintiffs who may come forward to assert similar claims based on the putative access violations that are being address[ed] and resolved pursuant to this settlement.” Id. at *8-9.
Pro tip here. If you’re a defendant wishing to use a consent decree to shield yourself against future litigation, try not to advertise that motive. While this concept should be common sense to any defense counsel, it was lost here. This naturally led the judge to question whether the plaintiff and defendant were colluding to use their consent decree as a mechanism to evade liability. Thankfully for the defendant, the judge found just enough evidence to tip this case over the line and allow the judge to conclude that there wasn’t any collusion between the parties. Or maybe the judge didn’t want to deal with this case anymore?
Disclaimer
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 “Legal Update: June 2024”