Add references to WCAG 2.0 #30
Comments
backwardok
pushed a commit
to backwardok/eslint-plugin-jsx-a11y
that referenced
this issue
Jun 27, 2020
Adds in a section for every rule that specifies what the WCAG guidelines are (if applicable) in a new Accessibility guidelines section near the bottom of the rule documentation. Additional changes: - Move Resources/References underneath Accessibility guidelines section - Fix up heading level of Resources so that the heading order progresses sequentially - Fix up resource link text to be clearer - Fix up some broken links or old references - Update pronoun usage in `accessible-emoji` to use they instead of he/she - Add some additional examples and rule clarity to `click-events-have-key-events` - Fix up code formatting for `tabindex-no-positive` - Add additional resources to some rules without resources Partially addresses jsx-eslint#30
backwardok
pushed a commit
to backwardok/eslint-plugin-jsx-a11y
that referenced
this issue
Jun 27, 2020
Adds in a section for every rule that specifies what the WCAG guidelines are (if applicable) in a new Accessibility guidelines section near the bottom of the rule documentation. Additional changes: - Move Resources/References underneath Accessibility guidelines section - Fix up heading level of Resources so that the heading order progresses sequentially - Fix up resource link text to be clearer - Fix up some broken links or old references - Update pronoun usage in `accessible-emoji` to use they instead of he/she - Add some additional examples and rule clarity to `click-events-have-key-events` - Fix up code formatting for `tabindex-no-positive` - Add additional resources to some rules without resources - Change Resources from ordered list to unordered list since the order really doesn't matter Partially addresses jsx-eslint#30
backwardok
pushed a commit
to backwardok/eslint-plugin-jsx-a11y
that referenced
this issue
Jun 27, 2020
Adds in a section for every rule that specifies what the WCAG guidelines are (if applicable) in a new Accessibility guidelines section near the bottom of the rule documentation. Additional changes: - Move Resources/References underneath Accessibility guidelines section - Fix up heading level of Resources so that the heading order progresses sequentially - Fix up resource link text to be clearer - Fix up some broken links or old references - Update pronoun usage in `accessible-emoji` to use they instead of he/she - Add some additional examples and rule clarity to `click-events-have-key-events` - Fix up code formatting for `tabindex-no-positive` - Add additional resources to some rules without resources - Change Resources from ordered list to unordered list since the order really doesn't matter Partially addresses jsx-eslint#30
backwardok
pushed a commit
to backwardok/eslint-plugin-jsx-a11y
that referenced
this issue
Jun 27, 2020
Adds in a section for every rule that specifies what the WCAG guidelines are (if applicable) in a new Accessibility guidelines section near the bottom of the rule documentation. Additional changes: - Move Resources/References underneath Accessibility guidelines section - Fix up heading level of Resources so that the heading order progresses sequentially - Fix up resource link text to be clearer - Fix up some broken links or old references - Update pronoun usage in `accessible-emoji` to use they instead of he/she - Add some additional examples and rule clarity to `click-events-have-key-events` - Fix up code formatting for `tabindex-no-positive` - Add additional resources to some rules without resources - Change Resources from ordered list to unordered list since the order really doesn't matter Partially addresses jsx-eslint#30
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great to add references to the Web Content Accessibility Guidelines 2.0 wherever we can.
https://www.w3.org/TR/WCAG20/
These understanding links might be good for individual linking e.g. https://www.w3.org/TR/UNDERSTANDING-WCAG20/text-equiv.html
TOC is here https://www.w3.org/TR/UNDERSTANDING-WCAG20/Overview.html#contents
It might make sense to reference these guidelines in the error messages, e.g. WCAG20-1.1
The text was updated successfully, but these errors were encountered: