-
Notifications
You must be signed in to change notification settings - Fork 4
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
WCAG2ICT Project: Update sections - Comments on Definitions in WCAG 2.0 Glossary in Appendix A & sub-sections #22
Comments
Need to determine if any of the new terms are used only in AAA requirements and list them in the section Glossary Items Used only in AAA Success Criteria.
The list of new terms in WCAG 2.1:
NOTE: Definitions that are ONLY used in Level AAA Success Criteria Don't do any interpretation on these for now. Simply list them in the existing section.
|
Attached is a Word document with the interpretation for most of the new WCAG 2.1 definitions. Will still have to scan for changed definitions and work on "style property" interpretation which uses several web-based terms: user agent, web, style sheets. |
Proposed the update for adding unique terms only used in Level AAA SC to that list in the definitions section. The rest of the terms will get introduced into the document at the same time as the SC they are used in. |
Added the new definitions for WCAG 2.1 and 2.2 that we will need to add into the corresponding new SCs that use them so we can make see if any interpretation of the terms is needed as we analyze the SC that uses them. I added a work item to the issues for the respective SCs to track along with that work. The last work item for this issue is to look at the existing WCAG 2.0 terms to see if there's any changes since 2013 that need to be reflected in WCAG2ICT. |
Moved the WCAG 2.2 definition list to issue #194, so this issue is tied only to WCAG 2.1 |
New WCAG 2.1 definitions have all been added, approved by the TF and AG WG alongside reviews of the related SCs and are published in the FPWD. |
The text was updated successfully, but these errors were encountered: