Everything You Need to Know About the AccessiBe Debate
Tags: a11y, webdev, frontend, discuss
Published: 2021-07-25 15:23:59

_Disclaimer: The following views do not reflect my employer nor any person nor organization I am, or have ever been, affiliated with. Opinions are my own._

## Jump to Section
  * [How accessiBe Really Works](#section-1)
  * [Accessibility and Disability Community Discourse](#section-2)
  * [Who accessiBe is For and Not](#section-3)
  * [That Which I Believe](#section-4)

## Setting the Scene
Recently, I came across this article by Anna E. Cook, a Senior Accessibility Designer, on how there is no such thing as fully automated accessibility 🙅🏻‍♀️

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I wrote this article last night, as promised.<br><br>I hope only to add to the conversations already shared by others about accessiBe and similar products.<a href="https://t.co/zKINM2tGPk">https://t.co/zKINM2tGPk</a></p>&mdash; Anna E. Cook (@annaecook) <a href="https://twitter.com/annaecook/status/1415666401663090701?ref_src=twsrc%5Etfw">July 15, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

![An illustrated french press machine being compared to automated tests. Grinding coffee beans is like automated testing catching under 25% of accessibility violations. Low effort is like the "automated" part of automated testing. And low quality is like saying automated testing is a good first step. Lists examples of automated testing tools: Lighthouse, Wave Tool, Accessibility Insights Fastpass, and axe-core](https://madalyn.dev/static/b917d6a311a6de42b6f64848f4d9e5d3/8aace/french-press.png)
_Source: Madalyn Parker's [blog](https://madalyn.dev/blog/a11y-testing-coffee)_

Turns out, though, there is a company who claims that with just two things - an overlay and AI - it can make your website compliant with WCAG 2.1, ADA Title III, Section 508, and EAA/EN 301549, for an affordable price.

This company is [accessiBe](https://accessibe.com/) and they provide a solution that is automated and scalable, growing with you into the future as your site evolves.

In other words, it saves you time and money if your product development cycle didn't include the disability community in the first place.

I wanted to get the following answers:

**1)** What does accessiBe actually do under the hood? 
**2)** Does it actually make the lives of those in the disability community, better?

## How accessiBe Actually Works <a name="section-1"></a>

I always like to guess how something actually works before going to see what it actually does. So I theorized it did the following:

```javascript
/* Missing alt text
  - Look for every instance of <img> tags using a parser
  - Check if it has an alt attribute
  - If it doesn't, use machine learning to determine what the 
    image is and create an alt attribute with the result
  - Celebrate DOM manipulation and AI powers with beers
*/
```

Now, I knew that there were three different demos on accessiBe's site explaining what it does - including a really long one from the CEO.

However, like a reporter with a good cause, I needed to see it myself.

So I signed up for a free trial 🤡 and tested it out on my website, whose code I am familiar with and is a work-in-progress.

_(I provided the phone number of the [Indian Residential Schools Survivors Society](https://www.irsss.ca/) so they can't call me. #reconciliation #sneaky)_ 

![Screenshot of my website which has two main sections: on the left, a vertical hero image of me sitting on a rooftop and on the right, the text for my site](https://i.ibb.co/t2P6Zgh/Screen-Shot-2021-07-24-at-3-32-53-PM.png)
_Source: My dumpster [website](clearlythuydoan.com)_

The first thing that I noticed was I couldn't test accessiBe locally because you have to provide the domain name for your trial. Couldn't use localhost:3000.

So I had to push this commit:

![Git commit that reads, "Our values do not align but I need answers. Equal access is more than just compliance. Testing accessiBe.](https://i.ibb.co/5xS66W6/Screen-Shot-2021-07-24-at-3-37-06-PM.png)

From inspecting the elements of my website, I could see that there were new css classes everywhere as well as aria attributes. And it created [skip links](
https://www.w3.org/TR/WCAG20-TECHS/G1.html) to make it easier for keyboard and screenreader users to move around the page.   

![Screenshot of html](https://i.ibb.co/h8dxhKt/Screen-Shot-2021-07-24-at-3-46-19-PM.png)

And when you activated it, you could access and do the following:

**Access skip links to navigate sections if there were none:**

![Screenshot of a website using skip links](https://i.ibb.co/G2CpjfV/Screen-Shot-2021-07-24-at-4-10-15-PM.png)

**Make visual changes like improve readability:**

![Screenshot of a website's text readability being improved by enlarging it and altering the contrast](https://i.ibb.co/qWMNyVk/Screen-Shot-2021-07-24-at-4-07-41-PM.png)

![Screenshot of a website using a visual ruler that grays out everything beyond the focus zone to improve readability](https://i.ibb.co/Jxd6R71/Screen-Shot-2021-07-24-at-4-09-59-PM.png)

Just to name a few.

After watching the CEO's demo on 2x, he confirmed to me that I was right about how their AI handles images. He also went on to explain other situations like how it uses its AI to handle a lack of [semantic html](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML). Let's say a site has multiple lists but none of them use the appropriate tag. It will make the great guess as to which one is the main menu and then alter that tag in the DOM. 

## Accessibility / Disability Community Discourse <a name="section-2"></a>

While accessiBe states that it includes people in the disability community in user testing, and states that its vision is "to make the entire internet fully accessible to people with disabilities by 2025", there has been backlash.

**Banned by largest U.S. Blind Advocacy Group**
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Largest U.S. Blind Advocacy Group Bans Web <a href="https://twitter.com/hashtag/Accessibility?src=hash&amp;ref_src=twsrc%5Etfw">#Accessibility</a> Overlay Giant AccessiBe: <a href="https://t.co/8HLMuFLffd">https://t.co/8HLMuFLffd</a> via <a href="https://twitter.com/Forbes?ref_src=twsrc%5Etfw">@Forbes</a> H/T <a href="https://twitter.com/Spellacy?ref_src=twsrc%5Etfw">@Spellacy</a>! <a href="https://twitter.com/hashtag/A11y?src=hash&amp;ref_src=twsrc%5Etfw">#A11y</a> <a href="https://t.co/xAbclS863N">pic.twitter.com/xAbclS863N</a></p>&mdash; Meryl Evans speaks at #ID24 and #CMWorld. (@merylkevans) <a href="https://twitter.com/merylkevans/status/1410974302770450433?ref_src=twsrc%5Etfw">July 2, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

**Descriptions about what's still bad even with use**
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Broken headings and tables. Misleading alt text. False advertising. Trapped keyboard focus. Zero support for non-HTML content. Sock-puppet reviews.<br>Here&#39;s a vision: read our stories in the <a href="https://twitter.com/hashtag/AccessiBe?src=hash&amp;ref_src=twsrc%5Etfw">#AccessiBe</a> thread before aggressively singling out critics for homework. <a href="https://twitter.com/hashtag/BelieveUsers?src=hash&amp;ref_src=twsrc%5Etfw">#BelieveUsers</a> <a href="https://t.co/svigYipn2j">https://t.co/svigYipn2j</a></p>&mdash; Chancey Fleet 🌈👩‍🦯 (@ChanceyFleet) <a href="https://twitter.com/ChanceyFleet/status/1366573648346284034?ref_src=twsrc%5Etfw">March 2, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

**A talk about how you can't out-code bad design (agree).**

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">You can never out code bad <a href="https://twitter.com/hashtag/design?src=hash&amp;ref_src=twsrc%5Etfw">#design</a>. Next week we discuss The Fatal Flaw of Overlays, led by the talented <a href="https://twitter.com/ShellELittle?ref_src=twsrc%5Etfw">@ShellELittle</a>. Join us at 3pm ET on July 28th. <a href="https://t.co/XyBzIfplK7">https://t.co/XyBzIfplK7</a> <a href="https://t.co/AG4rlY49WX">pic.twitter.com/AG4rlY49WX</a></p>&mdash; A11yTalks (@A11YTalks) <a href="https://twitter.com/A11YTalks/status/1418236907411099652?ref_src=twsrc%5Etfw">July 22, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

**A comparison to cancer.**

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">accessiBe is a cancer on the internet. I wrote about the insidious framing it uses to source customers and propagate harm. <a href="https://t.co/la4bj0pj1A">https://t.co/la4bj0pj1A</a></p>&mdash; Eric Bailey (@ericwbailey) <a href="https://twitter.com/ericwbailey/status/1418208693330399239?ref_src=twsrc%5Etfw">July 22, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

**And a Deafblind human rights lawyer cautioning against it.**

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">An alarming number of companies have fallen for it. Millions of dollars have poured into it. Beware of <a href="https://twitter.com/hashtag/AccessiBe?src=hash&amp;ref_src=twsrc%5Etfw">#AccessiBe</a>, <a href="https://twitter.com/hashtag/AudioEye?src=hash&amp;ref_src=twsrc%5Etfw">#AudioEye</a>, <a href="https://twitter.com/hashtag/EqualWeb?src=hash&amp;ref_src=twsrc%5Etfw">#EqualWeb</a>, <a href="https://twitter.com/hashtag/User1st?src=hash&amp;ref_src=twsrc%5Etfw">#User1st</a>, <a href="https://twitter.com/hashtag/UserWay?src=hash&amp;ref_src=twsrc%5Etfw">#UserWay</a>, &amp; other automated web <a href="https://twitter.com/hashtag/accessibility?src=hash&amp;ref_src=twsrc%5Etfw">#accessibility</a> &quot;solutions.&quot; I made this video to alert those new to <a href="https://twitter.com/hashtag/a11y?src=hash&amp;ref_src=twsrc%5Etfw">#a11y</a> <a href="https://t.co/j0nAgpaFsb">https://t.co/j0nAgpaFsb</a> <a href="https://t.co/IcsCHcJc1M">pic.twitter.com/IcsCHcJc1M</a></p>&mdash; Haben Girma👩🏿‍🦯 (@HabenGirma) <a href="https://twitter.com/HabenGirma/status/1390051536819023873?ref_src=twsrc%5Etfw">May 5, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

To summarize, main criticisms include the following:
- You can't automate your way to accessible products
- Overlays do not work and are flawed
- Focuses more on lawsuits than people

Eric Bailey, a designer, depicts it best here.

![Graphic of a pyramid of people. At the top, where there are few people, are those who care about outcomes. Usually outcomes means profit. Below them are slightly more people who care about checking boxes. Boxes meaning compliance. Below them is a much larger group: people who care about solutions. And the group below that which is even larger consists of people who are actually affected by the solution.](https://pbs.twimg.com/media/E66gVYJXEAAOsDB?format=png&name=large)

## Who accessiBe is For and Not <a name="section-3"></a>

At this point, what do I know?

**1)** Does accessiBe help some people in the community? Seems so.

**2)** Does accessiBe help all people in the community? No.

**3)** Does it help some companies reach compliance? Apparently.

**4)** Can you reach compliance and not be fully accessible? Yes.

**5)** Is it more cost effective than skilling up your ICs? Debatable.

**6)** Is this a debated topic in the space? Yes. By users and professionals.

I suppose if you were a company, and companies want to make money, and you were aware that almost [98% of homepages on the internet](https://webaim.org/projects/million/#wcag) are inaccessible, then created a product that is affordable, low-effort and aimed it at businesses that are afraid to get sued, then I could see why you like the idea. I suppose you could also like the idea if you cared about equal access.

You could argue that it does improve the quality of life of (some) people in the disability community, that it's the fastest way to get more businesses to reach compliance and, thus, closer to being fully accessible. And I suppose if you were really tired of the lack of urgency on the part of businesses' you might prioritize the approach to the future that accessiBe promises.

(Trust me, I understand the anger at businesses' lack of accommodation.)

But I have a hard time believing that you would also truly care about the needs and lived experiences of people in the accessibility and disability community.

Especially if it continues to [hurt (some of) them](https://twitter.com/turtlecatpurrz/status/1415189018313072641?s=20). Or [worse](https://threadreaderapp.com/thread/1367543823665139712.html).

## That Which I Believe <a name="section-4"></a>

Overall, my concern is with what it encourages people to continue believing.

A turnkey solution like this suggests multiple mindsets on the part of businesses, which accessiBe targets in their money-making model:

- The ability to build accessible products is not worth investing in
- If we're not getting sued, we're good
- If we're compliant, we're good
- We don't build for "unicorns" but we'll pay to keep them happy
- Accessibility is not the responsibility of ICs
- The needs of users we're excluding is not our concern
- Only abled people are worth our resources
- HTML is not an important skill

I believe in a different methodology to achieve equal access on the web.

Instead, you should incorporate accessibility considerations into everything you do from beginning to end to provide equal access on the web, especially if you're a company that serves an "every" somebody. You may have heard, "shift left". Shift left with security considerations. Shift left with accessibility considerations. Include users with disabilities in your user testing and research. Create a feedback loop with them and maintain it. 

Do not consider accessibility as an item that can be de-prioritized below your other OKRs. Bake it into your roadmaps. Include accessibility in your acceptance criteria. Include it in your designs. Include it in your development's definition of done. Test with at _least_ one screen reader and tack on more as you become familiar with the others. Train your ICs.

All of them. Actually invest in everyone. [Including recruitment](https://twitter.com/CdnShieldCarla/status/1418987382339158018?s=20). 

If you haven't been doing this from the start and you've been around a while, I get it. I'm disappointed, but I get it. Maybe you lacked the funds. Maybe you lacked the foresight. But you know now. Make a plan to remediate over time the UX debt you have accumulated that is preventing users from benefiting from your products or services and commit to shifting left incrementally for new features. You could also fully commit on an entire team first.

Then make that commitment public and stick to it by providing [updates](https://spotify.design/article/better-in-black-rethinking-our-most-important-buttons).

Accessibility should be part of your standard of quality. Do not rely long-term on one person or one team to make this commitment. Everyone in the company should commit to the quality of their product and consequently the actual impact to the experiences of their users and the users they are excluding. If you cannot pay a consultancy to train your entire staff, start with an external speaker. Bring them to an event where your ICs are present. 

And then actually iterate. 

Because truly quality things take time, repeated effort, and education.

Not a single script tag in the body of your application.

![A meme about minimum viable products that jokes about how we're going to iterate after releasing the MVP. Except we're not.](https://i.ibb.co/hDH9hBH/mvp-meme.jpg)

Keep it candid,

Thuy 🙋🏻‍♀️