RE: [EXT] ACT TF Meeting Agenda Thursday 5 November

Regrets, I am going to be on vacation this week.

Thanks,
Trevor

From: Mary Jo Mueller <maryjom@us.ibm.com>
Sent: Monday, November 2, 2020 5:19 PM
To: Accessibility Conformance Testing <public-wcag-act@w3.org>
Subject: [EXT] ACT TF Meeting Agenda Thursday 5 November


See the agenda below for our Thursday meeting.

The ACT TF will be meeting on Thursday at 15:00 Central European Time (Length: up to 60 minutes). See:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=ACT-TF&iso=20201105T15&p1=16&ah=1

Scribe list: https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Scribe_Rotation_List
IRC: http://irc.w3.org?channels=#wcag-act<http://irc.w3.org/?channels=#wcag-act>  (port: 6665 channel #wcag-act)

Agenda:
Joint meeting of the ACT Task Force and the ACT-Rules Community Group
- 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.

Teleconference information (both zoom and dial-in):
https://www.w3.org/2017/08/telecon-info_act

Best regards,

Mary Jo
_____________________________________________
Mary Jo Mueller
Accessibility Standards Program Manager
IBM Accessibility
Phone: 512-422-4242

"If your actions inspire others to dream more, learn more, do more and become more, you are a leader." ~John Quincy Adams