Upgrade StorageWCAG & Accessibility: Unlabeled author buttons in an item's information tab
This is an accessibility problem with a suggested solution .
OVERVIEW
A user relies on the JAWS screen reader. They are in the Zotero 6.0.22 Item Pane and in Information tab. The user is reviewing the information of an article (perhaps to correct spelling mistakes).
The user starts with the keyboard focus on the title edit box and presses tab until they get to the abstract field.
For sighted people doing this task, we see in the visual interface that they are moving through author fields. The elements are grouped visually so we know they all are related to the author.
The issue is that this visual grouping isn't conveyed in the aural interface and so it creates ambiguity and demands more cognitive resources, will take longer, and could cause more mistakes.
See also, WCAG 2.0 Success Criteria 1.1.1
CURRENTLY: JAWS Behavior
USER PRESS TAB KEY
JAWS: List box, Horizontal
TAB KEY
JAWS: Blake edit combo Supports AutoComplete
TAB KEY
JAWS: Dylan edit combo Supports AutoComplete
TAB KEY
JAWS: Switch to single field Button
TAB KEY
JAWS: Delete Button
TAB KEY
JAWS: + Button
TAB KEY
JAWS: Abstract edit
The problems: The inputs aren't labelled to sufficiently support exclusive reliance on the aural interface.
SUGGESTED IMPROVEMENTS: JAWS Behavior.
Give inputs more meaningful labels
JAWS: Author type, List box, Horizontal
TAB KEY
JAWS: Blake, author last name, edit combo Supports AutoComplete
TAB KEY
JAWS: Dylan, author first name, edit combo Supports AutoComplete
TAB KEY
JAWS: Switch author names fields into a single field Button
TAB KEY
JAWS: Delete previous author, Button ("previous" is an index that indicates that delete applies to previous author and not the following one.)
TAB KEY
JAWS: add author, Button
TAB KEY
JAWS: Abstract edit
OVERVIEW
A user relies on the JAWS screen reader. They are in the Zotero 6.0.22 Item Pane and in Information tab. The user is reviewing the information of an article (perhaps to correct spelling mistakes).
The user starts with the keyboard focus on the title edit box and presses tab until they get to the abstract field.
For sighted people doing this task, we see in the visual interface that they are moving through author fields. The elements are grouped visually so we know they all are related to the author.
The issue is that this visual grouping isn't conveyed in the aural interface and so it creates ambiguity and demands more cognitive resources, will take longer, and could cause more mistakes.
See also, WCAG 2.0 Success Criteria 1.1.1
CURRENTLY: JAWS Behavior
USER PRESS TAB KEY
JAWS: List box, Horizontal
TAB KEY
JAWS: Blake edit combo Supports AutoComplete
TAB KEY
JAWS: Dylan edit combo Supports AutoComplete
TAB KEY
JAWS: Switch to single field Button
TAB KEY
JAWS: Delete Button
TAB KEY
JAWS: + Button
TAB KEY
JAWS: Abstract edit
The problems: The inputs aren't labelled to sufficiently support exclusive reliance on the aural interface.
SUGGESTED IMPROVEMENTS: JAWS Behavior.
Give inputs more meaningful labels
JAWS: Author type, List box, Horizontal
TAB KEY
JAWS: Blake, author last name, edit combo Supports AutoComplete
TAB KEY
JAWS: Dylan, author first name, edit combo Supports AutoComplete
TAB KEY
JAWS: Switch author names fields into a single field Button
TAB KEY
JAWS: Delete previous author, Button ("previous" is an index that indicates that delete applies to previous author and not the following one.)
TAB KEY
JAWS: add author, Button
TAB KEY
JAWS: Abstract edit