WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: which are the things should keep in mind while doing content testing?

for

From: Meacham, Steve - FSA, Kansas City, MO
Date: Jun 30, 2017 1:28PM

This is what I provide to our web developers and testers (hyperlinks are mostly internal, so won't work):



How-to manually inspect HTML pages for Section 508 compliance<https://wiki.tools.fsa.usda.gov/display/508/How-to+manually+inspect+HTML+pages+for+Section+508+compliance>

As a HTML author, developer, or tester, you may feel (mistakenly) that Section 508 compliance testing has to be much more demanding, time consuming, and complicated than it really turns out to be. The testing strategy proposed below is intended to serve as a working approach to evaluate accessibility against Web Content Accessibility Guidelines (WCAG) 2.0<https://wiki.tools.fsa.usda.gov/display/508/Web+Content+Accessibility+Guidelines+%28WCAG%29+2.0> success criteria without requiring a technical background in accessibility or assistive technology.

This procedure is intend to be simple to use and produce results that are consistent with repetitive testing by any tester. In other words, the results are not subjective and the testing and its results may be easily replicated by anyone.

The core procedure does not require special software or specialized skill to perform. HTML inspection requires a knowledge of HTML and some technical acumen. The use of assistive technology is specialized skill and is best performed by an individual who regularly depends on it. When performed fully, this testing procedure can predict, with nearly 100% accuracy, the usability of the software application by persons of all abilities. In addition, the testing results that a tester can document when following this procedure can serve as a comprehensive description of what exact changes must be made to software in order to make it accessible, as well as compliant with Section 508.

Step-by-step Core Procedure (current)

1. Visually inspect each page, and

a. Note any use of color that is the only means of conveying information, (Success Criteria 1.4.1: Use of Color<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.4.1%3A+Use+of+Color>)

b. Note any instructional text that relies solely on sensory characteristics to direct the user; (Success Criteria 1.3.3: Sensory Characteristics<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.3%3A+Sensory+Characteristics>)

c. Note any logical divisions or sectioning of the page that lack descriptive headings; (Success Criteria 2.4.1: Bypass Blocks<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.1%3A+Bypass+Blocks>)

d. Note any non-English language on the page that are not proper names spelled with initial capital letters; (Success Criteria 3.1.2: Language of Parts<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.1.2%3A+Language+of+Parts>)

e. Note any moving, blinking, scrolling, or auto-updating information that cannot be paused, stopped, or hidden; (Success Criteria 2.2.2: Pause, Stop, Hide<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.2.2%3A+Pause%2C+Stop%2C+Hide>)

f. Note any flashing text or images; (Success Criteria 2.3.1: Three Flashes or Below Threshold<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.3.1%3A+Three+Flashes+or+Below+Threshold> or Success Criteria 2.3.2: Three Flashes<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.3.2%3A+Three+Flashes>)

g. Note any hyperlinks that would be insufficiently descriptive if viewed in isolation; (Success Criteria 2.4.4: Link Purpose (In Context)<https://wiki.tools.fsa.usda.gov/pages/viewpage.action?pageIde311581> or Success Criteria 2.4.9: Link Purpose (Link Only)<https://wiki.tools.fsa.usda.gov/pages/viewpage.action?pageIde311591>)

h. Note any headings or labels that are insufficiently descriptive given the context of the current page's title and any enclosing section's heading; (Success Criteria 2.4.6: Headings and Labels<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.6%3A+Headings+and+Labels>)

i. Note any navigation or UI elements that appear on other pages that is not identical in its arrangement (Success Criteria 3.2.3: Consistent Navigation<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.2.3%3A+Consistent+Navigation>) and identification; (Success Criteria 3.2.4: Consistent Identification<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.2.4%3A+Consistent+Identification>)

j. Note any scenarios where a user would be unable to determine what they could or should do, or where they are, in the application or any active workflow. (Success Criteria 2.4.5: Multiple Ways<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.5%3A+Multiple+Ways>)

2. Operate each page, and

a. Use the browser to resize the text on the page, and only the text. Enlarge it up to 200% and note any instances where this makes the content illegible; (Success Criteria 1.4.4: Resize text<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.4.4%3A+Resize+text>)

b. If some of the text didn't resize, right click on it to determine if it is actually image, and note if it is; (Success Criteria 1.4.5: Images of Text<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.4.5%3A+Images+of+Text>)

c. Traverse the page using the keyboard's TAB button and verify that all active user interface elements are usable using the keyboard alone; (Success Criteria 2.1.1: Keyboard<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.1.1%3A+Keyboard>)

d. Note any keyboard traps where the focus gets stuck or goes into a loop that prevents the keyboard from navigating away from the trap; (Success Criteria 2.1.2: No Keyboard Trap<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.1.2%3A+No+Keyboard+Trap>)

e. Note whenever the visual focus indicator does not flow in a natural and logical order; (Success Criteria 2.4.3: Focus Order<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.3%3A+Focus+Order>)

f. Note whenever the focus indicator is missing or appears in multiple places at the same time; (Success Criteria 2.4.7: Focus Visible<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.7%3A+Focus+Visible>)

g. Note whenever the act of shifting focus initiates a change of context or side effect; (Success Criteria 3.2.1: On Focus<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.2.1%3A+On+Focus>)

h. Note the absence of skip navigation (visible or invisible) or the ability to bypass any repetitive blocks of content; and (Success Criteria 2.4.1: Bypass Blocks<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.1%3A+Bypass+Blocks>)

i. Note any elements that, when changed, cause a change of context or side effect, but lack any notification to the user of this effect before they took the action (Success Criteria 3.2.2: On Input<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.2.2%3A+On+Input>)

3. Enter erroneous information into any data entry fields and controls, inspect the error messages, and

a. Note any error messages that fail to identify the item that is in error in text; (Success Criteria 3.3.1: Error Identification<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.3.1%3A+Error+Identification>)

b. Note any errors where the system should be able to suggest a correction, but doesn't; and (Success Criteria 3.3.3: Error Suggestion<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.3.3%3A+Error+Suggestion>)

c. On pages that allow the updating or removal of legal or financial data, ensure that the change is either reversible, checked, or confirmed. (Success Criteria 3.3.4: Error Prevention (Legal, Financial, Data)<https://wiki.tools.fsa.usda.gov/pages/viewpage.action?pageIde311624>)

Extended Procedure to Inspect the HTML to verify semantic markup



HTML inspection requires a knowledge of HTML and some technical acumen, but no special tools.

1. Using the Developer Tools in Internet Explorer, Developer Firefox, or Google Chrome,

a. Note any tables that aren't tables; (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)

b. Any headings that aren't headings; (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)

c. Any labels that aren't labels; (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)

d. Captions that aren't captions; and (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)

e. Any content that originates from CSS ":before" or ":after" specifiers. (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)

Extended Procedure to test operability with Assistive Technologies and alternate browsers



The use of assistive technology is specialized skill and is best performed by an individual with a disability who regularly depends on it.

1. Operate the page with a Screen Reader, FireEyes II's SimuAT, and alternate browsers, and

a. Note any unnatural reading sequences; and (Success Criteria 1.3.2: Meaningful Sequence<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.2%3A+Meaningful+Sequence>)

b. Note any corruption or illegible presentation details. (Guideline 4.1: Compatible<https://wiki.tools.fsa.usda.gov/display/508/Guideline+4.1%3A+Compatible>).
I hope this helps...
Steve Meacham