Closed putzhuber closed 7 months ago
Thank you for your comment. Project members are working on your comment. You may see discussion in the comment thread and we may ask for additional information as we work on it. We will mark the official response when we are finished and close the issue.
Discussed in the Silver meeting of 11 March 2022. RESOLUTION: 311 has some support in the group and needs more development, and will be assigned to "Outcome and Guidelines"
Approved response:
The structure and categorization has been worked on extensively in the last 12 months. We do not wish to make categories mutually exclusive for two reasons:
We are still working out the best ways to organize the default and optional views of the guidelines, we will take this structure as an input to that work.
Overall there is no update to the requirements document from this issue, and the categorization is in progress.
Response above approved by the group.
Guidelines will be more granular, more specific
Proposal:
Guidelines should focus as much as possible on special functional user needs, not mix very different needs, for instance structure (special need for screenreader users, machine readability) and styling (special visual needs) should not be grouped together.
Some examples for separation of user needs (as far as possible)
Guideline Content is semantically structured
Guideline Content is visually structured
Guideline Auditory content is structured and operable
Guideline Multimedia content that cannot be seen has alternatives
Guideline Multimedia content that cannot be heard has alternatives
Guideline The function of elements is semantically clear and consistent
Guideline The function of elements is visually clear and consistent
Guideline Content is understandable
and so on...