-
Notifications
You must be signed in to change notification settings - Fork 70
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
"Programmatically Determined Link Context" definition is too broad #2176
Comments
@carlosapaduarte check if there is an "universal" objective of sentence |
It's worth noting that AT/UA support can be rather inconsistent for the situation pointed out by @Jym77. For instance, when using VO + Chrome, pressing VO+S to announce the sentence results in it reading "about bar" regardless of whether it's the first or second "read more." However, when using VO + Safari, pressing VO+S correctly reads the sentence and its context. |
CG decision (April 25th): make more test of AT/UA, then if the problem is generic, open issue with WCAG. |
I've created test cases and the results are provided below.
Outcome:
It appears that sentence support, which seems to be lacking in NVDA, isn't consistently reliable even when available. I plan to bring up this issue on the WCAG GitHub in the next few days. |
The definition of Programmatically Determined Link Context includes all the containing paragraph (or block ancestor). This means that links inside the same paragraph cannot be disambiguated by their sentence, which is part of the note in the WCAG definition of programmatically determined link context:
So,
fails the rule, but arguably passes the SC (not the best practice, but still correct) because the sentence provides the context.
The text was updated successfully, but these errors were encountered: