accessibility guides, tips, examples, statement

[evanwill]

some starter to do's:

• start accessibility section - Accessibility
• basic statement
• link to accessibility resources for related platforms
• evaluate compliance with WCAG
• point out accessibility features
• add how to guide for auditing your own site, with resources, i.e. walk-through to Lighthouse
• add About info about semantic markup
• add more in metadata section about impact of choices

ideas of things to add to docs:

• "accessibility tab" -- lays "out what aspects of CB meet WCAG 2.1AA guidelines, which aspects of CB partially meet 2.1AA, and which aspects fail to meet 2.1AA... This could also be a space where you point out any accessibility features that CB has. You could also even include a demo about, from the perspective of a CB maker, how they could make choices to make more accessible projects." (Elliot)
• accessibility tips for creators in each relevant section (e.g. how to write about page using headers correctly, how to make good color choices during customization)
• link to accessibility resources for related platforms (e.g. GitHub, Google Docs) i.e. accessibility for project creators, not just site visitors
• guide for auditing your own site, with resources, i.e. walk-through to Lighthouse

examples:

• manifold statement
• pressbooks
• fulcrum

resources:

• Manifold Key Concepts for Accessibility
• pressbooks, Make Your Book Accessible and Inclusive
• no mouse challenge
• DLF accessibility working group, Accessibility Auditing Shortlist

[evanwill]

section started in PR #30