You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2019/05/08 13:31:23 UTC

[GitHub] [couchdb-fauxton] Neurrone commented on issue #1197: Improve accessibility for screen reader users

Neurrone commented on issue #1197: Improve accessibility for screen reader users
URL: https://github.com/apache/couchdb-fauxton/issues/1197#issuecomment-490486565
 
 
   The MR only fixes low-hanging fruit that nevertheless has a big impact on the user experience. 
   
   These are some other problems I've found. If there's interest to fix them, I'll create separate issues. I don't know how much time I have to submit MRs, but can still help by pointing out how to fix them.
   
   * `<div>`s with `onClick` handlers are used pretty often, and should be replaced with `<button>`s or `<a>`s as appropriate. This has many advantages, including making them reachable when navigating with the tab key, and being natively understood by assistive technologies like screen readers. This might cause some visible changes in appearance, which should be possible to work around e.g with CSS resets.
   * The query options dialog doesn't use native elements for radio buttons, checkboxes etc, so have similar problems being not keyboard navigable and not exposing state (e.g, whether the option is checked) in a way that screen readers can understand. It is also rendered some distance away from the initial button which triggers the options dialog to appear when clicked, so it isn't obvious where the options are, unless the whole document is explored with a screen reader. Some possible solutions:
   	* Make the dialog modal, similar to the confirmation dialog that appears when you delete a database. The implementation in use currently works very well for screen readers, preventing movement outside the modal's contents, and automatically bringing focus to it when activated. I don't know if this would cause other problems though.
   	* Retain the current appearance, but move focus automatically to the first focusable control in the options dialog.
   * The popup menus that are opened by clickable buttons don't behave as expected when navigating by keyboard. Some of them also have a similar problem to the query options dialog, being rendered some distance away in the DOM from the control that activates them, instead of next to it.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services