Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Specify WAI-ARIA feature #14

Closed
mar10 opened this issue May 12, 2013 · 5 comments
Closed

RFC: Specify WAI-ARIA feature #14

mar10 opened this issue May 12, 2013 · 5 comments

Comments

@mar10
Copy link
Owner

mar10 commented May 12, 2013

Discuss and finalize this RFC:

https://github.com/mar10/fancytree/wiki/SpecAria

@mar10
Copy link
Owner Author

mar10 commented Mar 3, 2014

Closing RFC issues, because they should not appear as Open Issue.

This thread is still open for discussion!

@mar10 mar10 closed this as completed Mar 3, 2014
@mar10 mar10 added this to the 2.0.0beta milestone May 11, 2014
@woddel
Copy link

woddel commented Oct 18, 2016

hia all. yes, aria-compatibility is also a issue for a project we do for the university of basel, switzerland. we use fancytree in an important portal, but we get requests to be fully accessable and this is a stopping point for the moment. we would be very happy if this topic would be reevaluated... :)

@mar10
Copy link
Owner Author

mar10 commented Oct 18, 2016

Hi,

There is already a tree.aria option and some specification with open questions.
Are you able to help or contribute by testing with different clients or proposing markup enhancements?

@cksachdev
Copy link

In a sliding area, I have fancy tree for navigation. When the sliding area is collapsed, elements in fancytree shouldn't be read by screen reader. I have tried to add following on the main container

 jQuery("#tree_container").css("display","none");
 jQuery("#tree_container").attr("aria-hidden","true");

But the nodes are still getting a focus. Is there a utility method in fancytree to enable/disable accessibility as and when required?

cc: @mar10 @woddel

@mar10
Copy link
Owner Author

mar10 commented Nov 27, 2019

Please create a separate issue for this, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants