Accessibility New Year’s Resolutions — The Deadline for Implementing WCAG 2.1

Procrastination is firmly embedded in human nature. And the lack of a deadline makes it easier to procrastinate.

Step 1: You tell someone they have to do something they may not really want to do

Step 2: They *always* ask you when the deadline is

Step 3: When you tell them there isn’t one or that you aren’t certain, the thing you told them they have to do immediately plummets to the bottom of their “to do” list

WCAG 2.1 is unfortunately a little bit like that. The first WCAG update in 9 years included a total of 17 new guidelines, of which 12 fall into the A and AA categories. For me, the 12 new A / AA guidelines fall into 3 categories:

1. Mobile

2. Cognitive

3. Things W3C should have included in 2.0 but didn’t (minimum contrast for keyboard focus indicators for example)

How do you figure out what deadline to give teams that can be authoritatively backed up when there is no explicit deadline in WCAG 2.1 itself?

Disclaimer — this is not legal advice.

Companies who do business in Europe and want to continue selling to the EU public sector

There is a deadline, and it is as early as September 23, 2019 !!!

Member states implemented the requirements in EN 301 549 into national laws on September 2018 (i.e. last year). Multinational corporations, no matter where they are based in the world, will need to adhere to the EU 301 549 if they wish to do business with the EU public sector starting just a little over 8 months from this writing. Basically, that includes meeting WCAG 2.1 Level AA. And the EU hasn’t stopped there — another update to EN 301 549 is expected at the end of 2019 so keep your eyes out for that.

How big is the EU public sector? Big. Really really big. Between 13 and 25 % of people employed in the EU work for the public sector, depending on the country (France has the highest rate of employed people working in the public sector). This is compared to 16 % of the US.

One thing that is poorly understood in the EU directive is there is a difference between new and old digital properties (i.e. websites, documents, native apps). When an “old” digital property is updated, effectively it becomes “new” and should comply with the requirements for a “new” digital property.

Old

1. Documents created before September 2018 are exempt from EU 301 549
2. Intranet and Extranet sites created before Sept 2019 are exempt from EU 301 549
3. Multimedia published before Sept 2020 are exempt from EU 301 549

New

1. New public sector websites must conform by September 23, 2019
2. All public sector websites must conform by September 23, 2020 (even if it is an “old” website pre-dating September 23 2019 )
3. All public sector native apps must comply by June 23, 2021

If your company wants to sell to EU governments, they may be in for a nasty shock if they want to update something without bringing it into compliance with WCAG 2.1 Level AA after Sept 23, 2019.

Settlement agreements are including WCAG 2.1

Lainey Feingold announced the first public settlement agreement that included WCAG 2.1 towards the end of last year. In addition to that I have heard several anectodal reports of settlement agreements that are not public requiring adherence to WCAG 2.1.

Given that it only took 4 1/2 months after WCAG 2.1 became final to be incorporated as a standard to be measured against in a settlement agreement, that provides another data point towards making a deadline choice in your organization of “sooner, rather than later.” Because the lawyers who are representing accessibility plaintiffs have been measuring to WCAG 2.1 for more than two months already.

Most settlement agreements give an organization 18 months to come into compliance

A few have stretched very narrow parts of settlement agreements out to 24–36 months. However, those longer timelines generally occur when very UI heavy 3rd party code is involved. It appears that the concerned parties in cases are allowing for some longer times to make something like Postal Code validation or maps WCAG compliant when the inaccessible code is in a plugin that the defendant doesn’t have direct control over. In these situations, it is always possible that the defendant will be forced to enter into a new contract to get a WCAG compliant plugin, and the paperwork on that at a larger company can take a substantial amount of time. This is especially true if litigation is being contemplated or is already underway, because then more lawyers are involved, and that always tends to complicate things and slow them down.

18 months from June 5, 2018 (when the W3C recommendation for WCAG 2.1 became final) is December 5, 2019. 36 months is June 5, 2021.

Conclusion

There are four possible outcomes to the “deadline” for implementing WCAG 2.1 Level AA for any organization.

1. If you want to do business with the European government, the deadline and requirements are crystal clear and you should pick the one that applies to your organization depending on the type of digital property (website, mobile app, documents) and whether or not you plan on updating them
2. If you are currently negotiating a settlement agreement, your deadline is the EARLIER of a) the EU deadline (if it applies to you); or b) the date you agree to in the settlement agreement.
3. If neither 1 and 2 apply to you, December 5, 2019 seems to be a reasonable and justifiable internal deadline for WCAG 2.1 Level AA compliance when creating new digital properties or updating old ones.

If you don’t choose one of those 3, the fourth possible outcome is you end up getting sued by someone who effectively chooses the deadline for you. And remember, Haynes v. Hootersheld that being in a settlement agreement with one party and making progress towards accessibility does not eliminate the possibility of getting sued for the same inaccessibility by a second unrelated party.