Published on March 20, 2014
Simplifying the Web Accessibility Test Lab Mitchell Evan and Kevin Chao JPMorgan Chase #csun14 #ATtestlab snipurl.com/ATtestlab
With limited resources, how do we support limitless diversity of AT users? • What we’re doing today • What we can do better
Two requests 1. Challenge your own assumptions. 2. Challenge me. How can we keep improving?
Simple for an organization =
Simple for a customer (client, etc.) =
It takes a lot of work to make it simple.
Browser Recommendations We have detected that you are using a browser which is not compatible with our application. Our application requires that you use Internet Explorer version 8.0 or greater Nice and simple for the organization!
BYOD: Bring Your Own Device
BYOC: Bring Your Own Combo hardware + browser + assistive tech
What goes into the combos? • Desktop and mobile operating systems (OS) • Browsers • AT software and hardware -- for vision, learning, and mobility • Versions • Configurations
Potential combos Windows: 1200 Mac: 150 Linux: 10 iOS: 12 Android: 5000 Symbian: 4
Conclusion: Give up. Thank you. Mitchell Evan @MitchellREvan Kevin Chao @KevinChao89
Diverse people use diverse technology Diversity matters.
Simulate diversity >
You can’t test all combos... ...but consider all of the potential combos, when you plan your testing.
You get to choose. The WCAG Working group and the W3C do not specify which or how many assistive technologies must support a Web technology in order for it to be classified as accessibility supported.
Web standards are essential… …but you still have to test. •Make sure it’s usable •For WCAG conformance, it must work in AT. Only accessibility-supported ways of using technologies can be relied upon for conformance. -- WCAG 2.0 (normative)
Quiz: What does “A 11 Y” stand for? 1) Accessibility 2) Affordability
Financial barriers Support by just one assistive technology (for a given disability) would not usually be enough, especially if most users who need it in order to access content do not have and cannot afford that assistive technology.
Principles 1. Make it affordable. 2. Support every disability group. 3. Include a free AT for each disability group. 4. Focus on popular, capable combos. 5. Browser versions: use the same list as the rest of your organization. 6. AT versions: Current minus 2 versions? Or current minus x years?
Put the principles into practice Principles Matrix Efficiencies
Choose your Big Matrix • Chop out combos that are irrelevant for your organization. • Expect customers to upgrade. • Define “incapable” combos closer to the cutting edge.
Survey: what do you use for testing? Org Test Suite or Support Principle Yahoo! NVDA, FF on PC; VO & Saf on Mac; VO & Saf on iOS; TalkBack & FF on Android. Spot check JAWS; Chrome Android. Latest versions. Affordable Intuit JAWS + IE, older and newer versions. NVDA lastest version. Firefox, Chrome, Safari latest versions. Capable: needs to work with ARIA. UC Berkeley Internal: latest versions only Providing AT directly to community
Survey: what do you use for testing? Org Test Suite or Support Principle Bank A Desktop screen readers, iOS, mobile keyboards Capable: work reasonably well with ARIA Bank B Desktop screen readers (first round plus spot check), iOS, Android Capable: work with older versions Pearson Screen readers (vision and dyslexia use cases), switch access, voice control, literacy aids, browser settings Support many groups
Which of these organizations did it the right way? Answer: All of the above
Prevent bugs in the first place • Train your managers, designers, and developers • Write standards-based code. Efficiencies
Pure time savings • Test UI components at the framework level. • Phase your testing. • Test two configurations a the same time. • Write custom-scripted automated tests. Efficiencies
Lower priority of some combos • Assume similar combos will give similar results; concentrate on combos that are more different from each other. • Bookend strategy: skip the middle version. Efficiencies
Accept some defects • Embrace “graded AT support” • If you write “good code” and it fails in one AT: “not my problem” Efficiencies
Reduce scope of testing • Deep test your framework. Anything that’s not framework, test more lightly. • With each release, rotate which combos you test with. Efficiencies
Reduce more drastically • Test the Accessibility API directly • Heuristic evaluation • Trust what you read on the web. • Let your customers test for you Efficiencies
Talk to your customers • On your accessibility page, be straightforward about what you do and don’t support. • If you offer live customer support, make sure they are trained.
Listen to your customers • Online feedback form • Customers submit issues directly to an issue tracking system
Future efficiency: Element-Level Support One way for authors to locate uses of a technology that are accessibility supported would be to consult compilations of uses that are documented to be accessibility supported. – WCAG “accessibility supported”
Crowdsourced element testing
Envision the result Crowdsource element testing Publish known issues Fix the frameworks Fix the Internet Users find what we missed Fix the AT, browser, or OS
It’s starting now • TPG Bug Bash: Tonight 5:30-6:30, Suite 3233 Harbor Tower • Saturday hack-a-thon: Launch the Open Accessibility Testing initiative
Discussion How can we simplify, yet test well? How do we advance quality and affordability? #ATtestlab snipurl.com/ATtestlab Mitchell Evan @MitchellREvan Kevin Chao @KevinChao89
Presentación que realice en el Evento Nacional de Gobierno Abierto, realizado los ...
In this presentation we will describe our experience developing with a highly dyna...
Presentation to the LITA Forum 7th November 2014 Albuquerque, NM
Un recorrido por los cambios que nos generará el wearabletech en el futuro
Um paralelo entre as novidades & mercado em Wearable Computing e Tecnologias Assis...
Simplifying the Web Accessibility Test Lab Session Information Session ID WEB-088 Date & Time Thursday, March 20, 2014 - 9:20 AM PST Location
Share Simplifying the Web Accessibility Test Lab. ... Presented 3/20/2014 at CSUN International Technology & Persons with Disabilities Conference. Text. 1.
Introduction to the Deque Showcase 2014: Web Accessibility: ... CSUN Universal Design Center ... Simplifying the Web Accessibility Test Lab: Web Accessibility:
CSUN 2014 参加に向けて ... Community Engagement and Gamification of Web Accessibility; ... What Can You Learn from a Usability Test; いよいよ ...
... CSUN International Technology & Persons with Disabilities Conference. ... Accessibility CSUN 2014 ... Simplifying the Web Accessibility Test Lab ...
Roadmap to WordPress Accessibility CSUN 2014 ... Simplifying the Web Accessibility Test Lab ... $10,000 Amaze Grant To Fix The Web Initiative At CSUN 2014;
Adobe is an active participant in W3C’s Web Accessibility ... include simplifying the process for ... Accessibility Test Lab ensuring that a ...
http://accessibility.mitsue.co.jp/ Web ... CSUN 2014 でも、触地図 ... Simplifying the Web Accessibility Test Lab;