Web Accessibility Verification Results
Tests based on JIS X 8341-3:2016 will be conducted and the results will be published.
The notation of "compliant" in this verification result is based on the notation specified in "JIS X 8341-3:2016 Compatibility Notation Guideline for Web Content - April 2021 version " of the Web Accessibility Infrastructure Committee of the Information and Communications Access Council.
Test Results for Success Criteria for Target Conformance Level
| Item | Contents |
|---|---|
| Date of declaration | April 1, 2025 (2025) |
| Standard number and revision year of the standard | JIS X 8341-3:2016 |
| Compliance level being met | Partially based on A |
| Brief description of the Web page in question | https://www.digital.go.jp/ All pages below |
| List of Dependent Web Content Technologies | HTML, CSS, JavaScript, PDF |
| Check tool used for the test | Nu Html Checker, Adobe Acrobat Pro, axe-core |
| Operating systems, user agents, and assistive technologies used to validate the content | Windows 11 / Google Chrome / NVDA, Windows 11 / Adobe Acrobat Reader / NVDA, iOS18.3 / Safari / VoiceOver |
| How the web pages to be tested were selected | 60 pages (web page: 40 pages, PDF:20 files) by random sampling, selecting 14 pages and one PDF file as representative web pages for a set of web pages |
| Web page where the test was conducted | Web accessibility verification result test execution page list |
| Success Criteria Checklist | Success Criteria Checklist |
| Study Period | From March 10 to March 28, 2025 (2025) |
| Additional measures beyond the Success Criteria to improve accessibility | A "Go to Text" link at the top of each page |
Success Criteria Checklist
- In the "Apply" column, "Yes" indicates that the Achievement Standard is applicable, and "-" indicates that the Achievement Standard is not applicable.
- In the "Result" column, "Yes" indicates that the Success Criteria have been met, and "X" indicates that the Success Criteria have not been met.
- Please refer to the glossary in Web Content Accessibility Guidelines (WCAG) 2.0 (Japanese translation) for terms used in the Success Criteria.
Success Criteria Checklist
| No. | Success Criteria | Compliance level | Apply | Result | Notes |
|---|---|---|---|---|---|
| 1.1.1 | Non-text content | A | Yes | No | Some Web pages do not include alternative text for images, and some PDFs do not include images with alternative text |
| 1.2.1 | Audio only and video only (prerecorded) | A | - | Yes | No Affected Content |
| 1.2.2 | Captions (prerecorded) | A | Yes | Yes | |
| 1.2.3 | Audio description or alternative content to media (already included) | A | Yes | No | Both audio description and transcribed text are not attached to some video contents |
| 1.2.4 | Live Caption | AA | - | Yes | No Affected Content |
| 1.2.5 | Audio description (pre-recorded) | AA | Yes | No | Some video content does not have audio description |
| 1.3.1 | Information and Relationships | A | Yes | No | List items are not marked up as lists in some sentences, and headlines are not marked up as headlines in some Web pages |
| 1.3.2 | Meaningful order | A | Yes | Yes | |
| 1.3.3 | Sensory characteristics | A | - | Yes | |
| 1.4.1 | Using Colors | A | Yes | Yes | |
| 1.4.2 | Voice control | A | Yes | Yes | |
| 1.4.3 | Contrast (minimum level) | AA | Yes | Yes | |
| 1.4.4 | Resize Text | AA | Yes | Yes | |
| 1.4.5 | Character image | AA | - | Yes | No Affected Content |
| 2.1.1 | Keyboard operation | A | Yes | Yes | |
| 2.1.2 | No keyboard trap | A | Yes | Yes | |
| 2.2.1 | Timing adjustable | A | - | Yes | No Affected Content |
| 2.2.2 | Pausing, Stopping and Hiding | A | - | Yes | No Affected Content |
| 2.3.1 | 3 flashes or less than threshold | A | - | Yes | No Affected Content |
| 2.4.1 | Block skip | A | Yes | Yes | |
| 2.4.2 | Page Title | A | Yes | No | Some PDFs do not have titles |
| 2.4.3 | Focus Order | A | Yes | Yes | |
| 2.4.4 | Purpose of the link (in context) | A | Yes | Yes | |
| 2.4.5 | Plurality of means | AA | Yes | Yes | |
| 2.4.6 | Headings and Labels | AA | Yes | Yes | |
| 2.4.7 | Focus Visualization | AA | Yes | Yes | |
| 3.1.1 | Page Language | A | Yes | No | Some PDFs do not have language settings |
| 3.1.2 | Some of the languages | AA | Yes | No | On a machine translated English page, the channel name and title of the YouTube embedded content contain Japanese, but the program cannot interpret the natural language |
| 3.2.1 | On Focus | A | - | Yes | No Affected Content |
| 3.2.2 | Input time | A | - | Yes | No Affected Content |
| 3.2.3 | Consistent Navigation | AA | Yes | Yes | |
| 3.2.4 | Consistent distinctiveness | AA | Yes | Yes | |
| 3.3.1 | Identifying Errors | A | Yes | Yes | |
| 3.3.2 | Label or Description | A | Yes | Yes | |
| 3.3.3 | Error Correction Suggestions | AA | Yes | Yes | |
| 3.3.4 | Error avoidance (legal, financial and data) | AA | - | Yes | No Affected Content |
| 4.1.1 | Syntax analysis | A | Yes | Yes | |
| 4.1.2 | Name, role, and value | A | Yes | Yes |
Issues identified by the study and directions for their resolution
As a result of the tests, we are aware of the following issues, and we will continue to work to resolve each issue.
Issues found in Web pages (HTML)
- Headings and list items are not marked up as headings or lists on some pages (Success Criterion 1.3.1, Information and Relationships)
In order to resolve the above issues, we will continue to improve the flow of creating web pages, various guidelines, and the accessibility confirmation system. We will also revise components as necessary.
Challenges with Non-Text Content such as Images and Videos in Machine Translated English Pages
- If there is text in the image, the text will not be translated and only the alternative text will be translated into English, so the alternative text may not play the same role as the image (Success Criterion 1.1.1, Non-Text Content).
- On a YouTube video page, the channel name or video title contains Japanese characters that cannot be interpreted by programs such as screen readers. (Success Criterion 3.1.2, Partial Languages)
In order to solve the above issues, we will consider measures from both technical and operational aspects, including the use of generative AI.
Issues found in the PDF file
- Success Criterion 1.1.1 Non-Text Content Identified with Files That Do Not Have the Appropriate Alternate Text for Images
- Some documents do not have markup or bookmarks, which may make it difficult for screen reader users to understand the content of the document. (Success Criterion 1.3.1, "Information and Relationships")
- Untitled files identified (Success Criteria Page 2.4.2 Title)
- Missing Language Settings Identified (Success Criteria: Language on page 3.1.1)
Overview of Accessibility by Material Type
Agenda, minutes, and meeting materials
The lack of tagging, language settings, and file titles makes it difficult to use with screen readers.
Initiatives to Improve Accessibility
- When posting in PDF format, prepare the agenda, minutes, and meeting materials so that they can be read by a screen reader.
- If it doesn't have to be a PDF, prepare a web page.
- Further Efforts
- Add headings to help you understand long sentences accurately and move around the document more easily
- For long documents such as minutes, provide a summary at the beginning to make it easier to understand the entire document.
Presentation materials
- The lack of tagging, language settings, and file titles makes it difficult to use with screen readers
- It is not possible to understand the content of the presupposed presentation materials with oral explanations only by adjusting the reading order.
- Materials that contain too much information per slide may be difficult to understand, even with increased readability
- I have attached an image without alternative text that was used in a different document, and there is no information that can be read by a screen reader.
Initiatives to Improve Accessibility
- Provide text data or web pages as alternative content for slides
In order to resolve these issues, we will continue to promote the flow of creating PDF documents, various guidelines, and the development of an accessibility confirmation system.