Evaluating Groupware Accessibility

Accessible collaborative writing for persons who are blind

“…Researchers surveyed respondents on the access and use of electronic docum ents [3], conducted automated examinations of Google Docs [7 ], and conducted screen reader examinations of Google Docs [1 , 2] ywangtu@gmail.com to co-editing text synchronously, collaborative writing tasks such as adding, changing or deleting text and comments, and comparing these results between vis ually able persons and persons who are blind in order to identify ways to improve accessibility and usability.…”

Accessible chats for computer supported collaborative learning environments in mobile devices: Doctoral consortium paper

“…Besides, if a new Window is opened or Java technology generates new buttons, then the user can be disoriented if they are not tagged properly [27]. Furthermore, some chats do not provide support for text-to-speech or text-to-braille which is useful functionalities for screen reader users [28].…”

“…For instance, developers use hierarchy navigation [28]. Another problem is related to the use of advanced functionalities or the use of functionalities which cannot be accessed by keyboard [30].…”

An Accessible Chat Prototype for Screen Reader Users in Mobile Devices

“…However, this kind of tools in MDs could present additional problems than other information technology (IT) systems like in-teraction problems or auto-refresh content [5]. Furthermore, some people cannot follow the conversation [6].…”

“…For instance, if one of the emitters is not able to write quickly and if there are not ways to establish the turn to write, he could have problems to follow the rhythm of the conversation [7] [8]. Besides, screen reader users face other specific problems related to the web page's auto-refresh or updated content because it causes the restart of the screen reader [3]; the use of keyboard traps [4]; or the lack of support for text-to-speech or text-to-braille functions [5].…”