-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Comments
This sounds great. @abrightclearweb are you project managing this? Are there specific subtasks that you can lay out that need to be done? |
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. |
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 😄 |
This issue seems best addressed in User Documentation. |
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. |
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:
@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
The text was updated successfully, but these errors were encountered: