Difference between revisions of "OATTS (Open Access Tool Tray System)"

From wiki.gpii
Jump to: navigation, search
Line 1: Line 1:
 
*'''What''': this is a tray and tools that are used to make telecollab and other online (or phone) work more accessible
 
*'''What''': this is a tray and tools that are used to make telecollab and other online (or phone) work more accessible
**Examples
+
**<div>Developed to address the issue of the lack of accessibility features in &nbsp;telecollaboration software</div>
 +
**<div>web-based "tool-tray" of accessibility features and tools (widgets)<br/></div>
 +
**<div>works with any telecollaboration system<br/></div>
 +
**<div>Users can choose the tools (widgets) they need and store them in their personal tray</div>
 +
**Widgets
 +
***<span class="s2">Each widget provides different accessibility function or service</span>
 +
***<span class="s2">Widget either independently provides accessibility services or acts as a gateway</span>
 +
***<span class="s2">People can create new widgets</span>
 +
***<span class="s2">Proprietary and open source widgets allowed</span>
 +
**Widget examples
 
***caption tools &nbsp;
 
***caption tools &nbsp;
 
****Caption tool (scheduled and on demand) that display in a resizable, &nbsp;positionable, always stay on top, window.
 
****Caption tool (scheduled and on demand) that display in a resizable, &nbsp;positionable, always stay on top, window.
Line 16: Line 25:
 
**Put all preferences into GPII compatible form
 
**Put all preferences into GPII compatible form
 
**Incorporate some of the GPII &nbsp;UI Access features into OATTS tools
 
**Incorporate some of the GPII &nbsp;UI Access features into OATTS tools
 +
*Screenshots
 +
*

Revision as of 01:31, 30 January 2015

  • What: this is a tray and tools that are used to make telecollab and other online (or phone) work more accessible
    • Developed to address the issue of the lack of accessibility features in  telecollaboration software
    • web-based "tool-tray" of accessibility features and tools (widgets)
    • works with any telecollaboration system
    • Users can choose the tools (widgets) they need and store them in their personal tray
    • Widgets
      • Each widget provides different accessibility function or service
      • Widget either independently provides accessibility services or acts as a gateway
      • People can create new widgets
      • Proprietary and open source widgets allowed
    • Widget examples
      • caption tools  
        • Caption tool (scheduled and on demand) that display in a resizable,  positionable, always stay on top, window.
        • CCCC (Controlable Crowd Caption Correction) Tool  (see below)
        • low cost caption tool  (allows use of speech recognition and rapid correction to create captions)
      • sign language on demand tool  (similar to caption tool)
      • hand raising tool - to ensure that people using captions (which are by nature delayed) or who are slower have the opportunity to participate on level playing field.  Also facilitates participation by less gregarious participants - and those who want to quickly contribute but not speak. 
  • Technology
    • Implemented in JavaScript and PHP and MySQL.  It runs as a ChromeApp (or a Chrome Extension).  
    • Compatible with  Windows, Linux, Mac.  
  • ToDo:  
    • Mount system on GPII server
      • This will then become an infrastructure service of GPII under Prosperity4All
      • It will also server as a model for other similar tools -- as well as a model for GPII compatibility for this type of tool
    • Put all preferences into GPII compatible form
    • Incorporate some of the GPII  UI Access features into OATTS tools
  • Screenshots