CARLOS LASTRES CONTACT

August 19, 2026968 wordsaccessibility · regulation · websites

What to Do Now About the JIS X 8341-3 Revision

Japan's web accessibility standard is being revised toward WCAG 2.2. That adds 26 success criteria, 11 of them at level AA. In a 2026 government survey, 21.7% of public bodies knew and were acting on it. What to do while it is still cheap.

Japan's web accessibility standard, JIS X 8341-3, is being revised.

ISO/IEC 40500 was revised in September 2025. In response, on 30 October 2025, the Web Accessibility Infrastructure Committee convened a drafting committee, with the stated policy of making the new JIS a conforming standard to ISO/IEC 40500:2025.

In practice: the current JIS is technically equivalent to WCAG 2.0. The revised one moves to WCAG 2.2.

26 new criteria, 11 of them at level AA

The committee's published material breaks down what gets added.

  • From WCAG 2.1: 5 at level A, 7 at AA, 5 at AAA
  • From WCAG 2.2: 2 at level A, 4 at AA, 3 at AAA
  • Total: 7 at level A, 11 at AA, 8 at AAA

One criterion, 4.1.1 Parsing, is removed in WCAG 2.2.

The eleven at level AA are the ones to look at, because Japanese public procurement and published accessibility policies generally point at level AA. A site that conforms to the current JIS does not automatically conform to the revised one.

The new AA criteria cover reflow, text spacing, contrast on non text elements, focus that stays visible, an alternative to dragging, and a minimum target size, along with screen orientation, identifying input purpose, content shown on hover or focus, and status messages. The level A additions include keeping help in a consistent place and not making people re enter information they already gave you.

None of that is specialist. It is ordinary interface work.

How ready the public sector is

The Ministry of Internal Affairs and Communications runs an annual survey, and the March 2026 summary shows the state of preparation. 2,092 organisations contacted, 1,058 responses, a 50.6% response rate.

21.7% know the revision is coming and are doing something about it.

44.9% know and have not started. 33.4% had not heard. That is 78.3% meeting this as a surprise or a scramble.

Other numbers from the same survey give useful context. 84.9% say they work on web accessibility. 52.1% have published an accessibility policy. 56.8% have run a conformance test against JIS X 8341-3:2016. 14.6% publish the result of the ministry's own evaluation worksheet.

Four different meanings living inside one word. Companies are no different.

Does this apply to private companies

Not as a direct legal obligation. What the disability discrimination act requires of private businesses is reasonable accommodation, which is not the same as a conformance level.

But standards travel.

Public procurement will start requiring the revised JIS. Agencies with government clients will build to it. Japanese CMS products will follow. Within a few years it becomes the default for what a competent Japanese web project looks like. The committee has already stated that the revised annex JA is being organised for private sector use and not only public bodies.

And separately, the European Accessibility Act has applied since June 2025. For any Japanese company selling digital products or services into the EU, that is already a requirement, and it points at the same WCAG criteria.

You can treat these as two compliance projects arriving from two directions. Or you can notice that they converge on one technical standard and do the work once.

What to do, in order

The revision has not been published and the committee is still working. That makes now the cheapest possible time to prepare, because nothing is mandatory and nothing is late.

The committee says it plainly: conformance to JIS X 8341-3:2016 is the foundation, and the criteria added in WCAG 2.1 and 2.2, particularly at levels A and AA, can be adopted ahead of time. It also says the work needs a plan with budget and hours attached. That second half is what most organisations skip.

  1. If you have never run the current JIS test, run it. Among public bodies, 43.2% have not. Until you do, everything else is guesswork.
  2. Check your site by hand against the new level A and AA criteria. Automated tools catch some of it. Focus visibility and target size need a real device and a real hand.
  3. Put it in your next vendor contract as a requirement, not as a remediation project after launch. Retrofitting is the expensive path and it is the one almost everyone takes.
  4. Publish the result. 14.6% do. A published evaluation admitting partial conformance is worth more than a conformance claim nobody has verified.

About the budget argument

The survey asked organisations that are not doing this work why not, and the answers are instructive. 65.6% said people and budget are limited so they cannot invest enough. 59.4% said they have nobody with the expertise.

The option saying it is not worth doing is effectively absent.

So persuasion is not what is missing. What is missing is material a person can take into a budget meeting. In the same survey, the most valued part of the ministry's guideline, at 76.2%, was the section explaining necessity and legal basis. People want the ammunition for an argument they are already having.

The revised JIS is going to be the strongest such ammunition available for several years. Nothing moves internal priorities like an external requirement with a date on it.

Related reading: how far accessibility work should actually go and the EU requirement.

Sources

READ NEXT

If You Sell into the EU, Accessibility Became an Export Requirement in June 2025 Why Splitting Brand and Content Across Two Suppliers Stops Working Getting ChatGPT and Claude to Describe Your Company Correctly
← All insights