Learning about accessibility in Hypha

How can we as a team working on Hypha improvements understand and learn more about accessibility and impaired folks needs from OSS?

Accessibility is often de-prioritised and de-scoped as part of technology/software and especially within resource-constrained OSS orgs so we started this wiki as a way to collect accessibility information and processes that we as Hypha maintainers, users and adopters would like to consider and learn more about so that the development of Hypha can improve continuously in terms of Accessibility.

As a rule, the product, design and development functions/roles within Hypha always do their best to include accessibility as part of the discovery/inception, design and requirements of a feature or improvement but they will invariably miss key accessibility needs and details.

Please feel free to edit this wiki to add any resources, details and information you believe is relevant.

Resources and Guides

https://www.a11yproject.com/checklist/ https://abilitynet.org.uk/ http://www.vischeck.com/vischeck/ http://www.eclipse.org/actf/downloads/tools/aDesigner/ https://www.facebook.com/groups/AskDisabled4Everyone/ https://contrastchecker.com/ https://contrast-ratio.com/ https://colourcontrast.cc/ http://www.photoability.net/index.php https://www.bbc.co.uk/accessibility/ https://www.bbc.co.uk/opensource/projects/bbc-a11y https://www.bbc.co.uk/accessibility/forproducts/guides/mobile/ https://www.bbc.co.uk/academy/en/collections/designing-for-screen-readers https://www.udacity.com/course/web-accessibility--ud891 https://shouldiuseanaccessibilityoverlay.com/

Best practice

WIP

Acceptance criteria for Hypha features and UI

• Can a user of Hypha use the 'tab' key to navigate the primary content within a section/page of Hypha without getting 'stuck' in any modal selection or 'window'.
• Do screen readers start at the most vital part of the information contained within the active section/page of Hypha