WCAG Compliance | Communifire Documentation

The Web Content Accessibility Guidelines (WCAG) cover 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 are responsible for ensuring accessibility to their site. 
2. WCAG compliance is mandated by law for government organizations, and they are responsible for using accessible information and communication technology.
3. No website or web application can guarantee absolute compliance unless it is super narrow (e.g., it has a couple of pages that can easily be tested for compliance).
4. Axero is an authoring app, so we cannot account for noncompliant user-created content.
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 ongoing process to address identified compliance issues and continue to incorporate accessibility considerations into our design, development, and QA processes.

How Axero Prioritizes Accessibility Fixes

We prioritize accessibility fixes for Axero as we do for any useability or functionality requirements from our clients. 

1. If any client finds an accessibility issue that impacts their compliance or user usability, 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 competing for priority, it is difficult to address all the potential accessibility issues, but Axero has a strong history of aligning with client needs 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 them and prioritize them behind client issues and along with other functionality improvements.
4. We prioritize accessibility issues we discover based on the likelihood that 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 a lower priority.