Collaborative editing for all: the google docs example

TL;DR: Results of an accessibility inspection of the main collaborative functions of Google Docs using the JAWS screen reader are illustrated and some general guidelines are discussed, for designing user interfaces of collaborative editors that are more usable when interacting via screen reader.

Abstract: Collaborative software tools allow people to share documents and knowledge via Internet, in a simple, economic and efficient way. Unfortunately collaborative software often relies heavily on visual features and dynamic technologies with user interfaces that are difficult to use via screen reader, or are sometimes even inaccessible for the blind. In this paper we illustrate and discuss results of an accessibility inspection of the main collaborative functions of Google Docs using the JAWS screen reader. Results highlight several difficulties encountered when interacting with elements of the Google Docs interfaces. Content perception is often incomplete, since many elements or changes occurring in the collaborative environment are not intercepted by the screen reader and announced to the user. In addition, the behavior of the collaborative functions analyzed (as well as the rendering) changes from one web browser to another. Some general guidelines are discussed, for designing user interfaces of collaborative editors that are more usable when interacting via screen reader.