Improve Zowe documentation accessibility

[nannanli]

Write the documentation with accessibility in mind. This is also a feedback in the Zowe community survey: more attention to accessibility, current docs are almost unusable for visually impaired users. Spend some time with it blindfolded at a Mac with VoiceOver enabled.

To do that, need to do the following:

• Consolidate general accessibility guidelines and examples.
• Add required guidelines to the Zowe style guide.
• Walk through the existing documentation to catch and fix accessibility issues.
• Ensure that new docs are written with accessibility in mind.
• Investigste tools for checking accessibility

[nannanli]

Here are some accessibility resources provided by Jakub (thanks @balhar-jakub !)

• a book by Jakub: https://www.igi-global.com/book/dyslexia-accessibility-modern-era/244400
• WCAG (https://www.w3.org/TR/WCAG20/)

• As for how to verify: In general there is a combination of automated tools that we can integrate in our pipeline, automated tools that we could use that are provided as service and manual tools and companies providing manual accessib ility testing. The list of tools is available here:https://www.w3.org/WAI/ER/tools/

  I would start experimenting with following ones for the integration in pipeline:

  • https://github.com/paypal/AATT
  • https://github.com/dequelabs/axe-core
  • https://asqatasun.org/
  • https://www.accesslint.com/
  • https://pa11y.org/

[balhar-jakub]

Thanks, I would just mention that the book isn't the best resource for exactly what you are trying to solve. The WCAG is more important resource.

The book is more focused on how to adapt what we know around accessibility to people with dyslexia.

[nannanli]

https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint is useful for style checking including a check of 2 common accessibility issues.