LESSON 1: Price of solutions is critical.
- This is a message we received repeatedly in our end-user surveys, workshops, and pilot testing. Few if any governments, schools, and employers fund purchase of all of the accessibility solutions needed by individuals with disabilities. Bringing down the costs of such solutions, therefore, is critical to increasing their adoption and the societal benefits from their widespread use.
LESSON 2: 3rd generation mobile solutions (e.g. Tecla) is groundbreaking
- One user said she would have paid any amount for having Tecla (while Tecla is for free).
- Paying for purchases via chin on wheelchair joystick. The AEGIS OAF and developments we were able to build around it in the mobile space – with the initial, specialized AT for people with physical impairments – clearly demonstrated significant potential for increased efficiency, and productivity, and inclusion possible with this work. It suggests that there is significant future research potential in this area.
LESSON 3: More needed downstream for ARIA success
- Different “interaction modes”: web vs. desktop vs. “web application” → training & more research needed End-user pilot testing of JAWS 12 with our ARIA-enabled components and web applications clearly demonstrated several key things, including: that the AT was not mature enough for ARIA, and that users think they will find web content (and not web applications) within the browser, and so are unprepared to interact with that content as if it is an application. Furthermore, sometimes “web content” models are appropriate within “web applications” - e.g. for content using headers.
LESSON 4: OAF really helps organize a very complicated landscape
- Accessibility Advisor; need for UI components, need for developer/author tool assistance
- Value of Personas and Ontology Successive generations of technology bring with them the need to be accessible. Digital technology is coming to more and more devices and aspects of our lives – such as (digital) television, (digital) household appliances. The OAF helps orient developers of these technologies to all of the things they need to do to be accessible (compared to the temptation to expediently address only those needs of disability advocate groups who gain their attention).