Open cooper-a opened 4 years ago
In Finland and the rest of EU, it's a law that public services need to meet accessibility standards, we have preliminary plans to make our instances meet them, but the core ckan should too meet the standards out of the box.
@Zharktas Do you know what work is being done for those preliminary plans to meet those standards? I'm just wondering what your thought process would look like for that process.
Since our CKAN version is also customized it would take some extra effort to reach accessibility standards outside of core CKAN.
I'll reopen this as the merged PR fixes most glaring problems but it doesn't make CKAN completely accessible yet.
Thanks, it was closed automatically, when i merged related issue(
I'll reopen this as the merged PR fixes most glaring problems but it doesn't make CKAN completely accessible yet.
Hi @Zharktas, I am also looking into making CKAN accessible for our Ontario Data Catalogue. Would you mind share what your development environment looks like? What extensions did you configure?
@bblwq we mostly use custom designs with our clients like in https://www.opendata.fi/en, https://liityntakatalogi.suomi.fi/en_GB/ and https://hri.fi/en_gb/. None of those are accessible yet but since they are heavily customized, their modifications for accessibility can't be easily ported to ckan core or other instances.
I am working on the Ontario Central Forms Repository: that is using CKAN as the basis... we will be making the system AODA compliant (which is based on WCAG 2.0 AA compliance) so once we have our report together, we'll provide that as direction for making changes to the core code... we may be able to do more, but we're on a very tight schedule so all we will have time for initially is making our system compliant, but we will certainly share our findings.
@ryangermann-gov-on-ca that's great to hear. Please do share your findings once you have them.
I am implementing an instance of CKAN for an organization that requires that it meets WCAG 2.0 Level AA. 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 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 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.