W3C

- DRAFT -

Accessibility Conformance Testing Teleconference

12 Oct 2023

Attendees

Present
Helen, ToddL, Wilco, trevor, Daniel, thbrunet
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Helen

Contents


<thbrunet> I'll be a few minutes late today.

scribe+

ACT Standup

Wilco: Writing up the implementation section from TPAC work and feedback

Daniel: I reviewed a paper that Trevor sent ACT towards more conformance accessibility testing and pull requests

Trevor: Been finishing the paper so would like feedback before EOD
... I was working on the subjective applicability examples to use definition types for navigational mechanisms
... we will talk about it later

Tom: A few PRs and a discussion on invalid rules, like display none so not in the accessibility tree so invalid - would like more feedback on it

Todd: I am the liasion on heading is descriptive but I cannot find the issue to work on - did someone else pick it up?

<ToddL> https://github.com/act-rules/act-rules.github.io/issues/1601

<thbrunet> https://github.com/act-rules/act-rules.github.io/pull/2084 is the PR I mentioned.

Todd: The confusing statement open issue - I need a pointer

Helen: Opened a discussion

CFCs this week

Wilco: I wanted to action some rules ready for CFC - so will be sent today
... will look at these later this week, and will create a discussion thread on these rules

Recharter of AGWG

Daniel: We talked a few weeks on this - it is recharging, we will receive an email on this that you are no longer part of the group as you will need to rejoin it to make sure members are active
... invited experts will be followed up with individually - so we can keep you in this group

Wilco: We will invite you all regardless

WCAG 2.2 updates

Wilco: 2.2 hit recommendation last week. 4.1.1 is deprecated as an errata was issued for 2.0 and 2.1 on this
... the call for review passed for deprecating the 4.1.1 rules - these will happen by the end of the day unless a concern is raised
... we need to update the rules with 2.2 links.

<Wilco> github.com/w3c/wcag/

Wilco: Any questions about 2.2?
... We are working on some new rules for this too.

Todd: When do you need the help?

Wilco: Soon if possible?

Todd: I can do some if needed by the end of the month

Open issues & pull requests

Wilco: The heading is descriptive item - there are action items for this PR

Todd: Those were addressed

Wilco: Please share the details via email?
... I will put the Table header cell rule to CFC, Helen to check the transcript PR
... discusses who should have the HTML element item, and the status of all the "update needed" rules
... goes through open PRs and ask for updates
... anything missed?

<ToddL> https://github.com/act-rules/act-rules.github.io/pull/1926

Todd: Yes, 1926 - it looks like it has been merged?

Wilco: want to put it into CFC?

Todd: Yes - there were some minor issues that were opened

<ToddL> https://github.com/act-rules/act-rules.github.io/issues/1361

<ToddL> https://github.com/act-rules/act-rules.github.io/issues/1595

Wilco: This looks good to go into CFC after a quick review

Subjective exceptions in the applicability

<trevor> https://tbostic32-upgraded-acorn-vgv9jq7pg69fxw4x.github.dev/

<trevor> https://github.com/w3c/wcag-act/pull/539

<trevor> https://github.com/act-rules/act-rules.github.io/pull/2050

Trevor: I am still playing around with the different types of formats and applicable examples. The general consensus was yes this works for the headings
... I am now looking at Chris' PR "navigational mechanisms" and it is not defined in any WCAG documents
... reads out the Getting Warmer, Getting Colder and Examples
... How do you all feel about this?

Wilco: I need a bit of time to take it all in and digest it, but it is WCAG's problem about not defining the navigational mechinisms
... This is just a big unknown

Trevor: I was hoping this would help, but maybe the applicability needs to be updated but the rule is about navigation

Wilco: It is quite a vague item - for instance a link that takes you to another page is a navigation item

Trevor: So maybe something that takes you to another part of the site rather than the vague definition that could define an accordion

Wilco: Thoughts from anyone else?

Daniel: I agree - I am not sure if this is something WCAG needs to have defined as very open to interpretation

Wilco: It is too broad and vague and can still be subjective

Tom: I think the approach is getting warmer - but the definition is complicated

Trevor: I think if we get the approach agreed we can revisit this later

Helen: This is hard to define in an easy sentence - making it too hard
... maybe look at the trigger definition next week?

<Wilco> https://github.com/w3c/wcag-act/pull/541/files

Wilco: Please look at the above link as it will be on the agenda next week

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.200 (CVS log)
$Date: 2023/10/12 13:58:03 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: Helen, ToddL, Wilco, trevor, Daniel, thbrunet
Present: Helen, ToddL, Wilco, trevor, Daniel, thbrunet
No ScribeNick specified.  Guessing ScribeNick: Helen
Inferring Scribes: Helen

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]