• 1 Unified Use Cases for Expert Handlers (Draft 2.02b)
  • 1.1 Introduction: What Are Expert Handlers?
  • 1.2 Speech Use Cases for Expert Handlers
  • 1.3 Alternative Input Use Cases
  • 1.4 Navigability Use Cases
  • 1.5 Magnification Use Cases
  • 1.6 Braille Display, Embossing and Tactile Conversion Use Cases
  • 1.7 Universal Use Cases
    • 1.7.1 Universal Use Case 1: Where Am I?
    • 1.7.2 Universal Use Case 2: Document Summary
• 2 Putting It All Together: Expert Handlers and the Flow of Control
• 3 Footnotes

document status: internal draft – this is a work-in-progress
revision date: 2008-01-21
previous versions: Draft 2.02a (2008-01-14), Draft 2.01 (2007-12-22)

authors: Pete Brunet, Vladmir Bulatov, Gregory J. Rosmaita, Janina Sajka and Neil Soiffer (chair, Expert Handlers SIG)
edited and annotated by Gregory J. Rosmaita

please provide feedback on this draft to the Expert Handlers SIG either via the Expert Handlers emailing list (preferred) or directly to this document's "Discussion" page to which posted comments will be appended by the editor

Generalized content markup (such as HTML) is complimented by markup specifications that facilitate more semantically precise content markup. Examples of specialized, semantically precise markup include MathML and MusicXML. Assistive technology (AT) typically handles generalized content markup, but does not know about specialized markup. Because of this, users of AT are unable to access or navigate specialized markup effectively.

The Open A11y Expert Handlers SIG is exploring a standardized plug-in mechanism to AT software. The goal of this plug-in standard is to allow AT software to take advantage of expert software that understands specialized markup. This plug-in standard will allow the expert software to provide enhanced, semantically rich access to specialized markup so that the AT can properly render (visually, aurally, and/or tactilely) and help users navigate the semantic meaning encoded in the specialized markup.

Computer users who are blind or severely visually impaired often use assistive technology (AT) built around synthetic text to speech (TTS). These AT applications are commonly called “screen readers.” Screen reader users listen to a synthetic voice rendering of on screen content because they are physically unable to see this content on a computer display monitor.

Because synthetic voice rendering is intrinsically temporal, whereas on screen displays are (or can easily be made) static, various strategies are provided by screen readers to allow users to tightly control the alternative TTS rendering. Screen reader users often find it useful, for instance, to skim through content until a particular portion is located and then examine that portion in a more controlled manner, perhaps word by word or even character by rendered character. It is almost never useful to wait for a synthetic voice rendering that begins at the upper left of the screen and proceeds left to right, row by row, until it reaches the bottom because such a procedure is temporally inefficient, requiring the user to strain to hear just the portion desired in the midst of unsought content. Thus, screen readers provide mechanisms that allow the user to focus anywhere in the content and examine only that content which is of interest.

Screen readers have proven highly effective at providing their users access to content which is intrinsically textual and linear in nature. It is not hard to provide mechanisms to focus synthetic voice rendering paragraph by paragraph, sentence by sentence, word by word, or character by character.

Access to on screen widgets have also proven effective by rendering that static content in list form, where the user can pick from a menu of options using up and down arrow plus the enter key to indicate a selection, in liue of picking an icon on screen using a mouse.

