This page has been translated using TexTra by NICT. Please note that the translation may not be completely accurate.If you find any mistranslations, we appreciate your feedback on the "Request form for improving the automatic translation ".

Web Accessibility Validation Results (2025)

A test based on JIS X 8341-3:2016 is conducted and the results are published.
The notation of "conformance" and "partial conformance" used in the results of this study is in accordance with the notation defined in " Web Content JIS X 8341-3:2016 Conformance Notation Guidelines - April 2021 " by the Web Accessibility Infrastructure Committee of the Info-communications Access Council.

Test results for the target conformance level criteria

ItemContents
Date of representationMarch 31, 2026
Standard number and revision year of the standardJIS X 8341-3:2016
Compliance level metPartially compliant with A
Brief description of the target Web pagehttps://www.digital.go.jp/ All pages below
List of Dependent TechnologiesHTML, CSS, JavaScript, PDF
Check tool used for the testNu Html Checker, Adobe Acrobat Pro, axe-core
Operating systems, user agents, and assistive technologies used to verify the contentWindows 11 / Google Chrome / NVDA, Windows 11 / Adobe Acrobat Reader / NVDA, iOS26.3 / Safari / VoiceOver
Method of selecting web pages to be testedSelection of 18 representative web pages for a set of web pages (web pages: 17 pages, PDF:1 file), 39 pages by random sampling (web pages: 30 pages, PDF:9 files)
Web page on which the study was conductedList of Web Accessibility Verification Results Test Pages
Success Criteria ChecklistSuccess Criteria Checklist
Duration of the studyMarch 9 to March 26, 2026
Additional steps beyond the success criteria to improve accessibilityPlace a "Go to Body" link at the top of each page

Success Criteria Checklist

  • In the "Apply" column, "○" indicates that the criterion is applicable, and "-" indicates that it is not applicable.
  • In the "Result" column, "○" indicates that the criterion is met, and "×" indicates that it is not met.
  • See the Glossary of External Links in the Web Content Accessibility Guidelines (WCAG) 2.0 (Japanese translation) for terms used in the Success Criteria.
Success Criteria Checklist
No.Achievement standardConformance levelApplyResult:Notes
1.1.1Non-Text ContentAYes×Pages and PDF Files Found to Not Have Image Alt Text
1.2.1Audio only and video only (prerecorded)A-YesNo such content
1.2.2Captions (pre-recorded)AYes×Missing captions for some video content
1.2.3Audio description or media alternative content (pre-recorded)AYes×In some video contents, neither audio description nor transcribed text is provided.
1.2.4Caption (Live)AA-YesNo such content
1.2.5Audio Description (Prerecorded)AAYes×Some video contents do not have audio descriptions.
1.3.1Information and RelationshipsAYes×Web Pesio and PDF files with issues with headings and listings were identified. Web pages with issues with table captions and strong element usage were identified.
1.3.2Meaningful orderAYes×Some PDF Files Are Untagged and Do Not Have a Reading Order
1.3.3Sensory characteristicsA-Yes
1.4.1Using ColorsAYes×Web pages that provide color-only information in dashboards and video slides identified
1.4.2Controlling Your VoiceAYesYes
1.4.3Contrast (lowest level)AAYes×Web pages with missing contrast ratios were identified on slides within the video
1.4.4Resize textAAYesYes
1.4.5Character imageAA-YesNo such content
2.1.1Keyboard operationAYesYes
2.1.2No Keyboard TrapAYesYes
2.2.1Adjustable timingA-YesNo such content
2.2.2Pausing, Stopping, and HidingA-YesNo such content
2.3.1Three flashes of light or less than thresholdA-YesNo such content
2.4.1Block skipAYesYes
2.4.2Page TitleAYes×A PDF file without a title was found.
2.4.3Focus OrderAYesYes
2.4.4Purpose of the link (in context)AYes×Found pages with links whose destination could not be predicted from the link text or surrounding context
2.4.5More than one wayAAYesYes
2.4.6Headings and LabelsAAYesYes
2.4.7Focus VisualizationAAYesYes
3.1.1Page LanguageAYes×A PDF file for which the language setting has not been made is identified.
3.1.2Part of a languageAAYes×On some English pages, there are Japanese channel names in YouTube, but it was confirmed that they cannot be interpreted by the program.
3.2.1On FocusA-YesNo such content
3.2.2On inputA-YesNo such content
3.2.3Consistent navigationAAYesYes
3.2.4Consistent DistinguishabilityAAYesYes
3.3.1Identifying ErrorsAYesYes
3.3.2Label or DescriptionAYesYes
3.3.3Error Correction SuggestionsAAYesYes
3.3.4Error Avoidance (Legal, Financial & Data)AA-YesNo such content
4.1.1Syntactic analysisAYesYes
4.1.2Name, role and valueAYesYes

