Meeting Accessibility Standards
- Dominant language
- No language data
- Stars
- 39
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I am implementing an instance of CKAN for an organization that requires that it meets [WCAG 2.0 Level AA](https://www.w3.org/TR/WCAG20/). The idea is that CKAN could by default meet this standard or other similar standards. This might not even entail further development, but instead just doing an [accessibility evaluation](https://www.w3.org/WAI/test-evaluate/) on certain standards to verify that CKAN already meets those standards.
If anyone else is also working on developing CKAN to meet an accessibility standard I would love to get in touch.
The current approach at my organization is to use [Web Experience Toolkit](https://wet-boew.github.io/v4.0-ci/index-en.html) with CKAN to help reach WCAG 2.0 Level AA. This approach seems to be mostly on the front-end with a customization of CSS and some JS components. After implementing Web Experience Toolkit there would still be some customization to fully meet the standard.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.