Opened 6 years ago
Last modified 6 years ago
#943 new defect
Making GS3 compliant with WCAG 2.0 web accessibility standards
| Reported by: | ak19 | Owned by: | nobody |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Greenstone3 Interface | Severity: | major |
| Keywords: | GS3-interface, demo-collections, wiki | Cc: |
Description
This ticket arose from librarian Christopher Loughnane's request to the mailing list on 10/07/18 04:33 titled "Accessibility Disclosure Form for Installation of Greenstone", the discussion that followed with Dr Bainbridge and the response to Christopher on 20 July 2018 18:55.
- How to Meet WCAG 2 (Quick Reference) at
https://www.w3.org/WAI/WCAG21/quickref/
- Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0 (beware that this is version WCAG 1.0!) at
https://www.w3.org/TR/WCAG10/full-checklist.html
- The fuller document: Web Content Accessibility Guidelines (WCAG) 2.0 at
https://www.w3.org/TR/WCAG20/
Dr Bainbridge's idea is for a summer project student to get the default GS3 interface to become WCAG compliant and then to rebuild the GS3 demo collections with them and adjust them to ensure the collections are compliant too.
We'd also want to have some wiki instructions/guidelines on developing DLs that meet WCAG 2.0: what to do if you have audio files in your collection, video files, images, images of text (need OCR-ed text for compliance), and more.
"Examples of WCAG Level AAA websites"
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_textbox_role
https://stackoverflow.com/questions/21922305/how-does-role-form-help-accessibility