Japan: JIS X 8341-3 & Reasonable Accommodation

What the law is

JIS X 8341-3 is older than people expect. Japan first published it in June 2004, which makes it one of the oldest national web accessibility standards anywhere. It was revised in August 2010 to line up with WCAG 2.0, and revised again in March 2016 to match ISO/IEC 40500:2012, which is WCAG 2.0 wearing an international standard's number. The Japanese committee that maintains the translations puts the outcome plainly. WCAG 2.0, ISO/IEC 40500:2012, and JIS X 8341-3:2016 all carry technically identical content. Meet one and you have met the other two.

A revision is coming, and Japan has already published how big it will be. JIS X 8341-3:2016 carries 61 success criteria. If the standard is revised on the basis of WCAG 2.2, the next JIS X 8341-3 will carry 86, and the Level A and AA subset you have to satisfy for AA conformance rises from 38 to 55. The engine behind that revision has already turned over, because WCAG 2.2 was approved as ISO/IEC 40500:2025 on October 21, 2025, cancelling and replacing the 2012 edition the current JIS tracks. What nobody will give you is a date. Every source we read, the ministry's own guideline included, says the timing is undetermined.

The legal half comes from the Act on the Promotion of the Elimination of Discrimination on the Grounds of Disability, Act No. 65 of 2013, in force since April 1, 2016. Article 7 binds administrative organs and Article 8 binds business operators in mirrored language, and each carries two limbs. The first bans unfair discriminatory treatment on the ground of disability. The second requires reasonable accommodation where a person with a disability has actually expressed that a social barrier needs removing, and where the burden of removing it is not excessive. The accommodation gets matched to that person's sex, age, and condition. Act No. 56 of 2021 turned that second limb from a best-efforts duty into a legal one for private business, effective April 1, 2024. Watch the trigger, because it differs from the American model. Japan's duty is request-driven. It starts when somebody tells you.

This applies to you if…

• You are a business operator in Japan, and the Act draws that circle wide. It covers you whether you are for-profit or non-profit, incorporated or an individual, so companies, shops, and volunteer groups are all inside it. There is no small-business exemption anywhere in this law.
• You are a Japanese public body, meaning a national agency, a local public body, or an incorporated administrative agency at either level. The Ministry of Internal Affairs and Communications writes a 183-page operational guideline aimed squarely at you, and it is far more directive than the word guideline suggests.
• A customer tells you they cannot use your service as it stands. That expression of intent is what starts the duty running. From that moment you either provide a reasonable alternative or fix the underlying barrier, unless you can show the burden of doing so would be excessive.
• You are asking about your own staff rather than your customers, in which case this is the wrong law. Article 13 sends measures an employer takes toward its own workers to the Act on Employment Promotion of Persons with Disabilities, Act No. 123 of 1960. Your internal HR system and your customer-facing checkout answer to two different statutes.

What it technically requires

• Conform to JIS X 8341-3:2016 at Level AA, which is WCAG 2.0 AA under a Japanese number. No fixed conformance deadline exists for private-sector websites here, unlike several other laws on this site. Testing against WCAG 2.2 AA instead covers the current requirement with margin, apart from success criterion 4.1.1 Parsing, which WCAG 2.2 dropped and JIS still carries. That advice is not only ours. The ministry tells its own public bodies to build new sites on WCAG 2.2 success criteria as far as possible, looking ahead to the coming JIS revision.
• If you are a public body, the ministry guideline sets out a full cycle rather than a one-off target. Start with your official homepage, its smartphone version included. A site not yet at Level AA has to promptly draw up and publish an accessibility policy, then reach Level AA, which the guideline defines as running the test and publishing the result. A site being built from scratch needs its accessibility policy written before construction starts and Level AA reached at build time. Then once a year, every body assesses itself against the web accessibility checklist and publishes the outcome before the fiscal year ends.
• Test the way the ministry says to test, because it wrote the method down. Select 10 pages that represent the site, taking care not to miss the ones that matter most, and the guideline names emergency disaster information and pages used heavily by older and disabled people as examples. Add 30 pages chosen at random. That is 40 pages tested. The guideline then names four ways organisations get this wrong. Fixing only the sampled pages and then declaring Level AA. Commissioning the annual test from the same vendor that built and maintains the site, so objectivity is not secured. Running automated tool checks alone with no human visual verification, since check tools cannot test everything. And running the test at the very end of the fiscal year with no time left to act on what it found. The ministry's own recommendation is a third party, chosen for expertise and independence, asked for specific remediation methods rather than a list of results.
• Write the accessibility policy to the prescribed contents, because Japan specifies them. Five items are required. The site's name and domain, the deadline for hitting the target, and the target conformance level along with the degree of conformance actually reached. Then any exceptions, naming the specific success criteria not met and the scope of any content left out of scope. And then any extra criteria you adopted above your chosen level. Recommended items add the responsible department, the problems you know about and how you are thinking about them, and a link to the published test results. Japan also fixes the vocabulary you may use, separating full conformance from partial conformance, and it explicitly advises against setting Level AAA as a whole-site target.
• Answer accommodation requests as they arrive, and have a way to receive them. The duty is not anticipatory, so nothing obliges you to guess in advance what any particular customer will need. What it does oblige you to do is respond when they say it, which in practice means a route into your business that a blind customer can actually use to tell you the checkout is broken.

