-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add proposed content to SC problematic for closed functionality #173
Conversation
✅ Deploy Preview for wcag2ict ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good with those changes - thanks Mary Jo for the hard work
Once the proposed content is approved and incorporated, the editor's note no longer applies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maryjom you were right, I forgot to hit submit on this review yesterday. Before our next Task Force call I will answer the questionnaire with links to these feedback items.
See discussion on the [introductory paragraph](https://www.w3.org/2023/07/27-wcag2ict-minutes.html#t05).
Also updated the intro to the Key terms section to list this new term.
This has been superseded by multiple other PRs to handle small groups of approved bullets. |
This PR is to include proposed new and changed content for the SC Problematic for Closed Functionality appendix so the sub-group (and eventually the full TF) to review.
Note: 1.4.10 Reflow was already added using another PR to ready the document for FPWD publication.
NOTE: This is an outdated PR used for our first survey on these proposed updates (that closed in Sept.). Changes that we consensed on have been merged using other PRs. Newer surveys are integrating comments from the original survey into text proposed in the survey directly. Once all items are agreed, this PR will simply be closed without merge and any edits to the section we agree upon will be merged in using a different, clean PR where I don't have to manage a bunch of merge conflicts.