Related to exploitation

LESSON 1: Working with existing open source projects – adding accessibility support to them – greatly increases the likelihood of exploitation. Adding ARIA support to Firefox is the best example of this in AEGIS; jQueryUI accessibility is a second. GNOME Mag is a third.

LESSON 2: Developing free plug-ins to existing popular platforms is also a good way to increase the likelihood of exploitation. Our four plugins are great examples of this: Odt2daisy, odt2braille, CCF-SymbolWriter, and AccessODF.

LESSON 3: Maximizing the use of pilot testing helps enhance exploitation (not a new lesson, but something that was nonetheless very clear from AEGIS). The improvements to a number of our exploitable results that came from successive user tests – such as new features in GNOME Mag, odt2daisy & odt2braille, etc. – helped polish them to the point that they are proving very popular and gaining lots of adoption even before the end of the project.

LESSON 4: Addressing cost issues is key for AT-related adoption. One of the key pieces of feedback coming from end users was that cost is a barrier, and we have found that low cost or free exploitable results from AEGIS tend to also be the more adopted ones.

LESSON 5: Developer adoption & exploitation of tools is more difficult. There is less obvious demand for them (vs. users demanding AT). For example, the AEGIS Scientific Advisory Board praised DIAS and also our other NetBeans plugins as very innovative and advancing the state of the art, but developer downloads of these has been small.

LESSON 6: Exploitation is not only of running code/applications. The AEGIS Personas continue to be adopted & exploited. The use of Creative Commons licensing has helped with non-code exploitation.