Guidelines focus on functional user needs #311
Labels
migration: core
Issues that raise core questions that are still open for discussion
migration: other
Issues that do not fall into the other three categories
only response needed
issues that should be easy to close, acknowledgement only
section: Requirements
Related to Silver Requirements document
section: structure
status: assigned to subgroup
ask subgroup for proposal
Subgroup: editors
no specific subgroup (default)
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...
The text was updated successfully, but these errors were encountered: