Accessibility guidance documentation for Tech Volunteers

FreeUKGen / Systemwide

repository for issues that affect all systems within the Free UK Gen portfolio

0 stars 0 forks source link

Accessibility guidance documentation for Tech Volunteers #237

Open DeniseColbert opened 2 years ago

DeniseColbert commented 2 years ago

Documents (or sections of one document) needed on:

[ ] Assistive technologies (we have this, but needs review) - GENERAL or FOR ALL
[ ] HTML for accessibility in App pages - FOR PEOPLE USING HTML AND CSS IN THE APP PAGES
[x] HTML for accessibility in Refinery - FOR PEOPLE USING HTML AND CSS in REFINERY (in Markup guide)
[ ] Accessibility for UX/Designers (#240?)

Folder with existing accessibility: https://drive.google.com/drive/folders/0BwVHfubVQz16eGV5enJZM2dEZkE?resourcekey=0-zz_GM7fB_grmuB6He9slOg&usp=sharing

DeniseColbert commented 2 years ago

@AlOneill is working on a summary table to perhaps include in the documentation

AlOneill commented 2 years ago

@DeniseColbert the 'summary table' is somewhat beside the point. What I am working on is some HTML pages that:

explain the need for valid and semantic (rather than presentational) HTML — with examples for commonly-used elements on our App pages
demystify our CSS — our style-names (and their use constraints) are somewhat quirky and many were named with designers in mind rather than those who work with CSS, such as developers
describe how to use (some) WAI-ARIA to help screen-reader users understand our pages
describe how to make image markup accessible to all our users — including the 'i' image

… plus anything else that seems relevant, as I think of it … or as someone else suggests it!

DeniseColbert commented 2 years ago

Hey @PatReynoldsFUG I’m using Zenhub in GitHub, click this link to join my workspace and see other features available in GitHub or download the Zenhub extension and sign up with your GitHub account. Posted using Zenhub

DeniseColbert commented 1 year ago

@AlOneill to consider writing this up in HTML (refinery) eventually: it will grow organically with input.

AlOneill commented 1 year ago

Have started to pull together all the accessibility guidance that I know. Am using Notion because of its flexibility (and because I want to get to know it better!).

It will be a multi-page document. I will place it in Refinery once the framework is complete, which could be quite a while.