Skip to content
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

Guidelines focus on functional user needs #311

Closed
putzhuber opened this issue Feb 23, 2021 · 4 comments
Closed

Guidelines focus on functional user needs #311

putzhuber opened this issue Feb 23, 2021 · 4 comments
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)

Comments

@putzhuber
Copy link

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

  • Outcome: Headings organize content
  • Outcome: Visual headings correspond with semantic headings
  • Outcome: Conveys hierarchy with semantic structure
  • Outcome: Paragraphs and lists structure content
  • Outcome: Landmarks convey sections of page
  • Outcome: Use of standardized semantic elements for blocks of content
  • Outcome: Use of lists for navigation
  • Outcome: Use of standardized semantic markup for datatables
  • ...

Guideline Content is visually structured

  • Outcome: Uses visually distinct headings
  • Outcome: Separates connected blocks of content visually
  • Outcome: Follows recommendations for heights of margins between content blocks
  • Outcome: Follows recommendations for line-length
  • Outcome: Use of clear visual form labels
  • ...

Guideline Auditory content is structured and operable

  • Outcome: Background noise is xxxx lower than foreground speech
  • Outcome: Sound does not start automatically
  • Outcome: Sound is easily dismissable
  • Outcome: information about sound is available

Guideline Multimedia content that cannot be seen has alternatives

  • Outcome: Short Summary of video content available
  • Outcome: Description of complex video available
  • Outcome Audio Description for complex video content
    • ...

Guideline Multimedia content that cannot be heard has alternatives

  • Outcome: Transkript for audio content available
  • Outcome: Captions for audio content in videos
  • Outcome: Translation in sign language for video content
    • ...

Guideline The function of elements is semantically clear and consistent

  • Outcome: conveys name, role and value of each element
  • Outcome: form elements are labeled
  • Outcome: links opening a different file format, convey this information in text
  • Outcome: conveys toggle function of links or buttons
  • Outcome: markup follows specification (html5, aria, pdf/ua...)
  • Outcome: navigation is consistent
  • ...

Guideline The function of elements is visually clear and consistent

  • Outcome: purpose of interactive elements (buttons, icons, links) is clear
  • Outcome: form elements have visual labels
  • Outcome: labels are clearly connected to form elements, even when page zoom up to 400% is used.
  • Outcome: navigation is visually consistent
  • ...

Guideline Content is understandable

  • Outcome: use of clear words
  • Outcome: appropriate level of specialist language
  • Outcome: appropriate use of foreign words
  • Outcome: explanation for abbreviations
  • ...

and so on...

@jpascalides jpascalides added section: Requirements Related to Silver Requirements document status: assigned to subgroup ask subgroup for proposal Subgroup: editors no specific subgroup (default) labels Mar 5, 2021
@jpascalides
Copy link

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.

@jspellman
Copy link
Contributor

jspellman commented Mar 11, 2022

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"

@rachaelbradley rachaelbradley added 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 labels Aug 29, 2023
@alastc
Copy link
Contributor

alastc commented Jan 16, 2024

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:
  1. The requirements are often overlapping, not least because of intersectional disabilities.
  2. We are aiming to use a tagging structure so that the guidelines can be viewed in different ways. It would conflict with the requirement "4.3 Multiple ways to display".

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.

@alastc alastc added the only response needed issues that should be easy to close, acknowledgement only label Jan 16, 2024
@alastc
Copy link
Contributor

alastc commented Mar 21, 2024

Response above approved by the group.

@alastc alastc closed this as completed Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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)
Projects
None yet
Development

No branches or pull requests

5 participants