JIS X 8341-3:2016

JIS X 8341-3:2016 is Japan’s national standard for the accessibility of web
content. It provides requirements and testing guidance intended to help
websites and web applications work for older people and people with
disabilities.

The standard is widely used by Japanese public organisations, accessibility
specialists, web-development teams and businesses seeking to improve digital
accessibility in Japan.

JIS X 8341-3 is a technical standard rather than a standalone law. Its legal,
contractual or procurement relevance depends on the organisation, service,
applicable government guidance and other Japanese disability-accessibility
obligations.

What is JIS X 8341-3?

The full title of the standard is:

JIS X 8341-3:2016 — Guidelines for older persons and persons with
disabilities: Information and communications equipment, software and
services — Part 3: Web content.

JIS stands for Japanese Industrial Standards. The X 8341 series addresses
accessibility considerations for information and communication technology.
Part 3 focuses specifically on web content.

Who is JIS X 8341-3 intended to support?

The standard is intended to improve access for users including:

• People who are blind.
• People with low vision.
• People who are deaf or hard of hearing.
• People with mobility or dexterity disabilities.
• People with cognitive or learning disabilities.
• People with speech disabilities.
• Older users experiencing changes in vision, hearing or motor control.
• People using assistive technologies or alternative input methods.

Is JIS X 8341-3 a law?

JIS X 8341-3 is a national technical standard. It does not automatically
impose the same legal duty on every website in Japan.

It can nevertheless become important through:

• Government accessibility policies.
• Public-sector procurement requirements.
• Contracts and tender specifications.
• Organisational accessibility policies.
• Reasonable-accommodation responsibilities.
• Customer or employee accessibility requests.

Organisations should distinguish between technical conformance with the
standard and compliance with a particular Japanese law or contract.

How did JIS X 8341-3 evolve?

Japan first published JIS X 8341-3 in 2004 to provide a national framework
for web-content accessibility.

The standard was revised in 2010 to align more closely with the Web Content
Accessibility Guidelines 2.0.

The current major edition is JIS X 8341-3:2016. It reorganised the standard
and aligned its accessibility requirements with ISO/IEC 40500:2012, which
corresponds to WCAG 2.0.

The publication of newer WCAG versions does not automatically change the
requirements of JIS X 8341-3:2016. Organisations should identify the exact
standard required by their policy, tender or contract while also considering
newer accessibility practices for new digital products.

JIS X 8341-3 and WCAG

JIS X 8341-3:2016 is closely aligned with WCAG 2.0. It uses the same
fundamental accessibility principles and equivalent success criteria.

The four principles are:

Learn more about
WCAG 2.0 accessibility requirements.

Conformance levels

JIS X 8341-3 uses three conformance levels corresponding to WCAG:

An organisation claiming Level AA conformance must satisfy all applicable
Level A and Level AA requirements within the declared scope.

What web content is covered?

JIS X 8341-3 can be applied to:

• Public websites.
• Corporate websites.
• E-commerce websites.
• Web applications.
• Online forms.
• Customer and employee portals.
• Multimedia content.
• Downloadable documents provided through websites.
• Mobile web experiences.
• Third-party components included in a web service.

The assessment scope should clearly identify the pages, processes,
templates and technologies being evaluated.

Perceivable web content

Users must be able to perceive essential information even when they cannot
see, hear or interpret the original presentation in the same way as other
users.

Important requirements include:

• Text alternatives for informative images.
• Captions for relevant video content.
• Alternatives for audio-only content.
• Semantic headings and page structure.
• Programmatic identification of form labels.
• Sufficient colour contrast.
• Content that does not rely only on colour.
• Text that can be enlarged without loss of essential information.

Operable interfaces

Users must be able to navigate and operate functionality without depending
exclusively on a mouse, touch gesture or visual interaction.

Relevant requirements include:

• Keyboard access to interactive controls.
• No keyboard traps.
• Logical focus order.
• Visible keyboard focus.
• Skip links or other methods for bypassing repeated content.
• Meaningful page titles.
• Descriptive headings and labels.
• Enough time to read and complete tasks.
• Protection against harmful flashing content.

Understandable content and interaction

Users should be able to understand the content and predict how the interface
will behave.

Important practices include:

• Declaring the page language.
• Using clear labels and instructions.
• Maintaining consistent navigation.
• Avoiding unexpected changes of context.
• Identifying form errors clearly.
• Providing suggestions for correcting errors.
• Allowing users to review important submissions.

Robust implementation

Content and controls should expose accurate information to browsers and
assistive technologies.

This includes:

• Using semantic HTML.
• Providing meaningful accessible names.
• Exposing correct roles and states.
• Associating labels and controls correctly.
• Avoiding duplicate identifiers where they break relationships.
• Keeping ARIA states synchronized with visible states.
• Testing compatibility with screen readers.

Native HTML controls should be preferred whenever they provide the required
semantics and keyboard behaviour.

Japanese language and content considerations

Technical conformance alone does not guarantee that Japanese content is easy
to understand.

Teams should also consider:

• Correct declaration of Japanese as the document language.
• Clear reading order for mixed Japanese and Latin text.
• Understandable labels and instructions.
• Appropriate explanation of abbreviations and specialist terminology.
• Readable text at enlarged sizes.
• Alternative text that reflects Japanese context and meaning.
• Screen-reader pronunciation of unusual names and terms.

JIS X 8341-3 conformance terminology

Japanese accessibility reports often distinguish between terms such as
“conforms,” “partially conforms” or “aims to conform.”

These terms should not be used casually. The organisation should follow the
applicable Japanese testing and publication guidance and clearly state:

• The standard and edition used.
• The target conformance level.
• The pages or processes included.
• The technologies relied upon.
• The testing method.
• The date of the assessment.
• Any excluded content.
• Known accessibility limitations.

Accessibility policies and test results

Japanese public-sector guidance commonly encourages organisations to
publish information about their accessibility goals and assessment results.

A useful accessibility page may include:

• An accessibility policy.
• The target JIS conformance level.
• The assessment scope.
• A list of pages tested.
• The testing method and date.
• Known limitations.
• A plan for improvement.
• A contact method for reporting barriers.

Claims should be based on current evidence and updated after significant
website changes.

Public-sector web accessibility in Japan

Japanese national and local government organisations use public-sector web
accessibility guidance that references JIS X 8341-3.

Public organisations should manage accessibility through:

• Published accessibility policies.
• Defined conformance targets.
• Periodic accessibility testing.
• Publication of assessment results.
• Training for content authors and developers.
• Correction of identified barriers.
• Ongoing monitoring after website changes.

Private businesses and reasonable accommodation

Japan’s Act for Eliminating Discrimination against Persons with
Disabilities prohibits unjust discriminatory treatment.

Since April 1, 2024, private businesses are also required to provide
reasonable accommodation when requested, unless doing so would create an
excessive burden.

In a digital context, reasonable accommodation may include:

• Providing information in an accessible format.
• Correcting an inaccessible form.
• Offering an accessible alternative to a digital process.
• Providing captions or a transcript.
• Supporting keyboard operation.
• Assisting a user who cannot complete an inaccessible transaction.

Building and maintaining websites in line with JIS X 8341-3 can help reduce
the need for individual adjustments by preventing barriers before users
encounter them.

JIS X 8341-3 and newer WCAG versions

JIS X 8341-3:2016 is aligned with WCAG 2.0. Since its publication, W3C has
released WCAG 2.1 and WCAG 2.2.

Newer WCAG versions include additional requirements concerning:

• Mobile orientation.
• Content reflow.
• Non-text contrast.
• Pointer gestures.
• Status messages.
• Focus visibility and obstruction.
• Dragging movements.
• Target size.
• Accessible authentication.

An organisation may need to assess formally against JIS X 8341-3:2016 while
also adopting newer WCAG criteria as part of its product-quality and
accessibility process.

Read more about
WCAG 2.1 accessibility guidelines.

Common JIS accessibility barriers

• Japanese images of text without equivalent real text.
• Navigation that cannot be operated by keyboard.
• Form fields without accessible labels.
• Error messages communicated only through colour.
• Insufficient contrast in text or controls.
• Heading levels that do not represent page structure.
• Videos without captions.
• PDF files without accessible structure.
• Buttons without meaningful accessible names.
• Dialogs with incorrect focus management.
• Pages that lose content when text is enlarged.
• Third-party payment or booking tools that block assistive technologies.

How to evaluate a website

A reliable JIS assessment should combine several methods.

Automated testing

Automated tools can identify repeatable technical issues such as missing
labels, some contrast failures, invalid markup and structural problems.

Manual testing

Human review is required for alternative-text quality, heading meaning,
keyboard behaviour, focus management and content clarity.

Assistive-technology testing

Important journeys should be tested using Japanese screen-reader
configurations and other relevant assistive technologies.

Complete journey testing

Testing should confirm that users can complete registration, purchasing,
booking, search, authentication and support processes from beginning to end.

How to build a JIS accessibility workflow

1. Define the target:
   identify the JIS edition, conformance level and organisational policy.
2. Define the scope:
   list templates, pages, components, documents and complete user journeys.
3. Run automated checks:
   identify repeated technical findings across representative content.
4. Perform manual testing:
   review keyboard use, focus, content meaning and complex components.
5. Test assistive technologies:
   verify important journeys with appropriate Japanese configurations.
6. Document findings:
   record user impact, evidence and applicable criteria.
7. Assign remediation:
   route issues to development, design, content, product or vendors.
8. Verify corrections:
   retest fixes before closing findings.
9. Publish accurate results:
   describe the target, scope, method and current status.
10. Monitor future changes:
    retest after releases, redesigns and content updates.

Procurement and vendors

Organisations purchasing websites, software or digital services should
include accessibility before selecting a vendor.

Procurement requirements can address:

• The required JIS version and conformance level.
• The pages and functions included in testing.
• Manual and assistive-technology testing.
• Accessibility documentation.
• Disclosure of known limitations.
• Remediation timelines.
• Acceptance testing.
• Responsibility after future updates.

A generic claim that a product is accessible should not replace current
evidence and functional testing.

Automated testing is not enough

Automated scanning cannot establish complete JIS X 8341-3 conformance.

Human judgement is needed to determine:

• Whether Japanese alternative text communicates the correct meaning.
• Whether headings describe the content accurately.
• Whether focus order is logical.
• Whether a screen-reader user can complete the task.
• Whether form errors are understandable.
• Whether captions accurately represent the audio.
• Whether an alternative process provides equivalent access.

Maintaining accessibility

A conforming website can develop new barriers after:

• A redesign.
• A content-management-system update.
• A new form or page template.
• A third-party integration.
• A document upload.
• A change to navigation.
• A new mobile layout.

Accessibility should therefore be integrated into design, development,
content publishing, quality assurance, procurement and release management.

How Pluro supports JIS accessibility workflows

Pluro is an accessibility workflow platform that helps organisations manage
findings from detection through verified remediation.

Teams can use Pluro to:

• Centralise automated and manual findings.
• Capture keyboard and behavioural evidence.
• Connect findings to accessibility requirements.
• Assign responsibility to design, development, content or QA.
• Provide remediation guidance.
• Track correction status.
• Verify completed fixes.
• Maintain an accessibility history.
• Monitor websites after future changes.

Pluro does not automatically certify a website against JIS X 8341-3.
Formal conformance requires an appropriately scoped assessment, current
evidence and testing against the applicable Japanese requirements.

JIS X 8341-3 checklist

• Use the complete name JIS X 8341-3:2016.
• Define the target level and assessment scope.
• Provide alternatives for images, audio and video.
• Use semantic headings and page structure.
• Make all essential functionality keyboard accessible.
• Provide visible focus and logical focus order.
• Maintain sufficient colour contrast.
• Provide accessible forms and error messages.
• Review Japanese-language content and pronunciation.
• Test with relevant assistive technologies.
• Include complete user journeys.
• Document known limitations.
• Verify corrections before closing findings.
• Publish accurate accessibility results.
• Retest after website changes.

Important notice

This page provides general information and does not constitute legal advice
or a formal JIS conformance assessment. Requirements depend on the
organisation, applicable law, procurement process, contract, scope and
version of the standard being used.

Review the official

WAIC information about JIS X 8341-3:2016
.

See how Pluro manages accessibility workflows
or
start a 14-day free trial
with no credit card required.