All roads lead to WCAG. Start with Level AA, the legal standard or the full 55-rule library. Unfamiliar term along the way? The A to Z glossary decodes it.

How it is enforced

Article 12 is the enforcement chain, and it is narrower than it first looks. A competent minister may require a report from a business operator, or give advice, guidance, or recommendations, but only on matters set out in the response guidelines for that sector. Those guidelines flow from the Basic Policy the Cabinet adopted on March 14, 2023, and each ministry writes its own. So the document your business is actually measured against is your industry's response guideline rather than the Act itself. Article 21 makes the competent minister whichever one has jurisdiction over your business. Article 22 lets those powers be handed down to the heads of local public bodies. So a demand for a report can arrive from a prefecture or a city rather than from Tokyo.

There is a fine, and what it attaches to is the part worth getting right. Article 26 sets a penalty of up to 200,000 yen for failing to make a report the minister demanded under Article 12, or for filing a false one. It is an administrative fine rather than a criminal one, so it carries no criminal record. And no fine attaches to having an inaccessible website. The fine attaches to ignoring the minister who asks you about it.

The ministry also runs a leaderboard. It publishes the ten organisations with the smallest share of pages carrying Level A and AA problems, as reference material for every other public body. A national government publishing a ranking of its own agencies on accessibility applies a kind of pressure no fine schedule delivers, and it works on suppliers too, because those rankings are built from sites that somebody was paid to build.

Before any of that there is a conversation. Articles 17 to 20 set up regional coordination councils to handle consultations and head off disputes. Article 14 then puts a duty on national and local government to respond properly to consultations about disability discrimination, and to build the people and systems that resolve them. So the realistic path in Japan starts with somebody raising it, not with a claim form. Which is why an accessible site pays here. Since April 2024 the question is no longer whether you owe the accommodation. It is why the person had to ask for it.

Key dates

1. 2016JIS X 8341-3:2016 aligns fully with WCAG 2.0
2. Apr 1, 2024Reasonable accommodation becomes mandatory for private businesses

Primary sources

• Japan Digital Agency: accessibility
• Cabinet Office: Elimination of Discrimination Act

Other laws

• United StatesADAWCAG 2.1 AA (Title II rule, de facto standard in Title III cases)
• European UnionEAAAnnex I, EN 301 549 (includes WCAG 2.1 AA)
• United States (federal)Section 508WCAG 2.0 AA (incorporated by the 2017 refresh)
• United States (aviation)ACAAWCAG 2.0 AA, named in 14 CFR 382.43
• United States (telecoms)Section 255WCAG 2.0 A and AA, through the Revised 255 Guidelines
• European UnionWeb Accessibility DirectiveEN 301 549 V3.2.1, which carries WCAG 2.1 AA
• California, USUnruh ActWCAG 2.1 AA (what courts and settlements expect)
• Manitoba, CanadaManitoba AMAWCAG 2.1 AA (Accessible Information and Communication Standard)
• ArgentinaArgentina Ley 26.653WCAG 2.0, referenced by the law
• ChinaChina PPD LawNo WCAG version named in the law itself
• ColombiaColombia guidelinesWCAG 2.1
• Hong KongHong Kong guidelinesWCAG 2.0
• TaiwanTaiwan 110.07WCAG 2.1 derivative
• Saudi ArabiaSaudi SWAWCAG 2.1 AA
• QatarQatar Law No. 2WCAG 2.1 AA
• United Arab EmiratesUAE requirementsWCAG 2.1 AA
• Ontario, CanadaAODAWCAG 2.0 AA (excl. 1.2.4 & 1.2.5)
• United KingdomUK Equality ActWCAG A and AA, named in PSBAR regulation 9 as amended from time to time
• United States (healthcare)HHS Section 504WCAG 2.1 AA (2024 final rule)
• New York, USNew York HRLWCAG 2.1 AA (what complaints and settlements cite)
• Colorado, USColorado HB21-1110WCAG 2.1 AA (written into state standards)
• Canada (federal)Accessible Canada ActCAN/ASC-EN 301 549 → WCAG 2.1 AA
• NorwayNorway (Universal Design)WCAG 2.0 AA private / 2.1 AA public
• IsraelIsrael IS 5568WCAG 2.0 AA (via IS 5568)
• AustraliaAustralia DDAWCAG 2.2 AA (AHRC 2025 guidance)
• GermanyGermany BFSGEN 301 549 → WCAG 2.1 AA
• FranceFrance RGAARGAA (WCAG-based) / EN 301 549
• ItalyItaly Stanca ActWCAG 2.1 AA (AgID guidelines)
• SpainSpain RD 1112/2018UNE-EN 301549, which incorporates WCAG 2.1 AA
• NetherlandsNetherlandsEN 301 549, which incorporates WCAG 2.1 AA
• IrelandIrelandEN 301 549, which incorporates WCAG 2.1 AA
• BrazilBrazil LBIeMAG, aligned with WCAG, plus ABNT NBR 17225 for web content
• IndiaIndia RPwDGIGW 3.0, which references WCAG 2.1
• New ZealandNew ZealandWCAG 2.2 Level AA
• South KoreaSouth KoreaKWCAG 2.2, a national standard aligned with WCAG
• SwitzerlandSwitzerland BehiGeCH-0059, which references WCAG 2.1 AA
• DenmarkDenmarkEN 301 549, which incorporates WCAG 2.1 AA