Challenges identified by the study and directions for their resolution

As a result of the tests, we are aware of the following issues and will continue to work to resolve each of them.

Issues found in web pages (HTML)

  • Web pages were identified where images were not properly labeled with alternative text (Success Criterion 1.1.1 Non-Text Content)
  • Video content without subtitles, audio descriptions, or transcribed text was found (Success Criterion 1.2.2 Captions (prerecorded), 1.2.3 Audio descriptions or media alternative content (prerecorded), 1.2.5 Audio descriptions (prerecorded))
  • Web pages were identified where headings or lists were not marked up as headings or lists (Criterion 1.3.1 Information and Relationships)
  • Dashboards and video slides relied solely on color to provide information (Success Criterion 1.4.1, Use of Color)
  • Some slides in the video were found to have insufficient contrast ratios between the text and background colors (Success Criterion 1.4.3 Contrast (minimum))
  • A link was identified that could not be predicted from the link text or surrounding context (Criterion 2.4.4 Link Purpose (In Context))

In order to resolve the above issues, we will promptly check the accessibility of the website before and after updating it. We will also revise components as necessary.

Video content issues for English-language pages

  • On a page that features YouTube video, Japanese characters in the channel name or video title are not interpreted by screen readers or other programs (Requirement 3.1.2, Partial Language)

In order to solve the above problems, we will consider countermeasures from both technical and operational aspects.

Issues found in the PDF file

  • PDF files were identified that were not properly labeled with alternate text for images (Success Criterion 1.1.1 Non-Text Content)
  • PDF files with unstructured headings, tables, and lists were identified (Criterion 1.3.1 Information and Relationships)
  • PDF files that were not tagged and had no reading order set were verified (Success 1.3.2 Meaningful Order)
  • Checked Untitled PDF Files (Success Criterion 2.4.2 Page Title)
  • PDF Files Without Language Settings Identified (Success Criterion: Language on page 3.1.1)

Overview of accessibility by document type

Proceedings, minutes, and meeting materials

The lack of tagging, language settings, and file titles makes it difficult to use with screen readers.

Efforts to Improve Accessibility
  • When publishing in PDF format, create proceedings, minutes, and meeting materials that can be read by a screen reader.
  • If PDF is not necessary, prepare a web page.
  • Further Efforts
    • Add headings to help you understand a long passage of text more accurately and move through a document more easily
    • In the case of a long document such as minutes of a meeting, a summary should be provided at the beginning of the document to facilitate understanding of the entire document.
Presentation material
  • Lack of tagging, language settings, or file titles makes it difficult to use with screen readers
  • You can't understand a given presentation with a verbal explanation just by adjusting the reading order.
  • If there is too much information in one slide, it may be difficult to understand the content even if the readability is improved.
  • Attached graphics used in different materials with no alternative text and no information that can be read by a screen reader
Efforts to Improve Accessibility
  • Use text or a Web page as a alternative content for a slide

In order to solve these issues, we will continue to develop the flow and various guidelines for creating PDF documents and the accessibility confirmation system.