- From: Wilco Fiers <wilco.fiers@deque.com>
- Date: Thu, 5 Nov 2020 16:20:53 +0100
- To: ACT Rules CG <public-act-r@w3.org>, Accessibility Conformance Testing <public-wcag-act@w3.org>
Received on Thursday, 5 November 2020 15:21:19 UTC
Hey folks, Here are the minutes to today's meeting: https://www.w3.org/2020/11/05-wcag-act-minutes.html In summary, the group discussed how to handle scenarios where browsers / screen readers behave differently from the specifications. The group was in full agreement that in the case where there is a specification, the specification should be used. Where there are known differences between browsers and specifications, a decision will need to be made on whether to include test cases that pass something that fails in a browser (or vise versa). This should allow implementors some flexibility on whether they pass or fail cases with known accessibility support issues. The ACT Task Force will come up with a process by which they can answer questions about whether to include or exclude test cases with known accessibility support issues. Thanks to all who attended! I think this is an important decision that would have taken us weeks to deal with otherwise. Much appreciated. -- *Wilco Fiers* Axe-core product owner - Co-facilitator WCAG-ACT - Chair ACT-R Join me at axe-con <http://deque.com/axe-con> 2021: a free digital accessibility conference.
Received on Thursday, 5 November 2020 15:21:19 UTC