Access to content arrayed in a table can also succeed by allowing the AT to simulate the process a sighted user employs to consider tables. In other words, mechanisms are provided to hear the contents of a cell and also the row and column labels for that cell (which define the cell's meaning).

Similar “smart” content rendering and navigation strategies are required by screen reader users in more complex, nonlinear content such as mathematical (chemical, biological, etc) expressions, music, and graphical renderings. Because such content is generally the province of knowledge domain experts and students, and not the domain of most computer users, screen readers do not invest the significant resources necessary to serve only a small portion of their customer base with specialized routines for such content. Furthermore, the general rendering and navigation strategies provided for linear (textual), menu, and tabular content are woefully insufficient to allow users to examine specific portions of such domain specific expressions effectively. On the other hand domain specific markup often does provide sufficient specificity so that the focus and rendering needs of the screen reader can be well supported.

In order to gain effective access to such domain specific content screen reader users require technology that can:

• Synthetically voice the expression in a logical order
• Allow the user to focus on particular, logical portions of expressions possibly at several layers of granularity
• Appropriately voice specialized symbols and symbolic expressions

There are users with disabilities who do not require accomodation in order to read domain specific markup. Rather, these users require assistive technologies to facilitate their scrolling and/or editing of content. Highly effective assistive technologies exist to accomodate alternative input strategies ranging from:

• speech input technology, such as DragonDictate;
• mouse and keyboard alternative systems, such as the [http://www.gok.ca/ GNOME On-Screen Keyboard (GOK)], and;
• context aware word-prediction technologies, such as Dasher

Users of alternative input assistive technologies require two specific accomodations for scrolling and editing domain specific content:

1. Context aware expedited scrolling and navigation. The Navigation Use Cases outlined in this document will serve this requirement.
2. Knowledge domain context aware command and content vocabulary for speech based navigation systems and for word-prediction systems.

Assistive Technology (AT) users need to be able to navigate within sub-components of documents containing specialized content, such as math, music or chemical markup. Typically these specialized components have content which needs to receive “focus” at different levels of granularity, e.g. a numerator within a numerator, an expression, a term, a bar of music, etc.

Within each level, functions are needed in response to AT commands to inspect and navigate to and from “items” (e.g., by word, bar, expression, clause, term, depending upon the type of content being expressed) for a particular level of granularity:

1. contextual query/inspection of object/glyph with current focus (“Where Am I?”)
2. character-by-character
3. previous/current/next item
4. all items with user-defined characteristics
5. all items in a author-defined category ^{footnote 1]}
6. first/last item on a line
7. first/last item within next higher or lower level of granularity
8. first/last item in the document

There are two scenarios to consider, a read-only scenario and a scenario where the user is editing the document.

There are three system components that need to interact: the user agent, e.g. a browser, the AT, and the plugin/handler.

In the read-only case, the AT responds to some sort of “Point of Regard” change event and depending on the “role” of the object which received focus, the AT fetches accessibility information pertinent to that role and then formats/outputs a response tailored to an AT user, e.g. TTS/braille. In the case of specialized content, a handler needs to be used by the AT because the AT doesn't know how to deal with such specialized content directly.

In order to meaningfully interact with the specialized content, the user needs to be able to execute the following actions:

• change level of granularity up/down
• read all from top
• read all from Point of Regard (POR)
• goto and read first/last item on the current line
• goto and read first/last item within the next less/more granular item
• goto and read first/last item in the document
• goto and read previous/current/next item

In the case of editable content there may also be a desire to have separate cursors, e.g. one to remain at the POR (the caret, if editing), and one to move around for review purposes.

The AT will already have UI input commands for most of the above functions, but probably not for changing to higher/lower levels of granularity. If the AT needs to provide the user with an increased level of granularity, in response, the AT would call the handler to change the mode of granularity. The AT will handle the UI commands and in turn call the handler to return an item at the current level of granularity. The AT would have told the handler about the output mode, e.g. braille or TTS. Armed with those three things: level of granularity, mode of output, and which item (first, last, previous, current, next), the handler knows what to do.

In the case of editable content, the UA provides the input UI for the user. This editing capability would most likely be provided via a plugin. An example of such a plugin is needed so that one can evaluate what accessibility features need to be added to the existing editors.

The most obvious use of magnification is for rendering the entire content larger. For text-based (or more generally, font-based) applications, this means that Assistive Technology (AT) software should be able to request rendering with larger sized fonts or a certain amount of magnification relative to some baseline magnification. Applications beyond standard text-based ones include math, music, and labeled plots/graphics. For non text-based applications such as graphics and chemical structures, magnification could be based on a certain percentage of the normal size or given by “fill this area”. These two ideas can always be mapped onto each other. In all of these cases, the magnification may be due to having the entire documented magnified or it may be due to a request to magnify an individual instance (such as an equation).

There are two other uses for magnification:

1. While navigating or speaking, it might be desirable to magnify the part being navigated/spoken to make it easier to see. For example, while playing some music, the current measure and next measure might be magnified to ease reading while leaving the rest unmagnified so that the amount of screen space used is minimized. There will also need to be a method to reset the magnification.
   
   
2. Math and Chemical notation shrink fonts for superscripts and subscripts. In math, these are further reduced for nested scripts. One common feature for math renderers is to set a minimum font size. Typically, this is 50% of the base font size and corresponds to the size used for doubly nested scripts. It is potentially useful to allow the AT to control the maximum percent shrinkage used by renderers. Another possibility is to have a feature that says “don't shrink at all”.

Although the rendering would not be consider high quality typesetting, it does make scripts more readable to those with some vision impairment.

An Expert Handler should be able to provide braille data for braille display output by generic Assistive Technology (AT). Custom braille output is needed, because generic AT has no knowledge about how specific specialized data can and should be represented via braille. An example is MathML: there are many different braille codes used to represent mathematics that vary from country to country and agency to agency.

An Expert Handler should also provide a means to allow a user to select a different type of braille conversion than that which is normally utilized by a user's refreshable braille display or a tactile graphic achieved via embossing or thermal printing.

Simple ASCII strings are normally used to communicate braille to braille devices. However, there are a lot of specific ASCII-to-dots pattern-encoding tables used to generate braille that conforms to a natural language's braille conventions. Therefore AT and expert handler have to negotiate braille table to be used. Another more universal approach would be use special braille Unicode symbols in range from 0x2800 to 0x28FF.

There is also a need to have braille output tailored to various level of granularity. For example, at a low level of granularity, the user would receive an overall description of the mathematical expression or image, while at the highest level of granularity, the user would receive a complete braille translation of the whole math expression or list of all labeled components of the image.

Some data may need to be expressed in a more advanced tactile output format than refreshable braille. For example, graphical data would greatly benefit from being embossed on paper or a 2D braille display. Input devices, such as a touchpad or camera, which allow a user to communicate to the computer which parts of the graphic the user is interested in and needs tactilely displayed. Such interactive functionality should be left exclusively to the Expert Handler. This means, that an Expert Handler must have an interactive mode and a way for an AT to trigger/toggle this mode on. In such a mode, an AT should also provide a way for the Expert Handler to produce more than one output stream – such as simultaneous speech and braille output – directly via an AT device which uses the same TTS engine or/and braille display.

The user must have a means of obtaining all available information about the object/character with focus, beginning with the repetition of the character or the programmatic binding which describes the object with focus. The ability to query the AT to determine one's point of regard within a document and within containers in the document is essential. An AT may create a User Interface where successive “Where Am I?” requests generates more verbose or more terse responses. ^{footnote 2]}

A user may find it necessary to consult a “Document Summary”, containing a list of the types of elements and containers in the document. The user needs to know the document title and language as well as the number of tables, links, headings, frames, forms, controls, items, images, and pages. The application may implement a document summary feature natively through its own UI instead of an accessibility API, but in the case of specialized markup, may need the assistance of an expert handler in order to present an appropriate document summary for the content being summarized.

The goal of the Expert Handlers working group is to define a standard so that AT software can call on expert software to interpret specialized markup. One issue that needs to be addressed is how and where (in the flow of control of reading a page) should the expert handler get invoked. Here are three possibilities:

• During installation, the expert handler registers itself with the rendering application (e.g., the web browser, PDF viewer, etc.). When the page is loaded, the handler is invoked by the renderer to convert the DOM or some proxy for the DOM node to make it appear to have non-expert content. For example, it might convert the specialized markup to text or some generalized markup that AT can typically handle.

• The AT traverses the DOM and when it gets to some node it doesn't understand, it consults some resource that associates a particular handler with the node name. It gets the node's content (which might include other nodes) from the DOM and passes that content to the expert handler. It then issues requests to the handler (e.g., “give me text to speak for the content”).

• The AT traverses the DOM and when it gets to some node it doesn't understand, it consults some resource that associates a particular handler with the node name. It then points the expert handler to that node and issues requests to the handler. In this case, the handler is directly interacting with the DOM.

Although similar, the later two cases probably have implications on the difficulty of implementation and the capabilities of the interface. Some of these are:

• If the expert handler directly reads the DOM, then the expert handler must understand MSAA, IA2, or whatever is appropriate for the level of functionality it needs. This also implies that the rendering application must support those standards. If not, the expert handler would need to know how to access application specific DOMs.

• If the expert handler is given a copy of what resides in the DOM, then interacting with the content (e.g., filling in a text field) would complicate any standard that is developed because support for passing info about input would need to be part of the standard.

Note 1. for example, the FIELDSET, LEGEND, LABEL grouping and labelling mechanisms for FORM controls or the headers/id relationship defined for TABLE in HTML 4.01/XHTML 1.0 or the ARIA markup “<a href=“http://www.w3.org/TR/aria-roles/#labelledby”>labelledby</a>” and “<a href=“http://www.w3.org/TR/aria-roles/#describedby”>describedby</a>”

• return to the text following note 1

Note 2. For each potential point of regard, the AT may require the following element characteristics, if they exist, depending on the type of elements in the item at the current POR:

• For all locations:
  1. Number of items in the document
  2. Relative item number (n of total) within the document
  3. Document title
• Table information if in a table:
  1. Caption and table summary
  2. Content for row and column headers
  3. Relative number (n of total number) for the table in the document
  4. Relative row and column number (x of total, y of total) within parent table
  5. Table type/role (data, spreadsheet, calendar)
• Section information if in a section:
  1. Section type (page, frame, heading)
  2. Section title
  3. Relative number (n of total) for the section type in the document
  4. Level if in a section with a heading
  5. Relative item number (n of total) within the section
• Form control information if on a form control:
  1. Group label for a control (such as LEGEND or OPTGROUP in HTML) if in a group
  2. Label or alternative text (such as title or alt in HTML or title and desc in SVG)
  3. Type of form control (role)
  4. State
  5. Relative number (n of total) of the parent form in the document
  6. Relative form control number (n of total) within the parent form
• Map information if in a map:
  1. Relative area number (n of total) within the areas of a map
  2. Title attribute for map
• List or menu information if within a menu or list:
  1. Type (role) - menu, simple list, definition list, ordered list, folder, navigation bar, and so on
  2. Title from parent menu or list
  3. Relative number (n of total) of parent list or menu in the document
  4. Relative list item number (n of total) within the list
• Link information if on a link:
  1. Relative link number (n of total) within the document
  2. Link state: visited, unvisited, active, focused, external or internal
  3. Extended information, such as that provided by the title attribute
• return to the text following note 2

• return to the Handlers SIG's Use Case page
• Expert Handlers Draft Documents Index
• return to the Handlers SIG's main page
• return to the Open A11y's main page