Compliance

Accessibility Conformance Test Rules Format 1.0 reaches Proposed Recommendation status

Share this post:

It’s a common question with accessibility verification and reporting. How did someone arrive at their test results? Are their results accurate, or are the issues being reported really not required by the accessibility standards? As a developer, it can be really frustrating when you’ve done the accessibility work and validated using robust automated tools and sound test methodologies only to be told that another test had different results. You’re left wondering, which test is right?

It would be nice if everyone involved in accessibility work could understand what steps a tester had taken and easily reproduce their test results, even if validating with a different tool or methodology. It might ease a developer’s workload to focus on fixing issues instead of struggling to understand or validate the test results.

The Accessibility Conformance Testing (ACT) Rules Format 1.0 was just published as a W3C Proposed Recommendation standard by the Worldwide Web Consortium (W3C). With multiple implementations and several reviews completed, this standard is one step closer to being a Recommendation, or final version.  The remaining step is for W3C member sign-off.

So how will this standard help to solve these problems? The ACT Rules Format 1.0 provides a consistent format for documenting test rules used to validate conformance to accessibility standards.  It enables developers of test tools and test methodologies to document their test rules for greater transparency. The rules format also includes a requirement to develop test cases so that implementations of the rules can be verified to ensure their findings match the expected test results.

This effort has the potential to harmonize rules used to check for accessibility conformance to standards. There is an ACT Rules Community Group which is developing a repository of rules for testing conformance to the Web Content Accessibility Guidelines (WCAG) 2.1.  It is an open community for anyone interested to contribute.  The rules they are developing are documented using the ACT Rules Format 1.0.  The ACT Task Force and Accessibility Guidelines Working Group will be reviewing rules to ensure they correctly interpret the accessibility requirements and correctly apply the ACT Rules Format. The intent is to strengthen all test tools and test methodologies to create an environment where accessibility testing will have more consistent results.  Hopefully this will lead to a higher level of accessibility for products and services tested using these tools.

To learn more, read the W3C announcement of the publication of the ACT Rules Format 1.0 Proposed Recommendation.

More Compliance stories
By Ram (P G) Ramachandran and Thomas Brunet on May 16, 2018

AI-Enabled Tools and Automation to Improve Accessibility

Try Automated Accessibility Tools wth Unlimited Scans through June The IBM Accessibility Research team is laser-focused on seamlessly integrating accessibility into the development process. We have developed a suite of IBM Automated Accessibility Tools to help development teams easily and effortlessly “make accessibility happen.” Teams that use our tools tell us: “The automated tests run […]

Continue reading

By Marc Johlic and Sharon Snider on May 14, 2018

Updates to the Va11yS Open Source Project

  With Global Accessibility Awareness Day (GAAD) quickly approaching, Sharon and I thought it would a be a good time to give you a brief update on our open source Verified Accessibility Samples project – or Va11yS.  Jack Dam, our Accessibility Test Engineer, has been rigorously testing the latest samples and adding the results for […]

Continue reading

By Tom Babinszki on September 11, 2017

Maximizing Impact with Personalized Accessibility Training

There are many outstanding accessibility tutorials online. Yet, I’m finding that designers and developers are reluctant to go through them. I always wondered why? As I travel to many different IBM offices around the world training product design and development teams and understanding their needs, I believe I have found what makes them more interested […]

Continue reading