Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use contentEditable for our hidden accessibility textArea
See original GitHub issueInvestigate into using contenteditable instead of a plain textArea for our hidden accessibility field.
It migh have performance implications, but it would allow us to have richer accessibility content on each line. Including line number, breakpoints etc…
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:12 (8 by maintainers)
Top Results From Across the Web
ARIA: textbox role - Accessibility - MDN Web Docs
The textbox role is used to identify an element that allows the input of free-form text. Whenever possible, rather than using this role, ......
Read more >How do I get the html from a contentEditable div to go inside of ...
Try: $('#clicker').click(function(){ var blog_post = $("#editable_div").html(); $('#hidden_text_area').val(blog_post); }).
Read more >The contenteditable attribute - HTML5 Doctor
Alternatively, you could copy the HTML content of your “contenteditable” into a hidden textarea through JavaScript. When the user would submit ...
Read more >ARIA14: Using aria-label to provide an invisible label ... - W3C
In other situations, elements can be given the attribute aria-label to provide an accessible name when the native HTML labeling element is not...
Read more >Help working with 'contenteditable'? - Learn - Elm Discourse
My main question is quite basic: Can you use a 'contenteditable' div much like ... textarea with some CSS and a hidden div...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
NVDA’s line number reading is not going to work in vscode, because vscode can only page n lines at a time to the hidden textarea used for accessibility.
@leonardder it’s a good question. Because our true editor is a bunch of html divs, spans and what not. It is not only text, as there can be inline decorations and other details. it is not a
textAreaor an input field and screen readers do not really work well with our editor HTML structure. Also the cursor is not the real cursor, the selection is not the real html selection and so on.I believe @alexdima the author of the editor considered this and he can probably explain in more detail if needed.