{"id":1255,"date":"2023-06-25T19:58:40","date_gmt":"2023-06-25T18:58:40","guid":{"rendered":"https:\/\/cerovac.com\/a11y\/?p=1255"},"modified":"2023-06-27T22:44:02","modified_gmt":"2023-06-27T21:44:02","slug":"wcag-is-part-of-en-301-549-but-en-301-549-goes-way-beyond-wcag","status":"publish","type":"post","link":"https:\/\/cerovac.com\/a11y\/2023\/06\/wcag-is-part-of-en-301-549-but-en-301-549-goes-way-beyond-wcag\/","title":{"rendered":"WCAG is part of EN 301 549 but EN 301 549 goes way beyond WCAG"},"content":{"rendered":"\n

We often read that Web Accessibility Directive<\/a> refers to standard EN 301 549 that includes Web Content Accessibility Guidelines 2.1 on levels A and AA. But if we don’t actually check the whole EN 301 549 then we may think that it only includes WCAG and a bit more. The reality is that EC 301 549 includes a lot more of success criteria than WCAG as it needs to cover accessibility beyond web. It can also be applied to native mobile applications, documents and also other digital solutions.<\/p>\n\n\n\n

In this post I present where EN 301 549 actually goes beyond WCAG and which parts of it are applicable for web and which for mobile. I think this can be of value for people not familiar with EN 301 549 that do know at least basics of WCAG. WAD in Norway is a bit simpler than in the rest of the EU<\/a>, so I guess there are potentially a lot of people not aware of the whole EN 301 549 and I hope this post will shed some light on the whole standard.<\/p>\n\n\n\n

43 out of 76 EN 301 549 success criteria are applicable to web and 32 to mobile applications alone<\/h2>\n\n\n\n

After processing all 76 EN 301 549 (version 3.2.1) success criteria I got to these numbers.<\/p>\n\n\n\n

43 out of 76 success criteria that go beyond WCAG in EN 301 549 are applicable to websites and some of them also for mobile applications and other so called ICT technologies.<\/p>\n\n\n\n

It’s important to understand what does ICT stand for:<\/p>\n\n\n\n

\n

Information and Communication Technology (ICT) : technology, equipment, or interconnected system or subsystem
of equipment for which the principal function is the creation, conversion, duplication, automatic acquisition, storage,
analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission,
reception, or broadcast of data or information<\/p>\nDefinition of ICT from EN 301 549 (PDF, opens in new window)<\/a>.<\/cite><\/blockquote>\n\n\n\n

The standard also includes examples of ICT, so to be totally clear about it:<\/p>\n\n\n\n

\n

Note: Examples of ICT are web pages, electronic content, telecommunications products, computers and
ancillary equipment, software including mobile applications, information kiosks and transaction
machines, videos, IT services, and multifunction office machines which copy, scan, and fax documents.<\/p>\nA brief note from the standard that provides examples of ICT.<\/cite><\/blockquote>\n\n\n\n

So, as mentioned in the start EN 301 549 goes way beyond WCAG also in terms of technologies that are applicable. Besides webpages and mobile applications it can also be applied on hardware and that covers a lot more.<\/p>\n\n\n\n

But let’s focus back on the web and mobile.<\/p>\n\n\n\n

32 out of 76 success criteria that go beyond WCAG in EN 301 549 are applicable to mobile applications alone.<\/p>\n\n\n\n

So, we have 43 success criteria that go beyond WCAG for web and 32 that go beyond WCAG for native mobile applications. That gives us almost double success criteria in theory.<\/p>\n\n\n\n

Basically we can establish that EN 301 549 includes almost twice as much success criteria for web and mobile. A bit less for mobile, but still quite a lot. Of course not all success criteria are applicable for all webpages and mobile applications and in practical terms we don’t need to check all EN 301 549 on all webpages and mobile applications. But we still need to check if they apply before we can be certain.<\/p>\n\n\n\n

To conclude I also provide the data that I got the numbers from. It’s based on latest version of EN 301 549 at the time of writing (version 3.2.1), to be clear about it.<\/p>\n\n\n\n