Details
-
Type: Epic
-
Status: Won't Do
-
Priority: Important
-
Resolution: Won't Do
-
Affects Version/s: 4.7.20
-
Fix Version/s: None
-
Component/s: Usability
-
Labels:None
-
Epic Name:Meet WCAG 2.0 AA accessibility standard
-
Versioning Impact:Minor (add functionality in backwards-compatible manner)
-
Documentation Required?:Developer Doc
-
Funding Source:Needs Funding
-
Verified?:No
Description
This is an epic for issues involved in improving CiviCRM accessibility so that it meets WCAG 2.0 (https://www.w3.org/WAI/WCAG20/quickref/). We should likely prioritise A, then AA, and finally the AAA levels.
Compliance with this standard would improve the usability of CiviCRM for important segments of users. It is also required by law for government websites in a number of jurisidictions (US, Canada, Australia), and in some places for all websites of organizations in a jurisdication (eg the Canadian province of Ontario, Australia).
In Australia, WCAG compliance is required by Australian Law and applies to all websites not just Government. See excerpt:
"This requirement applies to any individual or organisation developing a website or other web resource in Australia, or placing or maintaining a web resource on an Australian server."
From https://www.humanrights.gov.au/world-wide-web-access-disability-discrimination-act-advisory-notes-ver-41-2014#required
An obvious example of this would be a non-profit that uses CiviCRM and that has users with visual disabilities. Their website must be WCAG compliant to the required level. No exceptions.
Attachments
Issue Links
- is supplemented by
-
CRM-21732 Make drop down menus accessible, so they work with screen readers
- Open
1.
|
Make menu more accessible | Won't Do | Joe Murray |
|
|
2.
|
Make accordion panels accessible | Done/Fixed | Joe Murray |
|
|
3.
|
Make select2 widgets accessible | Won't Do | Monish Deb |
|
|
4.
|
Add labels for accessibility | Won't Do | Joe Murray |
|