-
Notifications
You must be signed in to change notification settings - Fork 256
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
Change on Request update for issue #738 #754
Conversation
Hi @alastc
This one has exactly the same problem, you tell here "people unable to detect the change are less likely to become disoriented" and "people not realizing that the context has changed are less likely to become disoriented" While it is more likely (if yout not checking the SC normative text at the top. The part "less likely disoriented if they make the change themselves" is the key here |
Hi Jake, I'm sorry, I'm not getting what you mean, could you provide a text update to that line? |
SC: "Changes of context are initiated only by user request or a mechanism is available to turn off such changes." One Benefit: It was: (and stand alone may be misinterpreted)
Now it is: (and stand alone may still be misinterpreted)
Make it:
|
@alastc suggest that instead of leaving this to linger, we proceed with it? I believe the suggested rewording (from my suggestion) may be sufficient to address potential confusion. |
merged my suggested simplification/rewording. if that was too rash, please back it out again |
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
need to check why the netlify preview failed there...some extra conflict somewhere? |
Discussed on TF call
Discussed on backlog call 9/6. |
Closes #738