![]() |
Guideline 6 Current interfaces to equations in educational software pose two sets of problems: first, users who are blind cannot read equations (and users with low vision may have trouble reading them at small sizes), and second, both users with visual impairments and those with physical disabilities have difficulty using equation input and editing interfaces that require use of a mouse. Checkpoint 6.1 Checkpoint 6.2 Understanding longer or more complex equations requires navigating within the equation to hear different parts separately. Equations provided in educational content that cannot be changed by the reader are referred to here as static equations. Equations that can be edited or written by the user are referred to as dynamic equations. Currently screen reader software for users with visual impairments cannot accurately read most math equations. Superscripts and subscripts, for example, may be read as a separate line from the rest of the equation's characters, and many special symbols aren't recognized by screen readers. Equations may be rendered as a single graphic and not recognized at all by screen readers. Software developers may use a range of means to read static equations to users, including direct approaches (providing pre-recorded audio files) and compatible approaches (making equations accessible to screen readers). A direct approach such as pre-recorded files would provide access for blind and low vision students, though not for those who are deaf-blind. The audio must include sufficient information about the structure of the equation to avoid confusing the listener. Unstructured communication is only adequate in cases of very simple mathematics. For example, nested fractions such as (x+2)(3/5) are difficult to convey accurately in speech without a structured way of speaking. See Appendix 4, Guides to Spoken Mathematics, for resources. Software that allows users to write new material including equations must provide a way to access any user-created text. The best solution is to use a standardized mark-up language that assistive technologies can interpret. The best choice is Math Markup Language, or MathML, defined by the World Wide Web Consortium. Screen readers cannot yet read MathML, but research and development efforts will make this possible soon. Widespread use of MathML by software developers will hasten the creation of solutions for users of assistive technology. See Technique 6.2.1. A second possible markup language for equation display is LaTeX. Tools do exist for converting LaTeX to Nemeth braille for blind users. These tools are designed to convert entire documents rather than for use with interactive software, but this does permit some access to instructional materials. See Technique 6.2.2. If these developing technologies fail, it is essential to find an interim solution to make equations accessible to students who are blind. A custom-designed text or text-to-speech solution can provide access to user-created equations without interfacing with assistive technologies. For example, the software developer could use a system of spoken mathematics to write out equations and send equations directly to a text-to-speech program. Care must be taken when using this option to include blind and low vision users in testing to ensure that the amount and timing of the equation voicing meets the users' needs. See Technique 6.2.5 for more information. Technique 6.2.1 The W3C's Math Home Page www.w3.org/Math Mathematical Markup Language (MathML) 1.01 Specification www.w3.org/TR/REC-MathML The advantage of MathML is it provides mathematical information in an open, standard format which can be exploited by a wide range of assistive technologies. Research is in progress on the development of specialized browsers or plug-ins capable of providing speech or braille output of MathML content. Information on the MAVIS Project talking MathML browser is available from www.nmsu.edu/~mavis/browser.html and www.nmsu.edu/~mavis/mavistex.html provides additional details. Math-capable assistive technologies that can interact with mainstream web browsers will likely be developed once MathML becomes a common means of publishing electronic math content. For maximum accessibility, software that includes content written in MathML and HTML should allow users to use a browser which provides the functions they need. If MathML is the protocol used to deliver math content but the product is not HTML-based, the MathML content should be available as part of an operating system accessibility API or in an accessibility mode allowing access by assistive technology. Once software programmatically exposes the MathML markup used to display math on the screen, assistive technologies will give users interactive control of reading and writing equations. Note that MathML itself is not intended to be human-readable; tools will interpret the markup and create a useful representation in speech or braille. Technique 6.2.2 Technique 6.2.3 Technique 6.2.4 For example, in the accessible prototype "How the West Was One + Three x Four," created by the CD-ROM Access Project, users can create simple four-function equations. Each character is voiced as it is entered and each character deleted is voiced with the message "deleted." The whole equation can be read back on command. Two digit numbers are read as single digits when entered but as complete numbers when read back. This prototype can be downloaded from the West Prototype section. Technique 6.2.5 Another interim solution is to send equation information directly to a text-to-speech engine. To use this technique, the software must provide a mode where the entire text of the equation is read and commands for reading specific sections of the equation. The software must also allow the user to move through the text in shorter chunks, such as parts of equations. Mechanisms for internal equation navigation may be required to allow the user to read specific elements and determine their position and relationship to other elements within the equation. See Appendix 4, Guides to Spoken Mathematics, for resources. |
|
TABLE OF CONTENTS | CREDITS WGBH | NCAM | CD-ROM PROJECT |