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 (2024)

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

Test results for the target conformance level criteria

ItemContents
Date of representationApril 1, 2025
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, iOS18.3 / Safari / VoiceOver
Method of selecting web pages to be testedSelection by random sampling of 60 pages (web pages: 40 pages, PDF:20 files), 14 pages and PDF1 files as web pages representative of a set of web pages
Web page on which the study was conductedList of Web Accessibility Verification Results Test Pages
Success Criteria ChecklistSuccess Criteria Checklist
Duration of the studyMarch 10 to March 28, 2025
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.
  • Refer to the glossary in the Web Content Accessibility Guideline (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×Images in some Web pages do not have appropriate ALT text, and images in some PDFs do not have ALT text
1.2.1Audio only and video only (prerecorded)A-YesNo such content
1.2.2Captions (pre-recorded)AYesYes
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×In some texts, list items are not marked up as lists, and in some Web pages, headings are not marked up as headings.
1.3.2Meaningful orderAYesYes
1.3.3Sensory characteristicsA-Yes
1.4.1Using ColorsAYesYes
1.4.2Controlling Your VoiceAYesYes
1.4.3Contrast (lowest level)AAYesYes
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×Some PDFs do not have titles
2.4.3Focus OrderAYesYes
2.4.4Purpose of the link (in context)AYesYes
2.4.5More than one wayAAYesYes
2.4.6Headings and LabelsAAYesYes
2.4.7Focus VisualizationAAYesYes
3.1.1Page LanguageAYes×Some PDFs do not have language settings
3.1.2Part of a languageAAYes×In a machine-translated English page, YouTube embedded content contains Japanese in channel names and titles, but the natural language is not programmatically interpretable.
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)

  • Headings or list items are not marked up as headings or lists on some pages (Criterion 1.3.1 Information and Relationships)

In order to resolve the above issues, we will continue to improve the flow of web page creation, various guidelines, and the accessibility confirmation system. We will also revise components as necessary.

Challenges with Non-Textual Content such as Images and video in Machine-Translated English Pages

  • If an image contains text, the text will not be translated and only the alternate text will be translated into English, so there may be places where the alternate text does not function as well as the image (Success Criterion 1.1.1 Non-Text Content)
  • 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, including the use of generative AI.

Issues found in the PDF file

  1. Files were identified that were not properly labeled with alternate text for images (Success Criterion 1.1.1 Non-Text Content)
  2. Some are not marked up or bookmarked, which can make it difficult for screen reader users to understand the content of the document (Criterion 1.3.1 Information and Relevance)
  3. Untitled Files Verified (Success Criterion - Page 2.4.2 Title)
  4. A file without a language setting was 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.