Curam SPM 6.0.5.2 not working with JAWS

1. A number of elements within CPIN/Cúram seem to assume/require mouse use, making keyboard navigation problematic with the universal shortcuts.

2. Inability to establish a cursor focus using CPIN modal dialogues - perhaps due to lack of the anchor tag required to navigate to a specific page location. Another example, the ESC key did not close a CPIN modal window.

3. Configured code tables require two steps involving 4-6 keystrokes (arrow keys), just to access the values - OOTB code tables might be fine but further testing would be required.

4. CPIN/Cúram lacks the necessary semantic mark-up which is critical to facilitating navigation across a web page with tabs, pages, context panels, menus, sections, pods, etc. A sighted person can mouse click directly on a selected location in the middle of the page but a screen reader needs the mark up to navigate to that same location.

5. Large volumes of data such as list pages or search results requiring extensive keying to move through the information. For example, 30 search results requiring 200 keystrokes.

6. Lack of consistency in design across the application, likely an issue for sighted users but compounded when relying on a screen reader. For example, menu locations are sometimes at the top of the screen or at the end of a line or under a section header and because they are all titled the same, it's near impossible to differentiate - the analogy being if you were to complete a form and all the fields are titled the same, it's hard to know which box you're filling in.

7. Inability to manage the cursor focus. For example, navigating from one tab to another or from the Family View to a person/case record. Specifically, with the Family View, when a sighted user mouse clicks the case, it opens in the background and they can keep reading the Family View but with the screen reader, the cursor focus jumps to the case... too bad if you wanted to read the rest of the Family View. With enough tabbing the user may eventually get there but it might be an awful lot of keystrokes.