-
Notifications
You must be signed in to change notification settings - Fork 46
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 #60
Comments
Discussion of CM accessibility for FireFox devtools integration: Fork with CM accessibility investigation: How to do accessible textarea option: |
http://ux.stackexchange.com/q/39868/47564 advice:
|
Acesskey "standards" and discussion whether they're good or harmful: http://www.standardaccesskeys.com/SAK2014/, http://www.hobo-web.co.uk/uk-gov-access-keys/ |
accesskey
works, not sure how to make it discoverable.<nav>
etc. to convey site structure.The most central question is whether CodeMirror content is even visible to screen readers?
Even if yes, and even if it's is conveniently editable, it probably wouldn't hurt to serve initial content over HTTP to people/spiders without javascript, and to allow fallback to textarea/form submission (#7).
<h1>
and not just visual styling like<span class="heading-1">
.<a>
(or at least<span href=...>
) links! Important both for accessibility and link juice.<h1>
etc. within CodeMirror (viarenderLine
hook, with CSS overrides like.CodeMirror .h1 { display-style: inline}
?).These is a harder problem that CM flattens logically nested structure like
# H1 *span* H1
into adjacent spans. Probably acceptable(?).Another part is math.
There are surely other aspects...
Testing tools: http://www.wat-c.org/
The text was updated successfully, but these errors were encountered: