Text field labels in Zotero application not accessible to screen readers #1411
Labels
Comments
dstillman
added a commit
that referenced
this issue
Apr 14, 2018
Set 'control' to the id of either the value label or the textbox, depending on whether the field is being edited. This causes NVDA to read the label associated with the textbox, but seemingly only the first time it's selected. Unfortunately NVDA also does some other unpleasant things, like reading a description from the duplicate-merging pane, which isn't the active element in the deck, and reading the entire text, including all field labels, of the item box) I'm not sure how much we can improve this until we're on Electron. VoiceOver doesn't read the textbox's label either, even though it does so in the bookmarks window in Firefox. Maybe things have improved since Firefox 52, so we can text again after upgrading to Firefox 60. Addresses #1411
fbennett
pushed a commit
to Juris-M/zotero
that referenced
this issue
Apr 15, 2018
Set 'control' to the id of either the value label or the textbox, depending on whether the field is being edited. This causes NVDA to read the label associated with the textbox, but seemingly only the first time it's selected. Unfortunately NVDA also does some other unpleasant things, like reading a description from the duplicate-merging pane, which isn't the active element in the deck, and reading the entire text, including all field labels, of the item box) I'm not sure how much we can improve this until we're on Electron. VoiceOver doesn't read the textbox's label either, even though it does so in the bookmarks window in Firefox. Maybe things have improved since Firefox 52, so we can text again after upgrading to Firefox 60. Addresses zotero#1411
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Testing with Zotero 5.0.34 under Windows, using the JAWS screen reader (similar results would probably be observed using the free/open-source NVDA screen reader):
If I open an item in my library and use the tab key to move between the controls that appear, none of the text field labels is identified by the screen reader automatically, as it should be. The usual reason for this is that the "accessible name" property in the accessibility API isn't being set, due to a coding error in the application.
The text was updated successfully, but these errors were encountered: