Testing for Web Accessibility John Slatin Access U

Testing for Web Accessibility John Slatin Access U May, 2009 Jim Thatcher http: //jimthatcher. com jim@jimthatcher. com Accessibility Consulting Austin, Texas May 11 -12, 2009

Resources p These slides at n n Power. Point testing. ppt n p http: //jimthatcher. com/testing Resources in order of appearance there too This class is very much a resource list! May 11 -12, 2009 Testing for accessibility 2

Questions Please ask questions or p … Make comments at any time p … If it isn’t clear to you – ASK! p May 11 -12, 2009 Testing for accessibility 3

Outline p p p Testing for Web Accessibility – Means? Standards and Guidelines Testability n Contrast example Automatic Testing tools n Free tools n Commercial Tools n Testing tool report Tools that assist with Human Review Lets test a page May 11 -12, 2009 Testing for accessibility 4

Testing for Web Accessibility: Web resources are accessible if people with disabilities can use them as effectively as non-disabled people (UT Accessibility Institute) p So testing means user testing with disabled and nondisabled people? p Instead there are “standards and guidelines” against which we can test May 11 -12, 2009 Testing for accessibility 5

Standards and Guidelines p WCAG 1. 0 Web Content Accessibility Guidelines 1. 0 n p Section 508 Standards n p http: //w 3. org/TR/WCAG 20/ Section 508 refresh See Section 6 n p http: //www. access-board. gov/508. htm WCAG 2. 0 n p http: //w 3. org/TR/WCAG 10 http: //www. access-board. gov/sec 508/refresh/report/ IBM web guidelines n http: //ibm. com/able/guidelines/web/accessweb. html May 11 -12, 2009 Testing for accessibility 6

Priority Section 508 p n 16 provisions all priority one! WCAG 1. 0 14 guidelines p n 65 Checkpoints – 16 Priority 1, 30 Priority 2, 19 Priority 3 checkpoints WCAG 2. 0 12 guidelines p n 56 Success Criteria – 18 Level A, 17 Level AA, 21 Level AAA success criteria 508 Refresh – who knows – p n May 11 -12, 2009 Public comment 1 Q 2010 – at the earliest Testing for accessibility 7

WCAG 2 – testability is key p All WCAG 2. 0 success criteria are written to be testable. While some can be tested by computer programs, others require human testers for part or all of the test. p My favorite testability example … Contrast May 11 -12, 2009 Testing for accessibility 8

Testability - Example p WCAG 1. 0 Priority 2: 2. 2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. n n May 11 -12, 2009 “Sufficient contrast”? “Color deficits”? Testing for accessibility 9

Flickr – black and white May 11 -12, 2009 Testing for accessibility 10

Testability - Contrast p WCAG 2. 0 Level AA: 1. 4. 3 Text and images of text have a contrast ratio of at least 4. 5: 1 … 3: 1 for larger text (18 pt or 14 pt bold) (Level AA) p Contrast Ratio? p Tools will answer that question – n http: //www. paciellogroup. com/resources/contrastanalyser. html (also pull down from toolbar) n Try that with http: //Flickr. com n Another to check out: http: //Graybit. com May 11 -12, 2009 Testing for accessibility 11

Testable? Automatic tests? p Testable by a computer vs. requiring human judgment p Only ~25% of accessibility errors can be detected by computers (Mike Cooper) p Many claim compliant/accessible because no errors reported by testing tool p Testing all for Section 508 Standards discussed n http: //jimthatcher. com/testing 1. htm May 11 -12, 2009 Testing for accessibility 12

p A current example of testing … Recovery. gov complies with all of the automatic checkpoints of the Section 508 Accessibility Guidelines, and has been manually verified for nearly all of the manual checkpoints. This compliance has been tested using Watchfire Web. XACT program. (To be in America) p Accessibility of Recovery. gov http: //jimthatcher. com/recovery. htm May 11 -12, 2009 Testing for accessibility 13

Automatic tests p p p p (about 12 tests) (3) Missing alt on <img>, <area>, or <input> with type=“image” (3) Empty alt on <img> in <a> without text, same for <button> or <input> with type=“image” (1) Form control with no title or label (or empty) (2) No title on frame or iframe (1) Sever-side image map (image link with ismap) (1) Missing lang attribute for page (1) [No HTML headings (h 1, h 2, …) on page] May 11 -12, 2009 Testing for accessibility 14

Testing tools (outline) p Automatic web accessibility testing p Human Review – tools that assist p User testing n n n May 11 -12, 2009 Beyond the scope of this class But check out Shawn Lawton Henry’s p Just Ask: Integrating Accessibility Throughout Design p The whole book is there One of 11 co-authors of Web Accessibility: Web Standards and Regulatory Compliance Testing for accessibility 15

Automatic Testing (outline) p Automatic n n Free 1 -page tools More general free tools Desktop tools Enterprise tools p Tools n n n May 11 -12, 2009 web accessibility testing lists: http: //www. w 3. org/WAI/ER/tools/complete http: //www. colostate. edu/Dept/ATRC/tools. htm http: //www. webaim. org/articles/tools/ Testing for accessibility 16

Some Free 1 -page tools on the web p Cynthia. Says (Hi. Software) n http: //cynthiasays. com p Bobby is gone! p Truwex (Erigami) n n p http: //checkwebsite. erigami. com/accessibility. html New kid on the block 2 years ago Worldspace by Deque – New Kid this year n n p http: //worldspace. deque. com For Google Toolbar, http: //tinyurl. com/9 h 7 elc Sample file http: //jimthatcher. com/testing/testfile. htm May 11 -12, 2009 Testing for accessibility 17

