With almost each guideline belonging to the accessibility-ready tag we have related topics in the Standards and best practices.
For example the guideline "Controls with accessible names, roles, and states" and the topic "Accessible name".
With the Standards and best practices the resources are set up like for example:
h2 Resources
h3 WCAG Success Criteria for accessible names in forms.
Giving a form control an accessible name is necessary to meet the WCAG success criteria:
- 1.3.1 Info and relationships (Level A).
- [etc].
h3 Related pages in this documentation.
- Standards and best practice - Frontend code: Accessible name.
- [etc].
h3 Other resources.
- WebAIM: Decoding Label and Name for Accessibility.
- [etc].
We can add a link to the related accessibility-ready guideline to this resources.
The accessibility-ready guidelines now only have the heading "WCAG resources" with a link to related the understanding pages. I propose to add more internal and external resources to the guidelines in the same structure as with the standards and best practices.
With almost each guideline belonging to the accessibility-ready tag we have related topics in the Standards and best practices.
For example the guideline "Controls with accessible names, roles, and states" and the topic "Accessible name".
With the Standards and best practices the resources are set up like for example:
h2 Resources
h3 WCAG Success Criteria for accessible names in forms.
Giving a form control an accessible name is necessary to meet the WCAG success criteria:
h3 Related pages in this documentation.
h3 Other resources.
We can add a link to the related accessibility-ready guideline to this resources.
The accessibility-ready guidelines now only have the heading "WCAG resources" with a link to related the understanding pages. I propose to add more internal and external resources to the guidelines in the same structure as with the standards and best practices.