CARVIEW |
Placeholder for information about ruby accessibility.
The document Rules for Simple Placement of Japanese Ruby has been moved here.
The information below about accessibility was removed from that document, and is retained here until it can be extended, at which point it will be published as a separate, accessibility-specific document.
Ruby and Accessibility
Accessibility Improvements Using Ruby
Ruby plays a role in improving accessibility for people with visual impairments, and other sources of reading difficulties. Therefore, this section examines the relationship between ruby and accessibility.
Reading difficulties can be caused by a variety of factors, and therefore, requirements to improve accessibility also vary. For example, here are some common requirements:
-
To accommodate young children who cannot read any kanji, general-ruby must be added to all kanji.
-
As studies progress, a greater number of kanji is known. After having read general-ruby many times, ruby on difficult kanji only becomes sufficient. Therefore para-ruby on only some of the kanji is required.
- Some people have difficulties in visually distinguishing between ruby characters and the base characters to which they are attached, and misread the combination as a different character altogether. There must be a display method that enables clearly distinguishing between the two. Also, for those who already know how to read the kanji, there must be a way to hide the ruby.
- As inline parenthesised annotations can be used instead, there is no strong need for double-sided ruby.
Ruby Display Requirements for Accessibility
Based on the above, we can gather the following ruby display requirements for accessibility:
- Support for general-ruby is required.
- Support for para-ruby is required. Moreover, as the number of kanji known increases with the level of studies, based on the content and on the level of the reader, it must be possible to only display ruby for kanji assigned to a particular school year (or later).
- Support for hiding ruby is required.
- Considering the cost of production, distribution, and of user management, it is necessary to support ruby-less display, general-ruby display, and para-ruby display with the same content.
- A method to clearly visually distinguish the ruby characters and their based characters, such as displaying them in different colors, is required.