Sample File for Testing p http: //jimthatcher. com/testing/testfile. htm Cynthia Truex Issue Worldspace 1 Server-side map Yes Yes 2 Two input fields – label but same id No No No 3 Empty alt on image link No Yes 4 No alt on image (duh) Yes Yes 5 title attributes on input fields (good) No Yes 6 No alt on image button Yes No Yes 7 No alt in image map area Yes Yes 8 Iframe with no title No Yes May 11 -12, 2009 Testing for accessibility 18

The Truex Map – very cool May 11 -12, 2009 Testing for accessibility 19

More General Free Tools p The n WAVE (Utah State) (version 4. 0) http: //wave. webaim. org p AChecker http: //www. atutor. ca/achecker/ (WCAG 2. 0) p Functional n Accessibility Evaluator (U of Ill) http: //appserv. rehab. uiuc. edu/fae May 11 -12, 2009 Testing for accessibility 20

Desktop Commercial Tools p Ramp ($69 -$1499) n p http: //www. deque. com In. Focus ($1795) n http: //www. ssbtechnologies. com May 11 -12, 2009 Testing for accessibility 21

Enterprise Tools (expensive) p Web. King by Parasoft n http: //parasoft. com/jsp/products/home. jsp? product=W eb. King p Rational Policy Tester by IBM n n p (was Web. XM by Watchfire) http: //tinyurl. com/9 hao 4 g Worldspace by Deque n http: //deque. com/products/ May 11 -12, 2009 Testing for accessibility 22

Six Commercial Tools, A Comparison p Chapter 13 – Web Accessibility: Web Standards and Regulatory Compliance … n p Forty “issues” n p http: //jimthatcher. com/step/new Based on 70 files n p See http: //jimthatcher. com/testing. htm. http: //jimthatcher. com/step/new/stepfiles. htm Example – how the tools deal with link text May 11 -12, 2009 Testing for accessibility 23

Link text - WCAG 1. 0 p WCAG 1. 0 13. 1: Clearly identify the target of each link. (P 2) (Not 508 requirement) p Interpreted to mean good link text or title attribute on anchor element. It is testable – evaluators would usually agree on “good link text. ” q May 11 -12, 2009 Testing for accessibility 24

Link text – automatic tests p Raise errors (or warnings) for Common phrases, “more, ” “click here, ” “more …, ” “details” etc. n List of such is editable with several tools. p Inadequate phrase like “click here” but with title attribute – should pass p Same link text different href – should fail without title. Extreme case - Empty link text or spaces for link text is error without title. p May 11 -12, 2009 Testing for accessibility 25

Link text – WCAG 2. 0 p 2. 4. 4 The purpose of each link can be determined from the link text and its programmatically determined link context. (A) p 2. 4. 9 The purpose of each link can be identified from the link text. (AAA) May 11 -12, 2009 Testing for accessibility 26

Testing tools and link text OK Bobby In. Focus LIFT Ramp W-King W-XM 21. “Click here” 4 yes no no yes yes 22. Image link with empty alt-text 4 yes no yes 23. Image link with spaces for alt-text 5 yes no yes yes 24. Link with text and image with empty alt-text 3 no no yes 25. “Click here” plus title 2 no no no yes no Test Details at http: //jimthatcher. com/testing 4. htm May 11 -12, 2009 Testing for accessibility 27

Testing tools - Results Total Bobby Correct Results 40 28 In. Focus 23 LIFT Ramp W-King W-XM 27 38 34 Details at http: //jimthatcher. com/testing 4. htm May 11 -12, 2009 Testing for accessibility 28 26

Human Review p Human Review n Notepad (source code) n Screen Readers and other AT n Special issue tools (like contrast) n Toolbars (the best news) n Jim’s Favelets p (User May 11 -12, 2009 testing – Beyond scope Testing for accessibility 29 )

Assistive Technology p Testing with assistive technologies n HPR (IBM) p No longer available n JAWS (Freedom p http: //www. hj. com Scientific) n Window-Eyes (GW Micro) p http: //www. gwmicro. com n Fangs p May 11 -12, 2009 http: //www. standards-schmandards. com/projects/fangs/ Testing for accessibility 30

Toolbars - for anyone interested in accessibility p Web accessibility toolbar - The Paciello Group n http: //www. paciellogroup. com/resources/wat-ieabout. html Best thing that has happened for accessibility – and a toolbar for Firefox p Web Developer Extension for Firefox n http: //chrispederick. com/work/webdeveloper May 11 -12, 2009 Testing for accessibility 31

IBM Accessibility Testing p Matt King started monitoring all of IBM. com (13 million pages) in 1999. Reports to Mgrs and VPs p Five Years later – Detectable errors way down. p Accessible? p Need Human Review – but too many pages p Idea: use sampling – like a political poll –evaluate sample pages and conclude results for whole site p http: //www. research. ibm. com/journal/sj/443/king. html p May 11 -12, 2009 Testing for accessibility 32

Human Review for IBM p Needed time per page around 3 -5 minutes p The toolbars don’t do what testing tools do. n Need value of software testing tools in the human review (e. g. , no alt attribute or no form label) Don’t make me look for these. p Simplify human evaluation – scoring (AIR) p My evaluation techniques (modified from Toolbar) n http: //jimthatcher. com/favelets (includes description of the process) May 11 -12, 2009 Testing for accessibility 33

The Testing Process I use p Sample n report http: //jimthatcher. com/testing/Sample-accessibility. doc p Lets look at some of the same pages – http: //www. sec. gov! p It is a mix of Web Accessibility Toolbar and “Jim’s favelets” p The way to do accessibility testing May 11 -12, 2009 Testing for accessibility 34

Thanks! Thanks for being here p I can be reached at p n p jim@jimthatcher. com You can contact Knowbility n knowbility@knowbility. org May 11 -12, 2009 Testing for accessibility 35