[
https://issues.apache.org/jira/browse/QUARKS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375493#comment-15375493
]
ASF GitHub Bot commented on QUARKS-201:
---------------------------------------
GitHub user home4slc opened a pull request:
https://github.com/apache/incubator-quarks/pull/166
QUARKS-201 screen reader text
Added additional aria-labels and hidden content to enable screen readers to
successfully navigate the console.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/home4slc/incubator-quarks
quarks-201-screen-reader
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-quarks/pull/166.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #166
----
commit eb417e8744a3cfadade326576fe6f301d1658ceb
Author: Susan L. Cline <[email protected]>
Date: 2016-07-13T18:26:24Z
QUARKS-201 screen reader text
----
> Make the quarks console keyboard navigible
> ------------------------------------------
>
> Key: QUARKS-201
> URL: https://issues.apache.org/jira/browse/QUARKS-201
> Project: Quarks
> Issue Type: Bug
> Components: Console
> Reporter: Susan L. Cline
> Assignee: Susan L. Cline
>
> I think it's important that the console can be navigated with only the
> keyboard. My thoughts are for the 'View all oplet properties' table that it
> be keyboard accessible as well since the graph itself can not be made
> accessible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
