Intuit’s Accessibility Champion program enables everyone to become a champion and a roadmap for people to become leaders. This was created to celebrate people making contributions towards accessibility. It highlights people via employee profile badges, congratulatory spotlights, and notifications to managers about their commitment. The program emphasizes customer empathy, disability etiquette, and accessible product design and development.
This post shares the Intuit Accessibility Champion process and includes resources and descriptions for your company to adopt the program. Intuit’s program has evolved continually, tasks have been added, made optional, and resources updated. Use this as a baseline and modify it to represent what is important for your organization. For instance, a restaurant may focus on customer interactions and not web application development.
Intuit’s program is hosted on QuickBase, an enterprise database program. It could easily be set up for Google Forms or your preferred platform. Data metrics has been a key to success, so use a solution that lets you filter champions by role, location, manager, etc.
Volunteering with a disability organization is an incredible opportunity to gain deep empathy for your customers. You can make a sincere impact by sharing your time and resources. The following list was created for fellow Intuit Accessibility Champions to find nearby organizations. Please leave your favorite organization in the comments.
There’s a lot of times when you need to find out which item on a page has focus. This is especially tricky when controlling focus as you move in and out of modals and components. Here’s how you can get the object with focus on a web page.
open inspector and choose the console tab.
This will return the element that currently has focus
This site crashed a few months ago really, really, really hard. It looks like it may have been hacked and then exploded when trying to do an update of the plugins and such.
Fortunately, the folks at Dreamhost were able to help me do a complete restore of the site.
Also, I noticed it came back with a theme from around 2006 with valid XHTML. Digg This!
It’s kind of fun to view the source and remember some of the old techniques. Notice this IE6 comment.
<p id=”iewarning”>Sorry, this site is for advanced CSS programming. As such, it is not optimized for IE6. Please visit this site with <a href=”http://www.mozilla.com“>Firefox</a>, <a href=”http://www.opera.com“>Opera</a>, <a href=”http://wwww.mac.com“>Safari</a>, or another modern browser. Microsoft has recently released a beta version of Internet Explorer 7, you may even want to try that for a better internet experience in general.</p>
I came across a bizarre experience while testing a Styled-Component prototype with VoiceOver and Chrome. This simple panel had an H2 in the code, but I couldn’t navigate to it with the screen reader. I opened the accessibility inspector in Chrome and sure enough, the H2 had no semantics. It was being rendered to the Accessibility API as if it was a div.