Policy-driven Test Initiatives
With policy-driven Test Initiatives, you can quickly isolate individual assertions, select a strategy to tackle them and monitor the progress of that strategy. You can set these policies in the ARC Monitoring dashboard and utilize them through ARC API.
Policy-driven Test Initiatives consist of three main elements:
- A Rule. This is the particular accessibility requirement you want to address and monitor. For example, the ARC rule of ‘iframeNoTitle’ will check for iframe elements without title attributes. Often the rules will come from your domain dashboards, where you have identified your remediation priorities.
- A Policy. A policy is a statement of how you want to address the rule. In ARC there are three policy types:
- Zero Tolerance – no failures allowed
- Sustain Conformance – level of assertion failures are to remain same as in previous scan
- Percent Improvement – set an explicit percent improvement to meet in comparison to a previous scan
- Baseline Scan. Progress in achieving your policy will be measured against a previous score in your ARC monitoring scans. For example, if you have 100 failures across 50 pages against the ‘iframeNoTitle’ rule in a scan, then that score can be used as your baseline for sustaining or improving over time.
Seamless CI/CD Accessibility TestingTPG ARC Monitoring API can fully integrate with any CI/CD and DevOps software that allows for Open or RESTful APIs.
- Travis CI
- Circle CI
Apply A Proactive Testing Approach To AccessibilityIntegrating accessibility into your CI/CD pipeline shifts your accessibility program management from a reactive management style to a proactive, policy-first management style.
Integrating on-demand testing into your organization’s CI/CD process takes a proactive approach by testing success against the same evaluation rulesets prior to the code or content being accepted into the repository. This ensures that systems, user flows, and other digital content complies with success criteria during the early stages of the development cycle. It also ingrains accessibility methodologies into the dev-ops culture.
Many accessibility monitoring solutions, audits, and reviews present a reactive approach to accessibility management. Program managers and accessibility engineers evaluate success criteria after digital flows and content are created and are then forced to remediate existing issues. This creates an inefficient development cycle that increases time, costs, and risk exposure. Remaining in a constant state of reacting to new issues means you’ll always be one step behind.
How Is ARC API Different?The ARC API fully integrates with TPG’s ARC Monitoring. ARC Monitoring provides the baseline datasets necessary to set policies and then the API can be used to test against them. Historical data from API testing is presented in ARC Monitoring dashboards, giving program managers full visibility into policy compliance at the earliest stages in development.
The API delivers the implementation while ARC Monitoring provides accessibility managers key insights and enables them to track and report progress. This all functions as part of TPG’s seamless accessibility management platform (ARC), which provides accessibility managers visibility and control across the entire accessibility workflow.