Accessibility Issue
|
Workaround
|
---|---|
Keyboard navigation
is not supported when you change preference options in the Preferences window.
A mouse is required to accomplish this.
|
No workaround available.
|
You cannot add an attachment
to a note with the keyboard alone.
|
No workaround available.
|
Items that are not available
(dimmed) are able to receive focus.
|
No workaround available.
|
Column sorting is not
possible with the keyboard.
|
No workaround available.
|
High-contrast themes
must be manually created.
|
No workaround available.
|
The software requires
that style sheets are enabled.
|
No workaround available.
|
When you use JAWS with
Google Chrome, many items are not read properly.
|
No workaround available.
|
When you use JAWS with
Google Chrome, table reading commands do not function properly with
many tables.
|
No workaround available.
|
When you use JAWS, extraneous
information is read for toolbar buttons.
|
No workaround available.
|
When you use JAWS, the
expand and collapse arrows do not identify what is being expanded
or collapsed on entity windows.
|
No workaround available.
|
When you use JAWS with
Google Chrome, you cannot read items under collapsible panels.
|
No workaround available.
|
When you use JAWS, the
Actions menu for entities is read as “Unlabeled zero button.”
|
No workaround available.
|
When you use JAWS, the
button for dismissing a notification is read as “Unlabeled
zero button.”
|
No workaround available.
|
When you use JAWS, calendar
edit fields are not sufficiently read, which does not allow screen
readers to provide information about what is being edited.
|
No workaround available.
|
When you use JAWS, the
informational, warning, and error messages displayed at the top of
the screen cannot be read.
|
No workaround available.
|