Page History

...

• A copy of JAWS screen reader software has been installed in the W92 QA test lab for use by WDA developers and QA.  This will allow basic unit testing of individual WDA components and screens.  It is not a replacement for full Accessibility testing by the IS&T Accessibility team.
• You can also install a demo version of JAWS on your own machine by downloading it from Freedom Scientific at http://freedomscientific.com/products/fs/jaws-product-page.asp** If you will be doing frequent testing with JAWS and want the fully licensed version, see Kevin Lyons or Mary Ziegler for instructions on tying to MIT's license server.
  • Here are the recommended settings when using JAWS with SAP Portal products (click to open doc).  For example,
    • For JAWS to work in WD4A, Virtual PC cursor must be turned off.
• SAP provides a Navigating with HotKeys doc (click here to open doc) to help navigate a screen via keyboard. 

Recommended Unit Test checks:

1. Testing that you can get to all UI elements using just the keyboard.  Check tab chain.
2. That JAWS is reading everything properly: did everything get read?
3. Screen changes:  make all dynamic changes below the cursor or announce that something has changed above the cursor.
4. Context changes must be communicated before hand.
5. Predictability of screen interaction. (Radio button click changes screen)
6. Using color for meaning: look for alternate ways to convey the meaning. Semantic color - badValueRed instead of Red - but this doesn't work for people who are color blind instead of blind.
7. Look for text that relies on visual cues (click the round button)
8. Check that color contrast is high enough (n/a if standard colors are used
9. Look out for flickering.
10. Timed responses – for accessibility, need to have ability to stop the timer; disable UI element time trigger
11. Cursor changes – setting in JAWS, announce % complete
12. Images of text – screen reader can’t read this, use tool tip (is decorative property can be set equivalent of empty alt tag)
13. Watch out for animations with meaning
14. That container elements contain accessibilityDescription - SAP recommends you put titles on complex elements, any element that is a container of things, tables (caption), groups, etc
15. Any application that has financial obligation/commitment, have ability to undo or confirm and submit.
16. Check for logical order of cursor tab changes.
17. Look for hotkeys enabled and that they move in a logical order
18. Provide alternatives for non-text fields (e.g. pie chart, graphic); provide link/table with same data – tables are accessible

...