Please read the 7 December 2016 ACT teleconference meeting minutes. The summary and the link to the full minutes is on the 2016 Minutes wiki page.

Summary

Details

Review the following text proposed for the for the 4.1 Selectors section of the Accessibility Conformance Testing Framework Requirements document in response to Action 13: Write up on selectors 4.1. See Pull request #21: Content for the Selectors section for additional thoughts and questions Romain had on his draft content.

• 4.1 Selectors

  A selector is a boolean predicate that takes an element or component in the set represented in the input data and unambiguously tests whether the element or component matches the selector or not. In an ACT Rule, a selector is applied to the entire input data to filter it into a set of elements or components to be evaluated with the test procedure.

  Selector syntax depends on the input type. When the input data is an HTML document or set of elements, the selector must be a CSS selector. When a formal selector syntax is not available for the input type, the selector may be described unambiguously in plain English.

Choose one of the following and record your comments in the github conversation tab for pull request #21: Content for the Selectors section (preferred) or in the comment box below.

Summary

(1 response didn't contain an answer to this question)

Details

Review the following updated text proposed for the Rule Description section 2.2 of the Accessibility Conformance Testing Framework Requirements document in response to the 7 December survey results for question 3 and the discussion from the 7 December meeting.

• 2.2 Rule Description

  Each ACT Rule MUST have a description that:

  • Is in plain language;
  • Explains the accessibility requirement being tested;
  • Lists any limitations and assumptions for the test;
  • Explains the failure conditions and their reasons.

Choose one of the following and record your comments, in the github conversation tab for pull request #12 (preferred) or in the comment box below.

Summary

Details

Review the following update proposed for the Introduction section of the Accessibility Conformance Testing Framework Requirements document in response feedback received during the 7 December ACT TF meeting: 7 December Meeting Minutes.

• The Accessibility Conformance Testing Framework (ACT Framework) defines a set of requirements, format and measurable qualities to produce a transparent set of accessibility test methods that produce consistent validation results. This work will lead to a more common understanding by accessibility experts on how to test accessibility standards, such as WCAG 2.0. In support of this framework is a set of test descriptions, known as Accessibility Conformance Testing Rules (ACT Rules) which define test descriptions that meet the requirements outlined by the ACT Framework.

Choose one of the following and record your comments in the conversation tab of pull request #20 (preferred) or in the comment box below.

Summary

(1 response didn't contain an answer to this question)

Details

Review the following update proposed for the Scope section of the Accessibility Conformance Testing Framework Requirements document in response to Issue 5: ACT Framework Requirements document is too general.

• Status of this document

  This document is an early draft. It has been updated based on initial feedback from the WCAG Working Group.

• Introduction

  The work has been incubated in the Auto-WCAG Community Group for over 2 years, which has shown a growing interest in harmonized accessibility testing. Development and implementation of ACT Rules are outside the scope of the ACT Framework. This work is currently done within the [Auto-WCAG Community Group](https://www.w3.org/community/auto-wcag/). The ACT Taskforce will support the Auto-WCAG Community group in the development of the first set of ACT Rules.

• Requirements
  • Manual: A process that can only be done by a user
  • Semi-automated: A test combining automated testing and manual testing
  • Usable With Different Accessibility Requirements

  Rules will be developed as part of the project as evidence that the ACT Framework is capable of targeting different accessibility requirements for web content and digital publications.

• Scope

  The ACT Framework is created to develop rules for the conformance of web technologies, including those used in digital publishing. This includes technologies such as HTML, CSS, WAI-ARIA, SVG and more. The ACT Framework is designed to be technology agnostic, meaning it has no specific technology in mind. This also means that the ACT Framework could conceivably be used for other technologies. Whether or not this is the case depends on the specific technology.

  Accessibility requirements such as Web Content Accessibility Guidelines, which is specifically designed for web content, can be tested using ACT Rules. Other accessibility requirements that would also be applicable to web technologies should also be testable with ACT Rules. Because some of those accessibility requirements may be applicable to technologies other than web technologies, the ACT Framework may not be suitable for every part of this requirement.

  For example, the User Agent Accessibility Guidelines 2.0 is applicable to web-based user agents, for which ACT Rules could be developed, but other technologies can also be used to develop User Agents, which are not web-based.

Choose one of the following and record your comments in Issue 5 (preferred) or in the comment box below.

Summary

(1 response didn't contain an answer to this question)

Details