How do you know what your customers with a disability are sharing with your company’s feedback forms and surveys? Is there an option for them to self-declare they have a disability? Probably not. The following list of keywords has been compiled from various sources and will help you data mine your customer feedback to find the voice of your disabled customers.
The following is the proposal for this presentation. I will publish the final presentation for further details.
Trickle-Down Accessibility Proposal
Trickle Down Economics suggests economic growth benefits all members of society. The focus is on tax benefits for corporations and the higher income population, as they have the potential for making larger impacts in economic growth. Providing financial incentives to this population will, in theory, eventually result in higher prosperity for all.
Matt May’s observation on Twitter in 2016 raised awareness of Trickle Down Accessibility:
“Watching a blind advocate tell someone with another disability to center blind issues first and wait for the benefits to trickle down. Wow. ”
Focusing on screen reader accessibility has distinct advantages for product developers. If your application works with a screen reader, it should also be usable with a keyboard, voice recognition, and switch control devices. Screen reader accessibility also falls in line with automated testing tools.
However, there are many disabilities, and assistive technologies, that are not necessarily benefited by this focus on the blind/low-vision community. Color contrast, closed captioning, readability, consistency in design, user customization, session timeouts, and animation distraction are just a few examples of concerns that often go unaddressed.
I love purpose built bookmarklets that help you find problematic code. I got an email yesterday from Travis Roth about a potential vestigial aria-hidden attribute on an otherwise visible element. Unfortunately, it’s not uncommon to find an element that has aria-hidden=”true” on an element that is visible and should have either “false” or no aria-hidden attribute. This causes assistive technology to ignore the element.
My first reaction was to search the code for aria-hidden attributes, but this can take time and would have to be completed on each page to find the issue.
So I created the following bookmarklet that will find any element on your page that uses aria-hidden. It will force it to be visible and will display the attribute’s value.
To use this bookmarklet, drag the following link to your bookmark toolbar. Visit your questionable page and click the link.
Intuit sets aside a week every year to give employees a chance to work with local non-profit organizations. This year, we gathered a small group to visit the Enchanted Hills Camp in Napa to help them prepare for this summer’s campers. It’s a fantastic organization and we loved our time there.
Accessibility is an important part of any app. Whether you’re developing a new app or improving an existing one, ensure that components are accessible to everyone.
Why develop for accessibility
1 in 5 people will have a disability in their life. – 2010 census
Designing for accessibility benefits blind, low vision, and eyes occupied (driving)
Android includes 4 types of assistive technology:
TalkBack: Screen reader
BrailleBack: Braille output for refreshable braille devices
Switch Access: switch control of device
Voice Access: control device by voice activation: “scroll up”
Android O’s major focus: increase productivity for users
new api additions for accessibility
print disabilities (reading disabilities)
New to TalkBack
accessibilityVolume: adjust audio volumen for accessibiity independently from media. So you can watch youtube and control that separately than talkback. This is available when talkback is on.
Volume from youtube is quieted while talkback is being used. it then fades back into the foreground. There’s a new accessibility volume slider
New gestures for talkback.
If there’s a fingerprint sensor on the back of the device, it can be used by talkback users. The sensor has its own set of customizable gestures. For instance, swipe up on the fingerprint. These can be assigned, such as longpress action
Quickly enable/disable TalkBack
long press the volume keys to quickly turn on/off talkback.
this works on any screen, this makes it easier to test apps and turn off talkback to type information. Press both keys at the same time for a long press and eventually it will turn on/off talkback. the accessibility shortcut can be assigned to switch control, zoom, or other service.
New Text to speech engine can handle multiple languages. Use LocaleSpan to trigger language switching.
2 new APIs
Continuous Gesture API: enable motor impaired users who use head tracker to perform drag and drop, zoom, etc.
A new accessibility button is located in the navigation bar. This allow users to quickly invoke context dependent accessibility features. This sits in the row with back and home buttons
People with dyslexia, low vision, learning new language… They can now use select to speak. part of talkback 5.2. Select element on screen and talkback will read it. It has a floating action button to enable.
In android o. read whole page, and advanced controls, word level highlighting, set up wizard.
manual testing: try your app with TalkBack and SwitchAccess.
if it is ok in talkback, it should be good for brailleback and select to speak
if it works with switch access, it should also work with voice access.