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

Accessibility #37

Open
roman01la opened this issue Apr 2, 2015 · 3 comments
Open

Accessibility #37

roman01la opened this issue Apr 2, 2015 · 3 comments

Comments

@roman01la
Copy link

I'm wondering if this is actually to be used in prod? Do you consider to work on accessibility for this? Replicating DOM inside of canvas tag seems somewhat a good practice, better than nothing.
This is related to similar issue on react-canvas.

@PixelsCommander
Copy link
Owner

It does not replicate DOM it replaces it visually, but DOM is at place and is clickable and selectable. You do not see selection highlight (which will be fixed), but you still can select and copy/paste. So lets keep this issue and close when selection highlight will be imlemented

@roman01la
Copy link
Author

True, there's no system outline on focusable elements.

@MrYellowMan
Copy link

I know a simple thing to hide the DOM elements by using javascript old way.

It works like this: page loads>DOM is taking it's time to generate>Canvas already made and should know whats inside to replace>JavaScript hides the DOM Elements if you did this on a onload page it should work as well.

Down-side: you'll have to hide all the packs you make in a different tag.

JS old way: we are used of using *.style.display="none"; for hidding elements that are not needed at moments that tou don't use them.

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

No branches or pull requests

3 participants