Improve WCAG compliance

[alex-mayorga]

Steps:

• Load https://wave.webaim.org/report#/https://cheatsheetseries.owasp.org/index.html

Actual results:

• 11 Errors
• 9 Contrast Errors
• 7 Alerts
• 9 Features
• 16 Structural Elements
• 15 ARIA

Expected results: The website is WCAG compliant

[mackowski]

@alex-mayorga do you want to fix the issues? These are good findings!

[shruti01052002]

Hey @alex-mayorga, I am interested to work on these issues.

[smariapena]

Some thoughts from an outside observer:

• A large amount of AX failures noted are in mkdocs itself and cannot be addressed in this codebase. This issue should be updated with correct scope.
• WCAG has versions and levels, probably best use whatever OWASP at large has committed to, and at the very least decide the CheatSheetSeries level and be clear about what that is in order to reach a compliance.
• WCAG compliance does not guarantee accessibility, the project should also specify the scope there, again with taking cue from OWASP (could not find an accessibility statement to reference).
• Disability community at large should be included in some way however small that may be. Think: "Nothing about us without us" if the intention is truly about making the site accessible.

Thanks for listening 🙌

[npiyush97]

@mackowski to fix this issue requires access to /custom-theme which I think isn't accessible.

[mackowski]

@npiyush97 custom-theme directory is created when the site is generated https://github.com/OWASP/CheatSheetSeries/blob/master/scripts/Generate_Site_mkDocs.sh