Joint ACT-TF / ACT-R CG meeting next Thursday Nov 5

Hey folks,

I wanted to invite you all to a joint meeting of the ACT Task Force and the
ACT-Rules Community Group on November 5th 3pm CET / 9am ET. This will be a
60 minute meeting. See:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=ACT-TF&iso=20201105T15&p1=16&ah=1

IRC: http://irc.w3.org?channels=#wcag-act  (port: 6665 channel #wcag-act)
Zoom invite: https://mit.zoom.us/j/234301406
Password: Ask in IRC
OR, if you are a member of the task force:
https://www.w3.org/2017/08/telecon-info_act

*Agenda:*
- Introductions
- Accessibility support of test cases

*The goal of this meeting is to come up with answers to the following
questions:*

1. Should ACT rules enforce consistency, even where accessibility support
is inconsistent?

2a. If yes, how do we decide which (combination of) browsers/assistive
technologies should be considered and which should not?
2b. If no, how do we deal with this in test cases, and how does that change
what we consider a consistent implementation?

3. Do we need to change anything in the rules, or in how we present
implementations for this to be clear and transparent?


*Some background info:*
This question came up after me getting stuck updating the iframe has
accessible name rule. The problem with that rule is that accessibility
support for iframes is so different that I tried to write a rule that
worked specifically for the three major browser engines; Chromium, Gecko
and Webkit. That got some pushback, because things like iframe with
aria-label would fail the rule.

In the past we've worked around this issue in two ways. The first one is by
just ignoring the differences and not including test cases for it. There
are no test cases in existing accessible name rules that deal with
inconsistencies between browsers of accessible name computation.

The second way we've handled this is by writing rules that only fail in
certain browsers, and documenting that. An example of that is the meta
viewport rule, which only tests for issues in older browsers on mobile
devices.


I hope you'll all be able to attend.

Kind regards,

-- 
*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.