Protect Your Website: Accessibility Lawsuit Insights

Protect Your Website: Accessibility Lawsuit Insights

Join Natalie MacLees and Natalie Garza for the 29th episode of the AAArdvark Accessibility Podcast. They delve into the significant rise in ADA lawsuits related to digital properties, examining how these lawsuits affect small business websites and government entities. The discussion covers key statistics, including the increase in state-level lawsuits, repeat lawsuits, and the impact of accessibility widgets. They also emphasize the importance of education and proactive efforts in making websites accessible.

Natalie Garza: Hello everybody and welcome to the AAArdvark Accessibility Podcast. My name’s Natalie Garza. I’m one of the co-hosts, and with me today is,

Natalie MacLees: Natalie MacLees, the other co-host.

Natalie Garza: and she is a digital accessibility expert here to answer our questions. Talk to us about today’s topic, which is how accessibility lawsuits have affected small business websites and also government websites.

So we’re gonna go through some statistics and then dive in. So to get started, first one, we found that “Over 4,000 ADA lawsuits related to digital properties were filed in 2024. With a decline in federal cases and an increase in state level lawsuits, particularly in New York and California.” (UsableNet 2024 Report)

Natalie MacLees: I think generally the decline in the federal cases is probably due to the change of the administration at the federal level and the administration demonstrating a different set of priorities around accessibility right now. So we see those cases kind of shifting to the state level.

California has a Civil Rights Act, the Unruh Civil Rights Act, that was passed in 1959. Which does let plaintiffs claim $4,000 per violation, per person, per visit, so that does create an incentive structure for frivolous lawsuits, unfortunately. Not all accessibility lawsuits are frivolous. But there is a problem I think, in the industry with abuse of using the judicial systemfor personal gain.

And there are definitely legitimate cases, and I don’t wanna take that away from anybody, but there are also cases where it seems like nobody actually did go try to use the website, and then they file these lawsuits.

So unfortunately, there’s that incentive for that to happen, and it’s meant to be an incentive for small businesses and government websites and things like that, it’s meant to be an incentive for them to avoid those fines and fees and make their, you know, the, it’s not just their websites, right? That law applies to physical locations, like having a wheelchair ramp for your restaurant and accessible restrooms, like it applies to all different all different situations, but it does include websites.

So it’s meant to be an incentive for businesses and governments to make things accessible. And I think it has accomplished that to a certain degree, but I think it also has this kind of other unfortunate side effect, that we see.

And then in New York, there’s not a specific law in New York that’s causing the extra lawsuits there.

I think it’s just a friendly court district that happens to be in New York, and I know that there are a lot of family-owned wineries in upstate New York that have been for some reason targeted by these lawsuits. Which is also unfortunate that what’s getting targeted are they small family run businesses.

I agree that they should all have accessible websites and accessible premises I think they should be doing everything that they can to make their websites and their shops accessible. But...

Jaksot(25)

WCAGs Cousins – ATAG, UAAG, PDF/UA

WCAGs Cousins – ATAG, UAAG, PDF/UA

Join Natalie and Natalie in the twelfth episode of the AAArdvark Accessibility Podcast as they explore the lesser-known cousins of WCAG: ATAG, UAAG, and PDF/UA. They discuss the importance of these guidelines for authoring tools, user agents, and PDFs and explore how implementing them can significantly enhance web accessibility. The episode also touches on the real-world implications and the responsibilities of tool developers in creating accessible software. Natalie Garza: Hello, everybody, and welcome to this episode of the AAArdvark Accessibility Podcast. My name is Natalie G, and with me today is, Natalie MacLees: Natalie MacLees. Natalie Garza: Yes, thank you for joining us today, Natalie. Natalie MacLees: Thanks for having me. Natalie Garza: Yes, this is the twelfth episode, and in this podcast episode, we’re gonna talk about WCAG’s cousins. Let’s talk about cousins. They are ATAG, UAAG, and PDF/UA. Natalie MacLees: Yeah, I’m pretty sure those are the official names. Natalie Garza: Yes, we’re gonna go over each one. Natalie MacLees: The other accessibility guidelines. Natalie Garza: Yes, the not-so-mentioned, often forgotten, but they’re here, and we’re gonna talk about them. Alright, Natalie, what is, what is WCAG? It’s just a refresher for our audience.  Natalie MacLees: WCAG, W C A G, stands for the Web Content Accessibility Guidelines, and it’s what applies to any kind of online content or software, even though the name is web content. So like online web apps and things like that, it also applies. Natalie Garza: Yes, and I feel like if you put any attention into the accessibility space, that’s all you hear. WCAG this, WCAG that. Natalie MacLees: Yes, you do hear it a lot. People talk about WCAG a lot and they don’t talk about its cousins. Natalie Garza: What are the cousins, Natalie? We want to start with ATAG? Natalie MacLees: I usually say A-TAG, but okay, we can call it whatever you want. ATAG, Authoring Tool Accessibility Guidelines. You’ll notice they all end in A G because they’re all accessibility guidelines. And this is a set of guidelines meant for authoring tools. So things like your favorite CMS. Whether that’s Drupal, WordPress, Wix, Weebly, Squarespace, etc. There’s literally hundreds of them at this point and ATAG should be applying to all of these things. Unfortunately, it is not very evenly implemented. And ATAG aims to do two things with an authoring tool. Number one, it aims to try to make sure that people with disabilities can use the tool. And, so in that way, it’s all of the WCAG rules just applied to, you know, the admin editing interface of, you know, WordPress or whatever to make sure that if you’re using a screen reader or your keyboard only, or, you know, whatever kind of assistive technology you’re using, you can go in and write blog posts and add images and all of those kinds of things. The other part of ATAG is to help you, as an author, make sure that your content that you’re creating is accessible. And so it should have little tips and little warnings that show up. If you try to put white text on a pale yellow background, you should see some kind of warning come up that just says, “Oh, hey, you might want to pick a different color here. This isn’t accessible.” It should have little reminders, “oh...

21 Helmi 31min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
mimmit-sijoittaa
psykopodiaa-podcast
rss-rahapodi
ostan-asuntoja-podcast
yrittaja
rss-lahtijat
rss-lentopaivakirjat
rss-rahamania
rss-sensuroimaton-kukkonen-kausi-3
rss-paasipodi
herrasmieshakkerit
leadcast
pomojen-suusta
lakicast
rss-myynti-ei-ole-kirosana
rss-seuraava-potilas
pari-sanaa-lastensuojelusta
rss-myyntipodi
rss-kohti-unelmia