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
Inline boundaries improvements #207
Comments
I love the feature and I think it greatly helps understanding where you're typing. However, quickly testing with Safari 10 + VoiceOver, the link boundary gets read out as: One option could be the one mentioned by @spocke on Slack:
When navigating by characters or words, screen readers already announce |
@afercia Did some investigations into this one. In order to keep the caret from normalizing into the anchor when being inside/outside we need to insert something that keeps the browser from doing it's default thing. We use zero width non breaking spaces for that it's basically an invisible character that is no longer used for anything except for BOM signatures in documents. These characters seems to be ignored by Jaws but spoken by VoiceOver and NVDA. I tried to work around this in various ways:
So to sum this up it's complicated. :) |
We fixed the items listed in this ticket. So I'm closing this one. |
There are various small issues with the new link/code boundaries logic that needs to be corrected.
The text was updated successfully, but these errors were encountered: