Open cben opened 9 years ago
Discussion of CM accessibility for FireFox devtools integration: https://bugzilla.mozilla.org/show_bug.cgi?id=816756 Mostly discusses RTL issues, some mention of screen readers but I didn't quite understand CM's status. Before CM landed FireFox used Orion which got most accessibility from using contentEditable.
Fork with CM accessibility investigation: https://bgrins.github.io/codemirror-accessible/
How to do accessible textarea option:
https://github.com/jsbin/jsbin/issues/936
(sorry github, I don't want to spam that issue)
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/ but I'm thinking (H)elp and (N)ew would do the job better for now.
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/