Find out how QuickBooks Desktop for Windows was rebuilt to make it accessible. QuickBooks for Desktop was originally developed before Microsoft’s accessibility APIs. The program was built upon custom drawn elements and the accessibility was always minimal.
However, a small group of developers and users worked together in 2013 to fix the issues within the core and added screen reader scripting to make QuickBooks 2014 accessible.
This presentation was developed for the ATIA 2014 conference in Orlando to show what is possible, even with a legacy product, when there is a commitment to making an accessible product.
Continue Reading QuickBooks Desktop Accessibility
This presentation was created for the TechShare conference in Delhi, India Feb. 2014 It shows how Intuit’s mobile strategy has encouraged accessible mobile applications. The secret behind Intuit’s mobile accessibility strategy is that it has less to do with accessibility and everything to do with user experience and user-based design.
Continue Reading Developing a mobile accessibility strategy
This presentation was created for the Mobile+Web Developer Conference in San Francisco, Jan. 2014
Continue Reading iOS7 Accessibility
The HTML specifications for forms suggests using a
<legend> to define similar items within a form. Normally this is used to combine the forms into large chunks, for instance the billing address, credit card information, and personal information. It’s also useful for combining radio and checkbox sets.
Typically, we associate a form input with a label. The label is announced as the screen reader places focus on the input. This works very well for letting the user know what the checkbox or radio button represents, but it doesn’t give the user context for how it is applied. For instance, the following radio button would be announced as “radio button Yes”. But what is the user saying yes to?
Continue Reading Fieldset legend, aria-describedby, and radiogroup role
There are times when we want the screen reader to announce individual letters in a string. This is sometimes up to the interpretation of the screen reader with an acronym, such as NASA. There are other times when we need to force the digits, for instance in a confirmation code IXbib. This page will test options for making a screen reader announce this confirmation code: IXbib
Continue Reading Force the screen reader to announce digits