scribe+
standup...
kathy - prepping for meetings and catching up so able to facilitate
trevor - two open PRs he is working on
<kathy> scribe+
Helen - working on behind-the-scenes
<kathy> Catherine: did the surveys
catherine-surveys
Scribe+
helen: updating transcript rules. taskforce asked to remove references to transcript from the a11y tree. big blocker is removal of the transcripts. jean-eves not keen because of braille users, etc.
<scribe> cont... transcript doesn't need to be in the tree to be accessible.
kathy - go back to survey responses and wilco's explanation states more a failure of 1.3.1. suggested removing it.
helen - audio transcript, video transcript and one more. shared link in pull request and jean-eves not happen with the change. wilco happy but jean-eves not so needs updating.
<scribe> cont - discussed autoplay instead of playing
<kathy> https://github.com/act-rules/act-rules.github.io/pull/2064
trevor - regarding "included in the a11y tree". agrees with Jean-eves. seems like you could pass the rule but still fails criteria. this is where the discussion lies.
helen - PR 2064. come back to this next week after people have a chance to look at it
kathy - another issue is whether the transcript needs to be visible and in the a11y tree. these two items are still open.
trevor - does markup have to be correct to link the rule? confused as to where the 1.3.1 relationship is established?
kathy - thinks wilco meant if something is inthe a11y tree it is a 1.3.1
trevor - needs to do a bit of research on this. not sure this is following the intent of linking 1.2.1 and 1.3.1
trevor - include 1.3.1 as a secondary requirement??
kathy - if we do that here, will also have to do it to many others.
helen - not feasible
kathy - undecided
catherine - also undecided
kathy - agree with helen, if past examples has to pass all the criteria
helen - jsut about transcript requirements. failure shoudl be if transcript is missing, not missing from the a11y tree
kathy - bring it up in the cg meeting?
helen - better to have it clarified here first and bring it back to cg.
kathy - options - transcript in a11y tree? or remove failed examples and keep in the a11y tree. let's being it up next week with more people present.
kathy - go over spreadsheet activities since last week meeting. any updates?
trevor - nothing specific but he needs to go and work on it.
kathy - has not updated her rules. waiting to hear back from ag if transcript has to be visible.
<kathy> https://github.com/w3c/wcag/pull/2057
kathy - wilco wanted us to take up this item.
<Helen> https://github.com/act-rules/act-rules.github.io/discussions/2124
helen - will share discussion with user feedback
helen - visible label but no acc name. then 4.1.2. if not associated, then it is 1.3.1. if labeled but doesn't meet name, then it is 2.5.3.
helen - agrees with scott... 1.3.1 not 4.1.2
kathy - could be multiple sc's failures. 4.1.2 and 1.3.1
helen - 4.1.2 could be secondary, not primary
kathy - if "some" AT, then it's a pass??
trevor - would leave as a fail but would give it supporting ... thinks it could fail multiple sc's. depends on scenario.
kathy - will leave discussion for next week for additional opinion
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: catherine, Helen, kathy, trevor Present: catherine, Helen, kathy, trevor No ScribeNick specified. Guessing ScribeNick: catherine Inferring Scribes: catherine 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: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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]