Why I’m not worried about WCAG 2.1

Laptop with Code

WCAG 2.0 - the 0 has been crossed out in red and a 1 has been written in to replace it.Hi everyone, Richard here, Founder and CEO of AccessibiliBuddy. If you’ve been following accessibility news, you might have seen that the new Web Content Accessibility Guidelines (WCAG) 2.1 guidelines have been published and are expected to be ratified in June.

Following this announcement, here’s quick FAQ on what questions I’ve been getting from clients and other members of the web development community:

  1. Are you worried about the learning curve and retraining your team?
    1. No. We’ve already reviewed the updates and they are already covered in our current practices.
  2. At least you’ll be making more money from revisions for your existing clients.
    1. Nope, see the answer to #1.
  3. Do you think people will be upset if they paid for work that isn’t required under 2.1?
    1. Nope, there’s no such thing. 2.1 is complimentary to 2.0 and doesn’t exclude anything.
  4. Does anything worry you about the 2.1 rollout?
    1. Yes. Opportunists using scare tactics.

#4 is probably what worries me the most about this update. If you search ‘Accessibility Lawsuits‘, you’ll notice a few paid ads in the search results to agencies trying to convince you that you’re going to sued if your site isn’t accessible. While thisĀ could happen, and has been generating quite a bit of news over the last couple of years, it’s not THE reason to make your site accessible. Aside from it not being ‘fair’ to not have accessible websites, take a look at the stats on our About page and you’ll realize how large of market share you’re probably missing out on by not having accessible content on your site. It boils down to this:

It’s ROI positive for you to make your site Accessible. End of story.