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

Email: Feedback on wcag 3.0 (How-To Design) #473

Open
jspellman opened this issue Mar 12, 2021 · 5 comments
Open

Email: Feedback on wcag 3.0 (How-To Design) #473

jspellman opened this issue Mar 12, 2021 · 5 comments
Labels
migration: other Issues that do not fall into the other three categories status: assigned to subgroup ask subgroup for proposal Subgroup: editors no specific subgroup (default) usability issues issues generally related to usability of the documentation

Comments

@jspellman
Copy link
Contributor

Comment from Email:

Hello Silver W3 – Wcag 3.0 Team

Looking to provide some insight on some improvement I’d like to suggest to
the WCAG 3.0

Feedback issue Notes

I Love this new section for the how to’s. section with the way it handles
breaking down the chunking of the content

Unforunately for my learning style, examples are pretty critical when I
start to talk about or learn about a topic.

In this scenario below of the how tos Get Started, explains the summary
description of a particular issue in text & the 5th tab examples sections
which is far away from the description of the issue.. examples tab is
great with lots of detailed examples.

whenever we talk about Summary level Defining an issue or a problem having
couple easy examples there next to the issue overview /summary description
to speak to what we are talking about is pretty critical in Helping with
comprehension and cognitive abilities.

if it included a few visual examples of the issues Would be helpful if
possible.

Similarly could be provided to the main wcag 3.0 ( silver ) guideline page
topic.

Just using the how-tos as an example. ( screenshot embedded of text
alternatives how-to UI with side panel nav and the getting started tab selected

  • Kevin Boyko
@jspellman jspellman added status: assigned to subgroup ask subgroup for proposal Subgroup: editors no specific subgroup (default) labels Mar 12, 2021
@jspellman
Copy link
Contributor Author

Note that there are screenshots attached to the original email.

@jspellman
Copy link
Contributor Author

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.

@colabottles
Copy link

@jspellman Do we have a link or any screencaps of the screenshot that was included in the original email? I'd like to bring this back to the group for reference. Thank you.

@gradualclearing
Copy link
Contributor

Note that there are screenshots attached to the original email.

@jspellman is it possible to get access to the screenshot images? Can they be attached to the issue, maybe? Thank you!

@colabottles
Copy link

@ jspellman @gradualclearing An observation and question.

Going back over this issue, this seems to me like this is a design issue and isn't necessarily Error subgroup related.

Did we ever get the screenshot image(s)? If not, I would be more than happy to reach out to the original poster.

Thanks.

@jspellman jspellman added usability issues issues generally related to usability of the documentation and removed Subgroup: Errors labels Jun 4, 2021
@rachaelbradley rachaelbradley added the migration: other Issues that do not fall into the other three categories label Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
migration: other Issues that do not fall into the other three categories status: assigned to subgroup ask subgroup for proposal Subgroup: editors no specific subgroup (default) usability issues issues generally related to usability of the documentation
Projects
None yet
Development

No branches or pull requests

4 participants