<scribe> scribe: dmontalvo

Call for review https://github.com/act-rules/act-rules.github.io/issues/461

Wilco: Three of those
... "Define what needs to change for focus indicator"
... Remove autocomplete example. I noted that we had an issue with one of the examples
... For the 2-week review, there is remove H43 to one of the table rules
... NOt maojr, but since we change the mapping, we have a 2-week review

Carlos: We were about to remove it from the background section, but it is still there.

Wilco: I think it is related. Can't it stay?

Carlos: It could be

Wilco: I don't think it should be removed.

Carlos: OK

Wilco: Is this still a useful agenda item? Originally we did them to make sure very change is discussed during the call, but it is not the case with the 1-week ones

Jean-Yves: I think it is useful. That help us having discussion that clarify some issues

Update from the ACT Task Force https://docs.google.com/spreadsheets/d/1OSkPFocXk4K3zYLnwS78WLsWO4PvE5yRcsauyefuIUI/edit?usp=sharing

Wilco: Most of the blocked rules have now been unblocked.
... Document has heading for non-repeated content: discussion under AG on whether headings are bypass blocks mechanisms. The group is devided, let's see what comes out of these discussions
... I assigned these to me because they are the same issue

Susan: Is it blocked because we don't want to send it to them until the take a decission

Wilco: Yes.

Jean-Yves: There is a techniques that discuss headings as a bypass blocks mechanisms

Wilco: They may make that one advisory
... The description track is not accessibility supported. The rule will still be around, but it won't be part of the composite
... There is some work in the Task Force to collaborate with WCAG3. There is a proposal where we are combining the methods with ACT-rules, will try to send to AG next week

Assigned issues: https://github.com/act-rules/act-rules.github.io/issues?page=1&q=is%3Aissue+is%3Aopen

Wilco: The semantic role I will try to do next week
... I did most of the WCAG3 stuff

<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/assigned/ajanec01

<Wilco_> https://github.com/act-rules/act-rules.github.io/pull/1649/files

Aron: Most of them will be fixed soon. PR #1649, you left a comment Wilco that would unchange is not accurate. I don't know if I am missing out soimething

Wilco: I think you are right

Aron: In #1432 they mention that if you have a combo box with content that is added to the DOM afterwards (in response to an event), is that an issue? Now the rule requires that additional content be present when the page is loaded, which is quite strict

Wilco: It always requires a text box, but the expanded thing is only required when the components is expanded
... Also, that is an owned element, not a required property. I think this is good, I am going to approve

<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/assigned/carlosapaduarte

Aron: Table header cells I am going to leave it for next weeks, all the other will be closed

Carlos: Nothing to update on. I would like to mention two of the issues
... Updating the "audio or video has on audio that plays automatically" I have deleted one of the rules. Jean-Yves suggests that instead of deleting the file we deprecate the rule.

Wilco: gree.

Carlos: Will update accordingly.
... Also using non-streaming audio . Will update the expectation so that any tester could test it. Also I need to work on a testing examples.
... If someone has a suggestions as to how we could get a live feed

Emma: All audio and video are non-streaming? Why do you need streaming examples?

Carlos: Because we added another rule that passes every time the video is live.

Emma: Did you change that then?

Carlos: Yes, we did. We were focusing on duration, but now we have concluded that looking at streaming versus non-streaming works better.

Emma: My suggestions is to do some sort of slow-TV, something broadcasting 24/7

Carlos: I have looked at all sorts of examples, but they state we can't use them pretty clearly

Emma: The other thing is to have something of your own that someone can trigger
... Because it is a live-stream it is not a file, it is just a lot of packages moving around

Wilco: Would we be able to use the camera on someone's machine when they are on the page?

Jean-Yves: You may not have a camera, or it might be switched off. Lots of privacy issues there
... Could we contact some of the sources you researched Carlos?

Emma: Also contact some of the streaming services, just checking if they have something available

Carlos: Will take a look

<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/assigned/EmmaJP

Todd: Will work on mine

Wilco: Emma, You have a PR with changes requested.

Emma: Not clear what to do here

<Wilco_> https://github.com/act-rules/act-rules.github.io/pull/1184

Wilco: Do you waant me to take a look at this?

Emma: There were some things around that we need to agree on

Wilco: Not sure if this change is actually needed

Emma: Something needs to change. We somehow need to make the distinction between all buttons, versus image buttons. We have lots of things where the text is very descriptive of the things that are in there
... The thing non-existing is not considered as a failure

Jean-Yves: We have been validating the rule in the TF, nobody has complained about it. There is also an issue on today's agenda that will touch on this

Emma: Now we have that a butotn that is not an image button has an accessible name, and also that an image button ahs an accessible name. Neither of them are related to SC 1.1.1

Jean-Yves: I agree that this is an artifitial applicability

Emma: Maybe adding "image button has descriptive accessible name"?

Jean-Yves: Yes

Emma: That is my proposal 6
... Which is not currently in the PR
... I am happy to do that

<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/assigned/Jym77

<Wilco_> https://github.com/w3c/wcag/issues/1936

Jean-Yves: Question about spaces in accessible name, discussed in AG, there is an issue in AG and my understanding is that it is OK for them to have spaces
... We will need to discuss that internally, not quite sure now how to do that

<Jean-Yves> https://github.com/w3c/wcag/issues/1936#issuecomment-868676987

Emma: Trimming at the beginning and the end should be OK
... NOt sure about the ones in the middle
... This is something kind of for an automatic tool to flag, and a person to decide

Jean-Yves: In any case we would need to update the rule

Aron: Is there place for such a rule? Seems very strict given the discussions

Jean-Yves: It seems the SC is here to stay, so does the sule.

Aron: Maybe it is worth asking again

Visible label (2ee8b8) inconsistency between pass and inapplicable https://github.com/act-rules/act-rules.github.io/issues/1618

Wilco: Talked about this one last time
... We concluded that we would add something to the background section, but not everybody agrees

Jean-Yves: MAybe that is enough to resolve that. My understanding is that it's OK as is

Wilco: Is everybody on the same page? If an image does not load, the alt is shown. The alt text is the same as the accessible name unless there is aria-label. Proposal is to mention that in the background section

Jean-Yves: I can take it on

How to preserve accessibility support test cases https://github.com/act-rules/act-rules.github.io/issues/1621

Wilco: We are getting to a point where some of the accessible support issues that we wrote are very old. At that time, we wrote up test cases, but these got lost. I was wondering: should we track what exactly we tested before we put some information in the accessibility support?

Emma: Do you mean a page that shows the test results?

Susan: Does it relate to user agents as well?

Wilco: One briwser dies not support titles in iframes, If we need to go back to that to see if something has changed, we need to create these again

Emma: Something like GitHub pages? Maybe similar to the gov.uk

Daniel: +1 for that, not sure it can be done in GitHub wiki

Wilco: It creates more work
... We will need to go back and create this data

Daniel: Not sure if we could take sometrhing from the Aria-testing group

Wilco: That could actually mean more work
... Does anybody thing this is a bad idea?

Emma: You have to create the use cases anyway, you just have to have place to point to and a date when it was tested

Wilco: I don't think we even want to publish that data. That might create possible conflicts
... I am inclined to put int in the repo, maybe a separate directory with accessibility support data, with each rule that has anything in that section getting its own file

Jean-Yves: We need to connect back the accessibility support with the test case
... If it is on the repo it is public, even if it is not published

Emma: It is very factual, it is not a judgment. We could add something in the background that this test case was done in this date

Jean-Yves: The rules already have a change log

Emma: The rule could mention the test cases and then link to a dated file

Wilco: : I would prefer to keep away from referencing this data. Even if it is public I don't think we should say that. I could very well be user error

Jean-Yves: That would be good if we can get people from user agents back and start some dialog

<Susan_H> sure Shadi..

Daniel: +1

<ToddLibby> Wouldn't be the first time I got hung up on. ;-) See you all next time!

<EmmaJ_PR> Dang ... I was hoping to say goodbye for now as my last thought.

<EmmaJ_PR> +1 to JYM comment

<shadi> SO SORRY EMMA!

<EmmaJ_PR> No worries ... I'll just come haunt you in your new job ;)

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: Jean-Yves, aron_, ToddLibby, CarlosD, shadi, Wilco_, Susan_H, EmmaJ_PR
Present: Jean-Yves, aron_, ToddLibby, CarlosD, shadi, Wilco_, Susan_H, EmmaJ_PR
Found Scribe: dmontalvo
Inferring ScribeNick: dmontalvo

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