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

Manual for users of assistive technology #10373

Closed
rianrietveld opened this issue Oct 6, 2018 · 5 comments
Closed

Manual for users of assistive technology #10373

rianrietveld opened this issue Oct 6, 2018 · 5 comments
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). Needs User Documentation Needs new user documentation

Comments

@rianrietveld
Copy link
Member

The new interface of Gutenberg has a learning curve, for all users.

For users that depend on assistive technology (AT), like a screen reader or voice recognition software, that learning curve is much higher.
If you don't have an overview of the whole screen or are depended on keyboard focus to perform tasks, Gutenberg is harder to learn.

To help AT users, a manual is needed. With:

  • a walk through of the basic functionality with a keyboard only
  • how to navigate through functionality with the screen reader navigation
  • a list of accessible names for labels that are icons now
  • a list of the keyboard short cuts
  • a way to report issues or and contribute.

@abrightclearweb already started this and she need help, people who do research on how to use Gutenberg and people that help writing. The work document is on Google Docs

Related: #5420

@rianrietveld rianrietveld added the [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). label Oct 6, 2018
@rianrietveld rianrietveld changed the title Manual for users of assitive technology Manual for users of assistive technology Oct 7, 2018
@aaronjorbin aaronjorbin added the [Type] Developer Documentation Documentation for developers label Oct 11, 2018
@aaronjorbin aaronjorbin added this to the Documentation & Handbook milestone Oct 11, 2018
@aaronjorbin
Copy link
Member

This sounds great.

@abrightclearweb are you project managing this? Are there specific subtasks that you can lay out that need to be done?

@abrightclearweb
Copy link

Hi @aaronjorbin - I started writing it, and @Wingo5315 also contributed.

I've been on holiday the last two weeks, so am intending to get back to it ASAP, with the 5.0 release due soon.

@chrisvanpatten
Copy link
Contributor

Thanks for tackling this @Wingo5315 and @abrightclearweb ^__^

It would be awesome to include this in our user handbook — I updated my outline in #10911 to reference this.

Although I don't use any assistive technology myself, let me know if I can do anything to help your efforts and please feel free to join us in the weekly "Gutendocs" meeting on Slack (Tuesdays at 17:00 UTC in #docs) if you need any thing too 😄

@DaisyOlsen
Copy link
Contributor

This issue seems best addressed in User Documentation.

@t-hamano
Copy link
Contributor

Thank you for your suggestion. I think this is an improvement for the handbook, Learn WordPress content, etc., so I would like to close this issue.

If you have any suggestions for improvement in Gutenberg, please feel free to comment.

@t-hamano t-hamano closed this as not planned Won't fix, can't repro, duplicate, stale Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). Needs User Documentation Needs new user documentation
Projects
None yet
Development

No branches or pull requests

7 participants