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.

Ver. 202504.0 (Apr 22, 2025)

• Added FAQ: Should the Words “Icon” or “Button” Be Included in the Alternative Text of Icon Images?

• Added FAQ: Screen reader stops reading long text in the middle

• Added FAQ: Focus Movement by Tab Key Is Strange Only in Safari

• Updated Correspondence Between axe DevTools Rules and These Guidelines

  • Updated to be based on axe-core source as of April 4, 2025

  • Changed the links to Deque University articles to link to the Japanese and English pages respectively

• Updated the accessibility checklist to V6.1.0

Ver. 202411.0 (Nov 22, 2024)

• Added translation of Issues with Content Changing Automatically

• Updated FAQ

  • Added example: There Are Kanji Or English Words That Are Read in an Unexpected Way by Screen Readers

  • Added: How Should Notations Like “2024-11-21 12:30” Be Read Aloud by Screen Readers?

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:

  • Input Device: Operation by Mobile OS Standard Gestures

  • Basic Principles of Accessibility in Mobile Applications

• 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:

  • Importance of Contrast Ratio

  • Method for Checking Contrast Ratio

• Added update history of this translation: this page and Google Spreadsheet for Performing Checks

Ver. 202404.0 (April 23, 2024)

• Added translations:

  • Considerations for Using Color in Expressions

  • The Role of Wording in Text Information and Accessibility

  • Checking Accessibility With axe DevTools

  • The Importance of Properly Marking Up Semantics

  • How to Switch to Grayscale Display

  • Describing Images Through Text

• Added FAQs:

  • What Information Should Not Be Read Aloud by Screen Readers?

  • Should the hr Element Be Read Aloud by Screen Readers, And How Should It Be Read?

Ver. 202403.1 (March 29, 2024)

• Added translations:

  • Preface

  • About freee Accessibility Guidelines

  • How to Utilize the freee Accessibility Guidelines

  • About Editing This Document

  • Correspondence Between axe DevTools Rules and These Guidelines

  • How to Perform Checks With NVDA

  • How to Perform Checks With macOS VoiceOver

  • Issues Related to Click and Tap Target Sizes and How to Verify Target Sizes

• Added FAQ: The Clickable Area of a Text Link Is Small

Ver. 202403.0 (March 4, 2024)

• The English translation of all guidelines was released.