W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2016

WCAG Next Possible Models

From: Makoto UEKI - Infoaxia, Inc. <makoto.ueki@gmail.com>
Date: Tue, 26 Apr 2016 01:10:42 +0900
Message-ID: <CAF9hGuZaoEtsLBXSJpdiJLOhruwKJNQO86855Fca3PYo4yUbrA@mail.gmail.com>
To: w3c-wai-ig@w3.org
First of all, having "WCAG 2.1", "WCAG 2.2" or whatever will be
acceptable in Japan as long as "WCAG 2.0" won't be modified. Secondly,
I prefer the "Option 2.2". The "Option 3.1" is also good.

In Japan, we have the national standard "JIS X 8341-3". It was updated
in March 2016 and became identical with "ISO/IEC 40500:2012"(= "WCAG
2.0"). It is safe to say that the "JIS X 8341-3:2016" is the Japanese
translation of "WCAG 2.0".

In general, JIS standards need to be identical with ISO/IEC standards.
For example, if "ISO/IEC 40500" will be updated in the future, "JIS X
8341-3" will be updated as well.If "ISO/IEC 40500" won't be updated,
then "JIS X 8341-3" won't be updated as well. Even if "WCAG 2.1" is
published, we'll keep using "WCAG 2.0" until "WCAG 2.1" is approved as
the new version of "ISO/IEC 40500".

So in Japan this would be acceptable only if "WCAG 2.1" is "WCAG 2.0(=
"JIS X 8341-3:2016") + some additional SC". We'll be able to make a
conformance claim by using both "JIS X 8341-3" and "WCAG 2.1" if a
website also meets the new SC in "WCAG 2.1".

In any options, the worst case scenario for Japan would be that "WCAG
2.1" will modify a part of the existing success criteria in "WCAG
2.0". In such case, it can be possible that conforming to "WCAG 2.1"
doesn't mean conforming to "WCAG 2.0(= "JIS X 8341-3:2016")" at the
same time. This would cause major problems in Japan

One more thing. We enforced a new law from April 1st 2016. It's the
first disability discrimination act in Japan. However the law and any
other related docuents don't refer to "WCAG 2.0" or any other
guidelines including "JIS X 8341-3"! So the version number of WCAG
won't cause any problem in Japan.


Makoto Ueki - Infoaxia, Inc. Tokyo, Japan
Received on Monday, 25 April 2016 16:11:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 April 2016 16:11:12 UTC