March 30, 2015
G3ict, in collaboration with Adobe Accessibility, presents a free white paper on PhoneGap accessibility. This 10-page introduction covers the state of mobile app accessibility, the advantages inherent to PhoneGap’s approach in creating accessible cross-platform mobile apps, and Adobe’s motivation to create a PhoneGap accessibility plugin that bridges the gap between web accessibility and native mobile accessibility APIs.
If you’re looking for a high-level introduction on what makes PhoneGap a good platform for building accessible mobile apps, this is it.
The PhoneGap Mobile Accessibility repository on Github is also available for PhoneGap developers who are interested in implementing more advanced accessibility support in their apps. (TL;DR PhoneGap apps by default benefit from good web accessibility practices, but the accessibility plugin gives developers access to native accessibility APIs, such as whether high contrast is on, or the user has selected a preferred text size.)
May 22, 2006
The Spry framework is not finished at this time. The support for accessibility is developing, and I’d love to hear comments. Feel free to post comments here or to the Spry forum on the Labs site.
Sounds pretty good, but what are the drawbacks? Page length and page weight are certainly factors to consider. If the page shows all of the data on a single page, there will be (in the case of the product demo) 150KB of images instead of 7KB and the page could be very long since it would have all of the content that is specific to each product on one page. There is the risk that the page would not be usable because of the length or page weight for some examples. Looking at the photo gallery demo I wouldn’t want all of the images from all of my photo galleries on a single page — pagination and separate galleries are useful features that help users deal with the large volume of content.