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.

How Should Numbers Containing a Slash (/) Be Read Aloud?

Last Updated: May 7, 2024

Tags: Screen Reader

Question / Problem

For instance, with the number “11/12”, it should be clear from the screen reader’s pronunciation whether it denotes November 12th, page 11 of 12, or 11 out of 12.

Answer / Conclusion

  • If pronounced “11 slash 12”, no further action is required.

  • If it is pronounced differently in the intended environment, consider implementing a remedy.


If pronounced exactly as “11 slash 12”, users should be able to discern its significance in the context, thus requiring no specific action. However, if it remains challenging to interpret even when read correctly, it might also be difficult for those viewing the screen to understand, necessitating a reevaluation of the notation used.

Note that some screen readers may read it aloud as “November 12th” or “eleven twelfths”. If this occurs in your primary environments, it could confuse users, prompting the need for a corrective measure.

Below are some strategies to address this:

  • Add spaces around the slash in “11 / 12” to ensure it is read as “11 slash 12”.

  • Display it in a format conducive to the intended reading, like “November 12th”. Aim to align the displayed text with the spoken text as closely as possible.