Caution
This document is an English translation of the “freee Accessibility Guidelines.” The normative version of this document is in Japanese, and the English version is informational. The English translation is incomplete, and any links with their link texts left in Japanese are untranslated. Please be aware that there may be inaccuracies in the translation or parts that are outdated.
Update History
Here, we list updates related to the English translation since the introduction of Ver. 202403.0, when we began providing translations of all guidelines. For the changes to the original Japanese version, please refer to the Japanese version of this page.
Changes After the Latest release
Added translation of Issues with Content Changing Automatically
Ver. 202409.0 (Sep 26, 2024)
Added a new guideline for mobile applications corresponding to WCAG 2.1 Success Criterion 2.5.1 and related explanations:
Updated the accessibility checklist to V5.1.0
Ver. 202408.0 (Aug 20, 2024)
Updated Correspondence Between axe DevTools Rules and These Guidelines to be based on axe-core source as of May 16, 2024
Updated About Editing This Document to reflect the current state
Updated the Accessibility Check List to V5.0.2
Ver. 202405.0 (May 14, 2024)
Added FAQ: How Should Numbers Containing a Slash (/) Be Read Aloud?
Updated Correspondence Between axe DevTools Rules and These Guidelines to be based on axe-core source as of April 29, 2024
Added translations:
Added update history of this translation: this page and Google Spreadsheet for Performing Checks
Ver. 202404.0 (April 23, 2024)
Added translations:
Added FAQs:
Ver. 202403.1 (March 29, 2024)
Ver. 202403.0 (March 4, 2024)
The English translation of all guidelines was released.