WCAG Compliance | Communifire Documentation

Web Content Accessibility Guidelines (WCAG) covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.

Please see World Wide Web Consortium (W3C) recommendations for the latest compliance guidance.

Understanding Compliance in Axero

1. Clients have responsibility for ensuring accessibility on their site. 
2. WCAG compliance is mandated by law for government organizations and the responsibility is on them to use accessible information and communication technology.
3. No website or web application can guarantee absolute compliance unless the site is super narrow, i.e. a couple of pages that can easily be tested for compliance.
4. Axero is an authoring app which means we cannot account for user created content that is non compliant.
5. Many client sites are heavily customized which may impact accessibility, we can only test the platform in its base state.
6. Axero has clients that have already confirmed WCAG compliance on their sites.
7. We have an on-going process to address issues of compliance that have been identified and continue to incorporate accessibility considerations in our design, development, and QA process.

How Axero Prioritizes Accessibility Fixes

We prioritize accessibility fixes for Axero in much the same way we do for any useability or functionality requirements from our clients. 

1. If any client finds an accessibility issue that impacts their compliance or useability for their users we ask that you submit a private case with the issue. Client cases are the highest priorities for each of our development sprints. 
2. With the breadth and variety of different product projects that compete for priority, it is difficult to get to all the potential accessibility issues, but Axero has a strong history of aligning with client uses to speed them to compliance (including Accessibility compliance) by focusing on pressing issues.
3. As we discover accessibility issues in the platform through our internal QA processes we track these issues and prioritize them behind client issues and along with other functionality improvements.
4. Accessibility issues we discover are prioritized based on the likelihood someone with accessibility needs will be impacted. Issues in areas that are most commonly used will be prioritized over areas that fewer users access. For example, issues impacting login will have a high priority; issues around site administrator and content moderation will have lower priority.