...
- 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.
...
- TextView versus InputField-ReadOnly
- For text fields that will always be read-only, developers should use TextView (not InputField-ReadOnly).
- For text fields that will sometimes be editable but under other conditions read-only (e.g. HSA Details screen), developers would prefer to use InputField-ReadOnly.
- For screens that have a mix of field types, group things accordingly. Keep TextView together or InputFields together for better visual user experience. Try not to alternate or mix types.
- For confirmation screens and button order, follow the SAP standard of ordering the buttons in order of "Yes/No".
- For pop-ups that contain variable length texts .....<Mark/Carolyn looking at this>
- For search helps ..... <tbd> Search Helps, see rule Accessibility rule #14 above.