Repository navigation
Homegrown partial conformance #5416
Replies: 2 comments 6 replies
|
I'll admit that you lost me somewhat there with the "people just choose an arbitrary subset of SCs". that's ... not something I've ever come across. you pick a WCAG level (generally AA), and you test all relevant SCs for that level (so for AA, you test all A and AA SCs). EN 301 549 adopts/references/incorporates WCAG 2.x AA. I'm further confused by your mention of ATAG. are you saying that, say, instead of an actual website, people are testing the tools used to create/publish it? None of this sounds like it's the basis for an actual WCAG conformance claim, nor a basis to claim compliance with EN 301 549. |
|
Being someone who works for the team that implements the WAD for the Dutch government, I can't say I recognize any of your remarks, @kreukelzone. We have a clear understanding of what we implement: EN 301 549 in full, of which some requirements are currently a bit more difficult to test, which is something we try to improve in close relationship with IAAP for all EU member states (and beyond). |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I’m kindly requesting an official working group response regarding section 5 Conformance.
Informative: In the Netherlands, in the context of the WAD, the local law explicitly mandates using EN 301 549. There is still no surveillance, and the general consensus appears to be that nobody knows what that means, and what to do, so we use WCAG-EM instead. So far, so funny.
In the majority of cases, however, no coherent conformance level of WCAG is actually used for WCAG audits. To save money and separate platforms and implementations, there are frequently
The idea is to choose and use an arbitrary selection of SCs in both cases. Again, those are not chosen based on a conformance level. Or any interdependence. Or any sort of collaboration. Or documentation. For partial content audits I’ve done so far, I’ve briefly looked into existing partial technical audits, which doesn’t really save any time or money, pragmatically speaking, and by and large, they either
a) are based on another, usually unspecified version or configuration, or
b) are just really sloppy and are missing a plethora of errors that I cannot report because those are “technical” SCs (for my employer, that might even be a completely unrelated selection for the technical audit).
So usually two parties are testing complete pages and processes, separated (or not) by an arbitrary subset of SCs, not based on conformance level, usually without information of platform version or configuration, and somehow this is all coming together as WCAG conformance. For the government party that might answer any questions. But is not actually tasked with surveillance. Because.
I appreciate that this question should also be directed to the EC, but I would still like to learn how this is supposed to at least lead to any sort of WCAG conformance claim as a bare minimum.
All reactions