IRC log of ag on 2019-09-18

Timestamps are in UTC.

23:21:02 [RRSAgent]
RRSAgent has joined #ag
23:21:02 [RRSAgent]
logging to https://www.w3.org/2019/09/18-ag-irc
23:21:04 [trackbot]
RRSAgent, make logs public
23:21:07 [trackbot]
Meeting: Accessibility Guidelines Working Group Teleconference
23:21:07 [trackbot]
Date: 18 September 2019
23:21:11 [AWK]
RRSAgent, this meeting spans midnight
23:21:17 [AWK]
Present: AWK
23:26:33 [Fazio]
Fazio has joined #ag
23:27:33 [Fazio_]
Fazio_ has joined #ag
23:34:42 [Chuck]
FYI: We are working on audio issues. Can't get in room audio to work.
23:35:00 [AWK]
ZAkim, agenda?
23:35:00 [Zakim]
I see 1 item remaining on the agenda:
23:35:01 [Zakim]
4. WCAG 2.2 SC initial reviews https://www.w3.org/2002/09/wbs/35422/wcag22reviews/ [from AWK]
23:35:06 [AWK]
Zakim, clear agenda
23:35:06 [Zakim]
agenda cleared
23:35:11 [Chuck]
present+
23:35:14 [Chuck]
scribe: Chuck
23:35:37 [Chuck]
AWK: Test
23:35:38 [AWK]
agenda+ AGWG Group dynamics and expectation setting
23:35:47 [JohnRochford]
present+ JohnRochford
23:35:55 [Makoto]
Makoto has joined #ag
23:35:58 [AWK]
agenda+ Silver topics
23:36:08 [MichaelC]
present+
23:36:16 [Fazio]
present+
23:36:20 [AWK]
agenda+ Finalise last WCAG 2.1 technique
23:36:39 [AWK]
agenda+ WCAG 2.2 Work
23:36:40 [Makoto]
present+
23:36:49 [AWK]
agneda?
23:36:52 [AWK]
agenda?
23:36:55 [MichaelC]
agenda: https://www.w3.org/WAI/GL/wiki/Meetings/TPAC_2019
23:40:52 [jamesn]
jamesn has joined #ag
23:42:56 [JakeAbma]
JakeAbma has joined #ag
23:43:27 [Ryladog]
Ryladog has joined #ag
23:43:46 [Ryladog]
Present+ Katie_Haritos-Shea
23:44:10 [JakeAbma]
present+ JakeAbma
23:44:22 [Chuck]
AWK: Start 15 minutes before top of hour
23:44:29 [alastairc]
present+
23:45:16 [Lauriat]
Present+
23:46:06 [Chuck]
AWK: All set?
23:46:17 [achraf]
achraf has joined #ag
23:46:30 [Chuck]
AWK: Welcome! Seen many at silver meetings. Now we transition to AGWG meeting. Time will be spent on silver.
23:46:34 [Chuck]
AWK: Review of agenda...
23:46:38 [achraf]
present+
23:46:51 [Chuck]
AWK: Time on group dynamics and expectations, then silver. Somewhere there will be a break.
23:47:16 [Chuck]
AWK: Within silver a bunch of topics, talking about the migration of existing content, assessing conformance models, pros and cons.
23:47:22 [Chuck]
AWK: Silver made progress on mon and tue.
23:47:34 [Chuck]
Shawn: I've some updated links to share.
23:47:57 [Chuck]
AWK: Some members will go address questions on our charter, and speak with some other members. There will be some chair shuffling.
23:48:30 [Chuck]
AWK: One last WCAG 2.1 technique to discuss for a full set of techniques for A and AA SC.
23:48:36 [Chuck]
AWK: for 1.3.5.
23:48:49 [Chuck]
AWK: We'll spend time on that, and shift into WCAG 2.2 which will finish the day.
23:48:56 [Chuck]
AWK: That's the main focus for tomorrow as well.
23:49:33 [Chuck]
AWK: 2.2 will be big focus. When charter is approved, we have a year to get 2.2 out the door. That includes wd, crs, techniques, etc. Lots of work to do.
23:49:40 [Chuck]
AWK: Any questions?
23:50:14 [Chuck]
Jake: Agenda of 2.2... in 2.1 first we made normative text, then techniques. Will we do that for 2.2?
23:50:26 [nicaise]
nicaise has joined #ag
23:50:26 [Chuck]
AWK: First bullet in 2.2 for agenda is reviewing process. In more detail.
23:50:38 [Chuck]
AWK: We need to spend some time on group expectations.
23:50:56 [Chuck]
AWK: Can we go around the room in 90 seconds and say who we are and company or invited expert.
23:51:02 [Chuck]
Nicaise, MS
23:51:05 [Chuck]
MC W3C
23:51:10 [Chuck]
David invited expert
23:51:26 [Chuck]
<various introductions>
23:51:49 [Chuck]
<observers introduced>
23:52:11 [DavidClarke_]
DavidClarke_ has joined #ag
23:52:11 [jamesn]
Present+
23:52:12 [Fazio]
David Fazio Invited Expert
23:52:15 [ReinaldoFerraz]
ReinaldoFerraz has joined #ag
23:52:21 [DavidClarke_]
present+
23:52:25 [Chuck]
AWK: Jake scribes after Chuck
23:52:27 [Chuck]
AWK: then Katie
23:52:30 [ReinaldoFerraz]
present+
23:52:38 [Chuck]
AWK: one more scribe... John
23:52:40 [laura]
present+ Laura
23:52:52 [DavidClarke_]
David Clarke, Invited Expert I18n, observing
23:52:54 [Chuck]
Nicaise: How does one put themselves in the q.
23:53:06 [mbgower]
mbgower has joined #ag
23:53:08 [Chuck]
AWK: q plus is the way. Good to add text related to question.
23:53:15 [DavidClarke]
present+
23:53:15 [JohnRochford]
present+ JohnRochford
23:53:48 [Chuck]
AWK: Need to discuss group expectations. Entering the new phase of work where we are very focused on 2.2 spec. If we learned anything, its now we get into difficult conversations.
23:53:58 [Chuck]
AWK: specific language, user needs, get a spec done, it's difficult.
23:54:10 [laura]
audio is great for me on Webex. Dialin didn’t work though.
23:54:16 [Chuck]
AWK: Anyone working on WCAG 2.1 would not say they got everything perfectly the way they want.
23:54:24 [Chuck]
AWK: 2.2 will be the same as well. There will need to be compromises.
23:54:33 [mbgower]
Present+
23:54:41 [Chuck]
AWK: What's important is that we are all on the same page on how we get there. Talking about some of the behavior and working norms we expect.
23:55:10 [Chuck]
AWK: This crosses W3C. At Chair lunch this was half of the agenda. Dispute resolution, make working progress smoother, better, more inclusive.
23:55:28 [Chuck]
AWK: We want to do that. Everyone wants to do that. But we want a conversation with everyone, highlight some resources we have at W3C
23:55:33 [Chuck]
AWK: We can level set around that point.
23:55:59 [Chuck]
AWK: Some of the things we think about... starting points for norms. Without making a long list, we have 5 things that we are putting forward as the norms.
23:56:14 [Chuck]
AWK: To see if anything should change or add.
23:56:40 [Chuck]
Chuck: can you paste in these five bullets?
23:56:42 [laura]
Yes. Audio is fine.
23:56:54 [Chuck]
1) Assume positive intentions from others.
23:57:03 [Chuck]
2) Treat others with respect you expect to be treated with.
23:57:08 [Chuck]
3) Take an inquiry stance.
23:57:11 [JohnRochford]
Order of operations Map WCAG to Silver structure For each guideline-level grouping, identify user needs Identify tests to validate meeting user needs Write methods to meet the tests Write the top-level guideline to communicate what the methods provide
23:57:20 [Chuck]
4) Ground statements in evidence.
23:57:25 [Chuck]
5) Hear all voices.
23:57:44 [Chuck]
AWK: This is something for when discussions are difficult, it's hard to remember.
23:57:48 [JohnRochford]
Ah, sorry Chuck. I did not see you were already adding the bullets when I pasted them in.
23:57:57 [Chuck]
AWK: for #2, very standard, but bears mentioning.
23:58:21 [Chuck]
AWK: #3, in group discussions, people get into reaction mode when someone says something and people strongly want to react against it ... "that's wrong!"
23:58:51 [Chuck]
AWK: The point of this one is that it's important to in working with other people, if someone says that something should work a specific way, we want to encourage questions to detemine the basis for that perspective.
23:59:18 [Chuck]
AWK: To get at the underlying point and understand the viewpoint. And questions help to analyze the point in a reflective manner.
23:59:36 [Chuck]
AWK: Much more welcoming. As opposed to digging in heels.
00:00:02 [Chuck]
AWK: It can turn into a situation where 12 people say one thing and 2 say another... we've determined consensus, but 2 people haven't had enough inquiry.
00:00:19 [Chuck]
AWK: Grounding statements in evidence is critical as well.
00:00:51 [Chuck]
AWK: No good examples, but we can say "this should work a way" or "this does work a way", make sure you are clear about it... Version of JAWS you use may make it work that way.
00:01:17 [Chuck]
AWK: But does that work in other permutations? We need to look at all the evidence. I think that making sure we are being deliberate will be valuable.
00:01:40 [Chuck]
AWK: Hearing all voices, which means listening to all perspectives. As a chair (can be hard to remember) is actively get more people involved.
00:02:04 [Chuck]
AWK: There are times when it's Alastair and Katie and David (as an example), I think that as a chair I can get other voices to participate.
00:02:18 [Chuck]
AWK: To get positive affirmation or hear other perspectives.
00:02:35 [Chuck]
AWK: As we are looking at first public working drafts as crs, we are looking for voices outside of wg.
00:03:02 [Ryladog]
q+
00:03:08 [Chuck]
AWK: That's our list. 5 starting points. What do people think, do they resonate? Anything else? Should we modify these? How do we handle these things?
00:03:24 [Chuck]
AWK: We'll have contentious conversations, and the goal is to have a consensus.
00:03:29 [Chuck]
AWK: Any thoughts?
00:03:33 [alastairc]
ack ry
00:03:59 [Chuck]
Katie: Not limited to this wg, the instances I was involved in where I mis-behaved, I reacted to my perception of bullying. I like that we want to hear other voices.
00:04:26 [Chuck]
Katie: Because of bullying, other voices weren't speaking up, and they didn't want to engage in that. It's important to try and counter that. I did not succeed before. I like these goals.
00:04:36 [Fazio]
Appreciative Inquiry is a good technique
00:04:49 [DavidClarke]
q+
00:04:57 [AWK]
ack david
00:05:03 [Fazio]
Yes ("I hear you"), and?
00:05:08 [Joshue108]
Joshue108 has joined #ag
00:05:25 [Chuck]
David: When I've been in other wg as well as my one, one of the things is that I've seen in the past (but not in recent years) people divide on personal lines.
00:05:34 [Makoto]
Makoto has joined #ag
00:05:55 [Chuck]
David: katie and I may disagree... if I am not careful, I may get into a state where I disagree with her in the future because I disagree with her now. It's important to not get in that mindset.
00:06:18 [Chuck]
David: Whatever the discussion point is, they get compartmentalized, and it's not based on an individual.
00:06:21 [AWK]
q?
00:06:29 [Chuck]
David: It's just to be aware of it and keep yourself out of individualizing it.
00:06:51 [Chuck]
Michael: Any suggestions? You are suggesting self awareness. Any idea on how to steer people?
00:07:16 [Chuck]
David: Let's say I automatically object to Katie, and someone says to me.. "last week didn't you agree with her, why disagree now?" It's a good gentle approach.
00:07:20 [KimD]
KimD has joined #ag
00:07:23 [KimD]
Present+
00:07:30 [Chuck]
David: The other is to call it out: "WHY do you think Katie is wrong?"
00:07:35 [JohnRochford]
q+
00:07:54 [Chuck]
AWK: There's valid in having evidence. I may disagree with someone that I feel is always wrong... when a point is structured around data...
00:08:14 [Chuck]
AWK: That can be broken down much more, it makes it harder for me to keep that wall and resistance up against those points.
00:08:29 [Chuck]
AWK: I can work on pieces I agree with and the pieces I don't. That's very valuable.
00:08:31 [AWK]
ack jo
00:09:07 [Chuck]
John: As a person who is legally blind, I don't have the advantage of detecting upset people via non-verbal queues. I wonder if it's ok that if I think it's happening, if I ask an open question? What should I do?
00:09:19 [Chuck]
Alastair: Everyone over a teleconference (no visual queues)
00:09:48 [Chuck]
Michael: some people with social challenges may not be able to interpret tone of voice or facial expressions.
00:09:52 [JohnRochford]
q-
00:10:09 [Lauriat]
q+ to offer my approach to what John raised.
00:10:11 [Chuck]
David: Everyone is difference, take a moment to breath, realize that we are all here for the same reason. Take a moment and have an open conversation.
00:10:28 [Chuck]
John: Doesn't address my question. What should I do, what should happen, how can I be helped?
00:10:32 [AWK]
ack sh
00:10:38 [alastairc]
ack la
00:10:38 [Zakim]
Lauriat, you wanted to offer my approach to what John raised.
00:11:00 [Chuck]
Shawn: My approach to that, I try to do pre-emptively if I see someone else struggling. If I think that I've come across poorly, I'll take a breath and ask how that person thinks I sounded.
00:11:31 [Chuck]
Shawn: I can correct that if necessary. Again based on facts. If someone's upset it may be because you came across wrong. If you start off with checking that.
00:11:58 [Chuck]
Shawn: Flip side... if I am upset because of what someone said, I'll try and mirror the statement back, rephrase, the words may not mean the same thing to them.
00:12:03 [DavidClarke]
q+
00:12:05 [Chuck]
Shawn: That will bring up the disconnect.
00:12:30 [Chuck]
John: Is there anything we as a group to help people who can't detect that?
00:13:10 [Chuck]
Shawn: Someone prompts "John you may be coming across wrong"... stop things from continuing off the cliff, and get everyone back on the same page.
00:13:15 [Chuck]
Shawn: There are other possibilities.
00:13:49 [Chuck]
Mike Gower: I count on the chairs on remote calls to provide the visual equivalence. Seeing blank faces, etc. To understand what's going on in the room.
00:14:10 [Chuck]
Katie: A lot of our meetings are digitally and on the phone, lots of people aren't seeing visual queues. It helps to verbalize.
00:14:25 [Chuck]
Katie: The ability to determine from a tone of voice if someone is upset is another area of sense.
00:14:35 [laura]
laura has joined #ag
00:14:37 [Chuck]
AWK: I think that ... David...
00:14:38 [AWK]
q
00:14:40 [alastairc]
ack da
00:14:40 [AWK]
q?
00:15:00 [Chuck]
David: Agree with ... the idea of Chair intervening if char is in position to observe. One reason people do get upset is because people misunderstand.
00:15:35 [Chuck]
David: Simple misunderstandings, one thing that happened a while ago was a relatively contentious motion. Someone said "should we table it", and q was "Do you REALLY want to?"
00:15:53 [jeanne]
jeanne has joined #ag
00:16:08 [jeanne]
rrsagent, make minutes
00:16:08 [RRSAgent]
I have made the request to generate https://www.w3.org/2019/09/18-ag-minutes.html jeanne
00:16:10 [Chuck]
David: People got upset. The concept was to put asside for future discussion. UK/Brittish was that we were going to vote on it. The identical words in the same language could cause misunderstanding.
00:16:48 [Chuck]
David: the "Please can you rephrase it" will often sort out those difficulties. Equally if you aren't sure if someone is upset, say "I'm sorry if I upset you", or "are you happy with..."
00:17:05 [Chuck]
David: Trying to keep communication open. Be aware that some people in wg aren't working in their best language.
00:17:39 [Chuck]
AWK: Yes paying attention to tone of conversation that Alastair and I strive to do, as does Michael. I don't think people should need to wait for us to notice that things are strained.
00:18:12 [Chuck]
AWK: I suggest that people should be confortable raising issue themselves. Ask some of those questions. For me if Alastair is away or I'm away... Chair is very loaded.
00:18:51 [Chuck]
AWK: I can't guarantee I'll catch every instance, sometimes issues bubble up. There's no doubt that we'll check every specific meaning. "Do you mean stop or vote"?
00:19:14 [Chuck]
AWK: We'll progress one step or 2 steps beyond where we prefered we stopped. I think that as long as we can identify take a step back, take a breath...
00:19:55 [Chuck]
AWK: "Did you actually mean this?" Or "This is what I think I'm hearing you say". Hopefully has smoother progress. Maybe we've got 5 minutes to get things done, maybe we shouldn't be pressured into finishing.
00:20:03 [AWK]
q?
00:20:25 [Chuck]
Alastair: Sometimes we try and summarize where a discussion has gotten to, which helps to determine if we understood properly.
00:20:32 [Chuck]
AWK: Any other points?
00:21:02 [Chuck]
Nicaise: Some information can be very sensitive. If we put too much burden on the speaker over expressing their views, that can put burden on speaker.
00:21:15 [Chuck]
Nicaise: Where frank and open conversation is needed, I prepare myself.
00:21:39 [Jemma_]
Jemma_ has joined #ag
00:21:44 [Chuck]
AWK: There's a balance to that. If you assume that someone has a positive intention, you can ask question to clarify, and maintain the positive view of intentions. You can get down to the facts.
00:22:12 [Chuck]
AWK: IT's pretty common in human interactions that you react to that. This exercise in part is to slow down the reaction, and think about things before reacting.
00:22:52 [laura]
laura has joined #ag
00:22:54 [Chuck]
AWK: If that ... I think that in my mind some of that is interpreted as "I should not be as sensitive..." and I think it's about being more analytical and probing, to determine if I'm justified in being upset or if I misunderstood something.
00:23:00 [Chuck]
AWK: All in agreement?
00:23:16 [alastairc]
q?
00:23:56 [Chuck]
AWK: Anything that you feel we can better do to support the practice of these things? I know there are times when I haven't done the things I need to do as well as I could.
00:24:14 [Chuck]
AWK: What other types of support people Alastair, I (AWK) and Michael can do.
00:24:38 [Chuck]
Shawn: Logistics... are these slides being shown in webex.
00:24:53 [Chuck]
Chuck: They are in twice.
00:24:54 [AWK]
q?
00:24:55 [Ryladog]
q+
00:24:59 [AWK]
ack r
00:25:31 [Chuck]
Katie: I would say that my frustration came a couple of times because I felt unheard. If we could take about it with all 3 of you together if someone has an issue.
00:25:59 [Chuck]
AWK: Absolutely. We'll talk about W3C's documents, there's a process document for formal objections. I think we are talking about avoiding that.
00:26:30 [Chuck]
AWK: We want poeple to feel comfortable asking questions of eachother. If that doesn't work, talking to us chairs.. If it's about myself or Alastair, we'll be receptive about taking about ourselves.
00:26:41 [MichaelC]
q+
00:26:48 [Chuck]
AWK: If that doesn't work, talking with the other two chairs about the subject is perfectly fine.
00:26:54 [AWK]
ack m
00:26:57 [Chuck]
Katie: Thinking about you 2 and Michael.
00:27:25 [Chuck]
Michael: I'm hearing suggestions for listening to others, and when expressing yourself making sure you are heard accurately. If you feel you aren't being heard.
00:27:47 [Jemma_]
present+ JaEunJemmaKu
00:27:52 [Chuck]
Michael: Say that you feel you aren't being heard. If that doesn't work, that's when the frustration starts building. We could build a cycle of self feeding tention.
00:28:14 [Chuck]
Michael: That might be the time to send an IRC message stating that you feel you aren't being heard.
00:28:38 [Lauriat]
q+ to mention checking with others, depending on comfort levels.
00:28:43 [Chuck]
Michael: May make a private suggestion on how to phrase. If that doesn't work, then come to us. A set of escalating tasks. As much as possible do them at the base level.
00:28:58 [Chuck]
Michael: Learn to express and learn to listen, and have these other escalated options available.
00:29:25 [Chuck]
Alastair: Whoever... if all three of us are on the call, and the 2 that aren't chairing, can receive messages and react. Or after the meeting we can discuss.
00:29:33 [Chuck]
Alastair: That does happen now.
00:30:03 [Chuck]
AWK: I would encourage people to bring things up BEFORE reaching boiling point. Makes it smoother.
00:30:27 [Chuck]
AWK: Why the conversation is important because we are heading into a time of pressure... deadline is coming, don't have time to worry about feelings, but takes longer if we don't.
00:30:36 [Chuck]
AWK: Won't result in high quality.
00:31:21 [Chuck]
AWK: Any other thoughts?
00:31:28 [AWK]
q?
00:31:33 [AWK]
ack la
00:31:33 [Zakim]
Lauriat, you wanted to mention checking with others, depending on comfort levels.
00:31:55 [Chuck]
Shawn: Another response to that and a q. The response is for situations where someone feels upset, coming to a chair or Michael can feel like escalating, and may not be sure that's what you want to do...
00:32:35 [Chuck]
Shawn: If I'm in that situation, I'll do a sanity check with a peer. Ask for their advice and perceptions. Sometimes maybe I'll be informed that I took it the wrong way, or I'll be instructed to advance to Michael.
00:32:52 [Chuck]
Shawn: Sometimes people who are upset don't want to prolong the experience.
00:33:24 [Chuck]
Shawn: katie, you felt that you were bullied. Having the person who feels bullied be responsible for bringing that up sometimes doesn't work. How do WE handle those cases?
00:33:42 [Rachael]
Rachael has joined #ag
00:33:49 [Chuck]
AWK: Someone who feels that they are feeling bullied, we encourage them to talk to us, we want to help. In the group, we've worked together often enough.
00:33:49 [MichaelC]
q+
00:34:06 [Chuck]
AWK: We can and should be advocates for eachother. The chairs need to pay attention to people being engaged.
00:34:37 [Chuck]
AWK: That's another piece. Similarly, I mentioned a while ago, hearing all voices, actively probing among the group so that if the conversation is dominated by some people, bring in other people...
00:35:01 [Fazio]
The open door policy of just being able to have a matter of fact conversation about how you're feeling about what's going on in the group with Michael, or a Chair, without it being an escalation I think goes along way
00:35:09 [Chuck]
AWK: So the person who feels bullied has voices in their support, but making sure if someone goes quiet we can actively engage them and pull them back in and make sure they understand their opinions are valued.
00:35:37 [Chuck]
AWK: If someone is feeling bullied, someone has to notice. Either the person, chairs, staff contact, or others in the group. All should feel empowered to raise concerns.
00:35:57 [Fazio]
Many times people just need time too vent. Actually psych studies have identified an exact number of minutes a person needs to vent when feeling upset to deescalate situations
00:36:01 [Chuck]
AWK: Alastair could be shutting down Chuck, shouting and yelling... does that... are there other things we should be doing?
00:36:22 [Chuck]
Shawn: Open question. To bring up things you can talk through, and to raise the point that it is all of our responsibility.
00:36:32 [Chuck]
Shawn: To try and stop them going south.
00:36:48 [Fazio]
+1 on the sanity check
00:36:56 [Chuck]
Michael: Sanity check is a good thing. Sometimes it can be someone you trust who is like minded, sometimes it can be someone who isn't like minded.
00:37:27 [Chuck]
Michael: Bullying is a tough issue... because sometimes leadership may be the source. If you don't feel comfortable coming to us, sanity checking is helpfull..
00:37:30 [JohnRochford]
JohnRochford has left #ag
00:37:32 [Rachael]
present+
00:38:04 [Chuck]
Michael: We may not notice, it could be viewed as a simple disagreement rather than bullying. Having someone else speak on your behalf COULD be an option.
00:38:17 [jeanne]
present+
00:38:34 [Chuck]
Michael: If that doesn't feel like an option, there are escalation paths besides us 3. You can go to Judy or Phillip. You should use them if you feel you can't use the lower ones.
00:38:53 [Chuck]
AWK: Some W3 resources: Code of conduct.
00:38:54 [alastairc]
https://www.w3.org/Consortium/cepc
00:39:11 [Chuck]
AWK: <reads from coc>
00:39:22 [alastairc]
New version: https://w3c.github.io/PWETF/
00:39:43 [Chuck]
AWK: The new version in development digs in much more to additional details around types of unacceptable behavior. Whether or not it's offensive comments, threats of violance...
00:39:51 [Chuck]
AWK: Fortunately we've never faced that.
00:40:21 [Chuck]
AWK: There's much more in here on details, micro-aggressions, talking over, feigning suprise at lack of knowledge. Lots of detail. It's not finalized.
00:40:39 [Chuck]
AWK: We have not fully digested it. It's a valuable tool for the W3C. All WG need to navigate.
00:41:00 [Chuck]
AWK: Also link to process document. Progression of a spec to rec, contacts, formal objections, etc.
00:41:10 [Chuck]
AWK: Any additonal comments? We can stop and move on.
00:41:59 [jeanne]
rrsagemt, make minutes
00:42:00 [JohnRochford]
JohnRochford has joined #ag
00:42:18 [JakeAbma]
scribe: JakeAbma
00:42:33 [jeanne]
s/ rrsagemt, make minutes//
00:42:37 [AWK]
zakim, take up item 2
00:42:37 [Zakim]
agendum 2. "Silver topics" taken up [from AWK]
00:42:47 [jeanne]
rrsagent, make minutes
00:42:47 [RRSAgent]
I have made the request to generate https://www.w3.org/2019/09/18-ag-minutes.html jeanne
00:42:55 [Jemma_]
https://docs.google.com/document/d/1aCRXrtmnSSTso-6S_IO9GQ3AKTB4FYt9k92eT_1PWX4/edit
00:44:09 [Lauriat]
Agenda: https://www.w3.org/WAI/GL/wiki/Meetings/TPAC_2019#Thursday.2C_19_September_2019
00:44:27 [alastairc]
Wiki page with the links we're about to look at: https://www.w3.org/WAI/GL/wiki/Meetings/TPAC_2019#Thursday.2C_19_September_2019
00:44:36 [Lauriat]
Project Plan Needs working doc: https://docs.google.com/document/d/1zFgVcDUMSOrZ5nnGRocs2pZYkqOhwdyMU_Z62_CedbQ/edit
00:44:54 [JakeAbma]
SL: 4 things to talk through
00:45:28 [JakeAbma]
SL: starting with Silver Project Plan Needs
00:45:59 [JakeAbma]
SL: how can we get SIlver and the overall working group working on SIlver in near future
00:46:31 [JakeAbma]
SL: we'll make more projects with some people working on it with expertice
00:46:42 [circ-user-8nvLo]
circ-user-8nvLo has joined #ag
00:47:09 [JakeAbma]
SL: starting with Explainer doc for on-boarding, etc.
00:47:24 [kirkwood]
kirkwood has joined #AG
00:48:26 [circ-user-6e7w9]
circ-user-6e7w9 has joined #ag
00:48:42 [JakeAbma]
SL: we need to know the bar for what to write, after that we can start picking up work we feel comfortable with in whatever way we chose to work
00:49:28 [JakeAbma]
SL: we need to prepare for spring 2020 when much more people will start working on SIlver
00:49:33 [alastairc]
q?
00:50:34 [AWK]
ack m
00:50:58 [JakeAbma]
SL: we need people with managements experience for project plans and keeping it up to date
00:52:34 [JakeAbma]
SL: we do different things in parallel, next to content we split up to work on a conformance model which is very rough at the moment
00:53:49 [AWK]
q?
00:54:07 [Lauriat]
https://www.w3.org/WAI/GL/task-forces/silver/wiki/How_to_evaluate_Conformance_Proposals
00:54:21 [JakeAbma]
SL: continue with How to evaluate Conformance Proposals
00:55:06 [JakeAbma]
SL: conformance models are complicated, in order to asses there are different dimensions on how they might work
00:55:30 [JakeAbma]
SL: we look at how the conformance model works against requirements
00:56:23 [JakeAbma]
SL: some are directly related, like Requirement 3.1 Multiple ways to measure
00:56:52 [JakeAbma]
SL: other are more indirectly, like Requirement 3.5 Readability/Usability
00:57:26 [JakeAbma]
SL: Requirement 3.1 Multiple ways to measure
00:57:32 [Lauriat]
Requirement 3.1 Multiple ways to measure: All Silver guidance has tests or procedures so that the results can be verified. In addition to the current true/false success criteria, other ways of measuring (for example, rubrics, sliding scale, task-completion, user research with people with disabilities, and more) can be used where appropriate so that more needs of people with disabilities can be included.
00:57:45 [AWK]
(https://www.w3.org/WAI/GL/task-forces/silver/wiki/How_to_evaluate_Conformance_Proposals#Requirement_3.1_Multiple_ways_to_measure)
00:59:09 [JakeAbma]
SL: we'll Check that the conformance model serves more needs of people with disabilities
00:59:35 [JakeAbma]
SL: in two ways as proposed, 1. Testing with proposed Success Criteria from Low Vision, Coga, and Mobile Task Forces
00:59:48 [JakeAbma]
SL: the other: Stakeholder interviews with Low Vision, Coga, and Mobile Task Forces, and other stakeholders
01:02:07 [JakeAbma]
SL: does this conformance make it easier or more difficult to get SC in, we need to check that it will not be more difficult than with the current model
01:02:13 [AWK]
Deferred items from WCAG Github: https://github.com/w3c/wcag/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3ADeferred
01:02:19 [JakeAbma]
SL: that would be bad if we make it more difficult
01:02:48 [AWK]
https://github.com/w3c/wcag/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3AWCAG.next+
01:03:15 [JakeAbma]
AWK: searching for deferred issues / SC in Github to be used for checking
01:03:45 [JakeAbma]
SL: next, Requirement 3.2 Flexible maintenance and extensibility
01:03:47 [AWK]
(https://www.w3.org/WAI/GL/task-forces/silver/wiki/How_to_evaluate_Conformance_Proposals#Requirement_3.2_Flexible_maintenance_and_extensibility)
01:03:51 [Lauriat]
3.2 Flexible maintenance and extensibility: Create a maintenance and extensibility model for guidelines that can better meet the needs of people with disabilities using emerging technologies and interactions. The process of developing the guidance includes experts in the technology.
01:04:05 [Jemma_]
+q
01:04:50 [JakeAbma]
SL: we want to Pick at least 2 emerging technologies
01:04:56 [Jemma_]
how would you define "emerging" technology?
01:05:03 [AWK]
ack je
01:05:26 [JakeAbma]
Jemma: how do you define emerging technologies
01:06:24 [JakeAbma]
SL: Good question, difficult to answer, but most likely technologies NOT present in WCAG right now, like AR / VR etc.
01:07:24 [JakeAbma]
SL: we must be clear that we don't include emerging technologies which might not be there after a while, like 1 / 2 years, we must be careful to right guidance for them
01:08:53 [JakeAbma]
SL: we might also look at full desktop touch etc. So same underlying technologies but different uses of them
01:10:51 [JakeAbma]
SL: we've been talking about removal or editing of possible guidance, how does this work out with a possible point system, conformance etc.
01:11:19 [JakeAbma]
SL: next, Creation & Platform: Stakeholder interviews with SMEs in the area of that emerging technology
01:12:04 [JakeAbma]
SL: most of the WG members know web very well, but we might need to add people for other expertice
01:12:17 [JakeAbma]
SL: SME = subject matter experts
01:13:10 [AWK]
q?
01:13:11 [Jemma_]
+q
01:13:20 [JakeAbma]
David: have you had some discussions with member companies?
01:13:25 [JakeAbma]
SL: not yet
01:14:07 [AWK]
q?
01:14:23 [JakeAbma]
Katie: does gaming fit?
01:14:44 [AWK]
ack je
01:14:58 [JakeAbma]
SL: yes, gaming can fit
01:15:26 [Jemma_]
my questions is about the relationship with Flexibility and the voice of stakeholders.
01:17:02 [JakeAbma]
Jemma: Stakeholder interviews are involved, how do we find the people that don't know, get them involved?
01:17:29 [JakeAbma]
SL: my view is the following list, to get them involved
01:17:38 [Fazio]
q+
01:17:38 [Lauriat]
Stakeholder map, for those interested: https://docs.google.com/spreadsheets/d/128vPnCweXN9t4JBG7-AOeBhT-KquaWXcCsi3H-f8u94/preview
01:19:09 [JakeAbma]
SL: of course we need to set the line somewhere, still working on the correct approach
01:19:23 [achraf]
q+ to say can be part
01:19:48 [JakeAbma]
Katie: we got to do something outside of the English language
01:19:51 [alastairc]
ack da
01:19:55 [alastairc]
ack fa
01:20:11 [JakeAbma]
Katie: they might have other AT, ways of interacting etc.
01:20:25 [mbgower]
q+ to say regarding emerging technology, do we have good definitions of what constitutes 'web'? Do we have a handle on how to delineate what parts of an online game like, say Overwatch, are covered by AG?
01:20:59 [JakeAbma]
David: we need to engage not only the dominant players
01:21:05 [DavidClarke]
q+
01:21:11 [alastairc]
DavidF talks through national & international rehabilitation agencies that could be source of stakeholders.
01:21:29 [alastairc]
ack ac
01:21:29 [Zakim]
achraf, you wanted to say can be part
01:22:36 [JakeAbma]
SL: we made the stakeholder map to see how it maps and we we can bring to researchers
01:23:02 [JakeAbma]
SL: so we can map out the space and helps in our search
01:23:04 [AWK]
ack m
01:23:04 [Zakim]
mbgower, you wanted to say regarding emerging technology, do we have good definitions of what constitutes 'web'? Do we have a handle on how to delineate what parts of an online
01:23:05 [alastairc]
ack mb
01:23:07 [Zakim]
... game like, say Overwatch, are covered by AG?
01:23:31 [JakeAbma]
MG: do we have a handle on how we constitute "web"?
01:23:34 [JakeAbma]
SL: No
01:23:57 [JakeAbma]
AWK: we'll talk about this in combination with the charter, together with AC
01:24:21 [alastairc]
q?
01:24:22 [JakeAbma]
SL: it's complicated , the chairs will figure it out!
01:24:27 [alastairc]
ack da
01:25:13 [JakeAbma]
DC: there's a translation WG, please reach out if you need help
01:25:51 [Lauriat]
s/translation WG/internationalization WG/
01:26:03 [JakeAbma]
DC: in the internationalisation WG we have lots of contacts willing to help out
01:26:06 [Jemma_]
for example, Korea has KWCAG to localize WCAG to Korean context.
01:27:55 [JakeAbma]
Katie: take into account also the cultural aspects
01:28:18 [Lauriat]
q?
01:29:14 [Jemma_]
+1 Katie's suggestoin
01:29:26 [Jemma_]
s/suggestoin/suggestion
01:31:36 [Jemma_]
Katie suggested to have a meeting with international stakeholders if Silver TF project time line allows.
01:40:19 [laura]
rrsagent, make minutes
01:40:19 [RRSAgent]
I have made the request to generate https://www.w3.org/2019/09/18-ag-minutes.html laura
01:40:53 [Makoto]
Makoto has joined #ag
01:48:19 [AWK_]
AWK_ has joined #ag
01:54:00 [Ryladog]
Scribe: Ryladog
01:54:49 [Ryladog]
Jeanne: What is a good idea?
01:55:05 [AWK]
Requirement 3.4 Technology Neutral
01:55:07 [Lauriat]
Requirement 3.4 Technology Neutral: Guidance should be expressed in generic terms so that they may apply to more than one platform or technology. The intent of technology-neutral wording is to provide the opportunity to apply the core guidelines to current and emerging technology, even if specific technical advice doesn't yet exist.
01:55:14 [Ryladog]
Having and an Internationale Accessibility AT Users for input into silver
01:55:21 [AWK]
(https://www.w3.org/WAI/GL/task-forces/silver/wiki/How_to_evaluate_Conformance_Proposals#Requirement_3.4_Technology_Neutral)
01:55:22 [DavidClarke]
DavidClarke has joined #ag
01:55:48 [DavidClarke]
present+
01:55:54 [Fazio]
Fazio has joined #ag
01:55:57 [Ryladog]
Requirement: Technology Neutral 3,4
01:56:44 [Ryladog]
SL: Tech Neutral has the same braeking out, for emerging tech
01:57:13 [Ryladog]
...for the CM we want tomake sure that this deosnt prohibit this. The CM affects this
01:57:48 [Ryladog]
AWK:I think with in WCAG this is individual SC
01:57:55 [ReinaldoFerraz]
ReinaldoFerraz has joined #ag
01:58:08 [ReinaldoFerraz]
present+
01:58:25 [Ryladog]
SL: We can talk about Language of environment rather than page (as in 3.3.1)
01:58:32 [Ryladog]
SL: Other tests?
01:58:51 [Ryladog]
Nicaise: Emerging ? what does that mean
01:59:43 [Ryladog]
SL: In the past it meant keyboard UIs, and now we have many like touch UI models. Emerging UI could be platform or content
02:00:31 [Ryladog]
AWK: MS Game system uses gestures as a UI, and it might be the only way. That interaction type we haent really dealt with
02:00:41 [Lauriat]
Requirement 3.5 Readability/Usability: The core guidelines are understandable by a non-technical audience. Text and presentation are usable and understandable through the use of plain language, structure, and design.
02:00:44 [AWK]
(https://www.w3.org/WAI/GL/task-forces/silver/wiki/How_to_evaluate_Conformance_Proposals#Requirement_3.5_Readability.2FUsability)
02:01:26 [Ryladog]
SL: in the context oftest CM, this is largely making sure that wedont make the GL incomprehensible
02:01:50 [Ryladog]
...we have tests in here checking against the style guide
02:02:09 [Ryladog]
Take the 4 existing success criteria and 3+ new guidance proposals (from Test of 3.4 Technology Neutral), and check against our style guide to see whether we can still meet it. Stakeholder interviews with Cognitive Task Force, plain language experts, translation (non-native English speaker) experts.
02:02:12 [AWK]
q?
02:02:32 [alastairc]
Jake: Is there a plan B if the plain language/readability part doesn't work?
02:02:41 [Ryladog]
SL: I have tagged David for i18n
02:03:00 [Ryladog]
JA: Understandable by a non-tect audeince.
02:03:53 [Ryladog]
SL: Have top level which is tech nurtral, and have the paltform specific guidance that would have to include wording that was specifc in that technology
02:04:32 [Ryladog]
Alastair: Plan B would be seperate content
02:04:38 [Ryladog]
SL: well that is plan A
02:05:09 [Ryladog]
JohnR: so you also have to think about the tech for dev language
02:05:30 [Ryladog]
SL: It has to meet the Readability
02:06:10 [jeanne]
q+ to say the plain language prototype plan
02:06:12 [Ryladog]
JohnR: A common tech a plain langauge then parens '(tech term)'
02:06:16 [jeanne]
q-
02:06:24 [DavidClarke]
q+
02:06:28 [Ryladog]
DF: we are going through this right now with COGA
02:06:36 [alastairc]
q?
02:06:40 [alastairc]
ack da
02:06:42 [Ryladog]
...creating glossaries of term
02:07:37 [Ryladog]
DavidC: Something called Simplified English for people whose first lang, that might be nice to look at and other langauges simplified grammarsuage is not English
02:08:04 [Ryladog]
...dont use term that is a noun and verb
02:08:31 [JohnRochford]
JohnRochford has joined #ag
02:08:59 [Ryladog]
SL: yes, but this is a little too in the weeds for this. But matters alot for the style guide
02:09:17 [AWK]
q?
02:09:25 [Lauriat]
Requirement 3.6 Regulatory Environment: The Guidelines provide broad support, including: Structure, methodology, and content that facilitates adoption into law, regulation, or policy, and; clear intent and transparency as to purpose and goals, to assist when there are questions or controversy.
02:09:31 [AWK]
(https://www.w3.org/WAI/GL/task-forces/silver/wiki/How_to_evaluate_Conformance_Proposals#Requirement_3.6_Regulatory_Environment)
02:09:37 [Ryladog]
Stakeholder interviews with at least 5, but not more than 10, Regulatory policy-making stakeholders including at least 5 different regulatory systems. Stakeholder interviews with at least 5, but not more than 10, Regulatory policy-using stakeholders including at least 5 different regulatory systems.
02:10:33 [Ryladog]
SL: For testing the CM, these these are the two
02:11:06 [Fazio]
Fazio has joined #ag
02:11:08 [Ryladog]
SL: We do not want 5 RS from just the US
02:11:46 [Ryladog]
SL: we expect to get a range of feedback on...we will want
02:12:02 [Chuck]
Katie: Example... this won't work in Japan law because...
02:12:10 [Ryladog]
....we want tohear about barriers to law buidling in all coutries
02:13:05 [Ryladog]
AWK: This is why we want to look at 3 or 4 CM so we can look at them and make those decisions after holding them up to the light. It maybe a combo approach
02:13:22 [Ryladog]
SL: Just because there are so many moving parts to a CM
02:13:52 [Ryladog]
...Stakeholder interviews as many as we can do in a reasonable amount of time
02:14:24 [Fazio_]
Fazio_ has joined #ag
02:14:35 [Ryladog]
AWK: It might even be a webinar for different regulatory systems - that would e ideal. Like atking advantage of evryone at M-Enabling
02:14:44 [Jemma_]
+1
02:14:55 [Lauriat]
q?
02:14:55 [Chuck]
q?
02:15:11 [Lauriat]
Requirement 3.7 Motivation: The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility.
02:15:11 [AWK]
(https://www.w3.org/WAI/GL/task-forces/silver/wiki/How_to_evaluate_Conformance_Proposals#Requirement_3.7_Motivation)
02:15:15 [Ryladog]
Stakeholder interviews across a range of organizations. Stakeholder interviews across a range of disability advocacy organizations.
02:15:58 [Ryladog]
SL: I will talk about what we talked about on Tuesday.
02:17:08 [Ryladog]
SL: Google has many diffent team to get different types of teams.
02:17:59 [Ryladog]
SL: We got alot of overall content itself, should were think this, does thi actually move the needle
02:18:46 [Ryladog]
Jemma: In Summary this is the one are to validate there testing.
02:19:07 [Ryladog]
SL: But users still come to us but they still have all of these issues
02:19:45 [Ryladog]
SL: Having a structure to navigate a path forward.
02:20:20 [Ryladog]
SL: One thing we go we could have user participationhave our mem take this back ber orgs
02:21:08 [Ryladog]
Jemma: For stakeholders it is more of a user reasearch
02:21:11 [AWK]
q+
02:21:38 [alastairc]
ack aw
02:22:20 [Ryladog]
AWK: How do we know your motivation. There sort of answers that. So I wonder about our tests?
02:22:43 [Ryladog]
...will that be tantamount to motivation
02:23:08 [Ryladog]
...I dont know if we want to say...
02:23:39 [Ryladog]
AWK: Does this scoring system work for you?
02:24:02 [Ryladog]
SL: And does the scroring mechanism make the teams go BEYOND?
02:24:05 [JohnRochford]
q+
02:24:20 [achraf]
q+ to say about the monitor
02:24:26 [Jemma_]
+q how about we rephase the title of "movitivation", requirement 3.7?
02:24:45 [Ryladog]
SL: Sub-bullets thes are the questions we want answer to
02:24:54 [Fazio]
Fazio has joined #ag
02:25:02 [Fazio]
q+
02:25:08 [Ryladog]
AWK: If we get 5 responses that they dont test this way at all
02:25:16 [alastairc]
q?
02:25:19 [Ryladog]
Alaistair: If somebody saysno
02:25:37 [Ryladog]
Jemma: What is the point about this req?
02:25:57 [alastairc]
Suggest questions such as: Would this scoring system work for you? And then: Would it encourage you to go beyond the baseline min?
02:25:59 [Ryladog]
SL: we do have some notes on this page, but we do elsewhere
02:26:03 [alastairc]
q?
02:26:12 [Ryladog]
...I will followup with giyhub bugs
02:26:20 [AWK]
ack john
02:26:23 [alastairc]
ack jo
02:26:33 [Ryladog]
SL: Ihave answers on to why its vague
02:27:04 [Jemma_]
s/what is the point/what is the purpose
02:27:19 [alastairc]
ack ac
02:27:19 [Zakim]
achraf, you wanted to say about the monitor
02:27:20 [AWK]
ack ach
02:27:28 [achraf]
http://qatar.checkers.eiii.eu/en/benchmarking/
02:27:29 [Ryladog]
JohnR: Silver did a protypeof the points system and eveluating user need. The outcome was that some disability group something one important to one group
02:28:25 [Ryladog]
ACHRAF: I want to share this Qatar resource with you...
02:28:57 [Ryladog]
...how we evaluate, and our partners
02:29:24 [Ryladog]
DF: I wonder if partners wouldbe afraid to participate
02:29:34 [Ryladog]
Jemma: That wouldnt work in Korea
02:29:37 [AWK]
q?
02:29:41 [AWK]
ACk Da
02:29:58 [alastairc]
ack fa
02:30:12 [Ryladog]
DF: The motivation peice confused me, are we tracking the motivation before use or after we publish?
02:30:30 [Jemma_]
s/That wouldnt work in Korea/
02:30:38 [Ryladog]
SL:We want to get a sense BEFORE wepublish. We will respond to the feedback we get
02:30:50 [Chuck]
katie: Are we looking for a certain amount of feedback? A least amount?
02:31:00 [Jemma_]
rssagent, make minutes
02:31:12 [Chuck]
SL: It's per interview. We want a broad range achievable in a given timeline.
02:31:19 [Ryladog]
Do we have a minimu for 3.7?
02:31:29 [Jemma_]
rrsagent, make minutes
02:31:29 [RRSAgent]
I have made the request to generate https://www.w3.org/2019/09/18-ag-minutes.html Jemma_
02:31:39 [Ryladog]
SL: We want many but not too many
02:32:00 [Ryladog]
AWK: this is a prominent issue with Regulators
02:32:47 [Lauriat]
Requirement: 3.8 Scope: The guidelines provide guidance for people and organizations that produce digital assets and technology of varying size and complexity. Our intent is to provide guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.
02:32:48 [AWK]
(https://www.w3.org/WAI/GL/task-forces/silver/wiki/How_to_evaluate_Conformance_Proposals#Requirement_3.8_Scope)
02:33:10 [Ryladog]
Req #1: Develop a mix of Silver guidelines and Methods that would include at least 2 methods each for: content creators, browsers, authoring tools, and assistive technologies. Show the methods to AGWG members (content creator experts), accessibility experts from 2-3 major browsers, 2-3 assistive technology vendors (including at least 1 non-English language assistive technology), and 2-3 accessibility experts from authoring tool vendors.
02:33:19 [Ryladog]
SL: there is only one test
02:34:17 [Ryladog]
SL: The reworded wouldbe stakeholders and validating
02:34:43 [alastairc]
Katie: I'd like to go above one
02:34:46 [Chuck]
Katie: I'd like to go above at least one.
02:35:04 [Chuck]
Katie: Not specific to this topic, we might want to look at the 5 most used languages in the world and make sure we are testing the AT in those areas.
02:35:21 [Chuck]
SL: I'd like to include a breadth of language requirements.
02:35:33 [Chuck]
Katie: I wouldn't limit it to that we should have some sort of metric for that.
02:36:15 [Chuck]
Katie: The relevance matters. It's the quality vs... we know everyone is using it, instead of security and privacy where you have different things around the world.
02:36:22 [Chuck]
Katie: In our case it's one standard around the world.
02:36:28 [Ryladog]
JohnR: this goes back Acheivability
02:36:45 [Ryladog]
I would like to ensure the qualityover the speed
02:37:47 [Jemma_]
+1 to JohnR
02:38:20 [Ryladog]
Jake: It alsodepends on if it is possible to extend. Because if we publish now in certain parts of the world they use technology in a different way, that wewill have a way to adress those things
02:39:22 [Ryladog]
SL: I think here is the communication aspect -when we dont have the feedback in time
02:40:08 [Chuck]
Katie: I think we will have lessons learned. No matter how we try to figure this out. Our experience from 2.0 and 2.1. If we do this well enough and publish in 5 languages we'll get more feedback.
02:40:30 [Chuck]
Katie: If only in english you'll get feedback from english speaking participants. But we are an international standards body.
02:40:38 [Ryladog]
Theshas not been approval for an extensibility
02:40:42 [Chuck]
Katie: It will only get somewhere if it's in the relevant language of the world.
02:40:49 [Fazio]
+1 to multiple languages
02:40:57 [alastairc]
q?
02:41:07 [Ryladog]
SL: Thisgoes bakc to the project plan add publishing draft in severallangauges
02:41:25 [Ryladog]
SL: Anything else for CM testing?
02:41:36 [Ryladog]
SL: Some is part of IA
02:41:51 [AWK]
q?
02:42:27 [Chuck]
Katie: Jeff, other than different testing from different countries and different technologies. We are talking about publishing in 5 different languages.
02:43:16 [Ryladog]
AWK: I agree but let finish the CM first
02:43:33 [Ryladog]
SL:Does this look CM testing good?
02:43:41 [jeff]
jeff has joined #ag
02:43:49 [jeff]
present+ jeff
02:44:12 [Ryladog]
DavidC: It might be better to say one non-latin script instead of nonEnglish
02:44:15 [Ryladog]
SL: Yes
02:44:31 [Ryladog]
AWK: We would like to hear what people think
02:44:55 [Ryladog]
+1 to this is a good plan
02:45:05 [Chuck]
+1
02:45:08 [AWK]
Any objection to using the plan as presented to evaluate the conformance model proposals?
02:45:16 [JakeAbma]
+1
02:45:21 [JohnRochford]
+1
02:45:31 [achraf]
+1
02:45:32 [Makoto]
+1
02:45:55 [Rachael]
+1
02:46:14 [Jemma_]
+1 with a condition that we make "Requirement 3.7 Motivation" be a bit clearer.
02:46:14 [Ryladog]
Nicaise: In organization we use the word "range"?
02:46:39 [KimD]
+1
02:46:42 [Ryladog]
SL: It is covered in our langauge I think
02:47:09 [Ryladog]
SL: We will addressJemma's concern
02:47:33 [Ryladog]
RESOLUTION: Accept conformance model noring Jemma's Condition
02:47:47 [Ryladog]
s/noring/noting
02:48:52 [Ryladog]
SL: We do have 2 more Silver Topics
02:49:08 [Ryladog]
TOPIC: Silver Issues and Exceptions
02:49:16 [Lauriat]
Conformance issues & exceptions: https://docs.google.com/document/d/1II0MP6l_Xn8GaRhxGSJPIbCto7xTLww3zpSjr6k57g4/edit
02:49:29 [Lauriat]
How do we set up methodologies for task-based assessment that can be used across a breadth of websites and products?
02:50:41 [Ryladog]
SL: Becasue a task is relevant to a particular site, so we would define that
02:51:26 [Ryladog]
SL: So we would want to include the Non-Interfence type SC but without it becoming very difficult to do so
02:52:39 [Ryladog]
SL: Because we are moving away from the term Webpages, and towards environment. Defining the tasks would scope of what would be conformance on the owner of the thing that is going through the assessment
02:53:13 [Chuck]
Katie: I think the concern we talked about the other day is leaving it up to the org to define the scope has to be controlled. They can scope out stuff that is relevant...
02:53:41 [Chuck]
Katie: I want to address some other way to address the interface that's in front of you. The user is interacting with the interface in front of them.
02:53:48 [Chuck]
Katie: Unless 'what is this' is a task.
02:54:25 [Jemma_]
+q can you share the definition/example of "non-interference" type if you don't mind, Shawn?
02:54:25 [Ryladog]
Alastair: I think it is how far around that task could go
02:54:32 [alastairc]
q?
02:54:44 [alastairc]
q+ Jemma_
02:54:51 [Ryladog]
DF: I am glad readily acheivable is there.
02:55:13 [Ryladog]
SL: my view is not up to us, but their regulators or others
02:56:04 [Ryladog]
DF: Maybe we can give them a mechanism
02:56:13 [alastairc]
ack je
02:56:34 [Ryladog]
Jemma: what is Non-interference?
02:57:10 [Chuck]
Katie: like the 4 sc that are called for in wcag 2.0, 2.1. Keyboard trap, flashing, things that keep a user from using the interface.
02:57:14 [Lauriat]
Non-interference: https://www.w3.org/TR/WCAG21/#cc5
02:57:49 [Ryladog]
SL: Please ask questions while we are going through this
02:58:08 [Ryladog]
Alastair: Are we trying to answer this?
02:58:25 [Ryladog]
SL: I want answer the first part
02:58:41 [Ryladog]
SL: This is not specific to the CM
02:59:21 [Ryladog]
...go acognitive walkthrough of thispersona (of say low-vsion)
02:59:54 [Ryladog]
SL: That is one example, we have sketched out a particlar issue
03:00:46 [Ryladog]
...Rating those expereince of each persona. Andfind out why you cant accomplish easily with a screen magifier
03:01:25 [Ryladog]
Jake: We shouldbe thinking about the more interactive parts, when you use tab sequencing
03:01:51 [Ryladog]
Jake: It may be possible to go beyond on-
03:01:57 [jeff_]
jeff_ has joined #ag
03:02:10 [Ryladog]
...beyond non-interference
03:02:58 [Ryladog]
SL: Yes. Conformance and the results of actual testing. Like collisions we would like that to be relflected
03:03:58 [Ryladog]
Alastair: Easilt Keyboard cover like 8 GL. But using maybe non-AT and more subjective barriers.
03:04:34 [Ryladog]
....we had a complaint from a dragon users, that used the tools different
03:04:41 [Chuck]
Katie: User interaction patterns.
03:05:10 [Ryladog]
SL: I am getting to a point, in Docs there are at least5ways to bold text
03:06:53 [Ryladog]
SL: This is an illustration of that all pahts should be accessible. In voice it depends on the the persons voice
03:07:45 [Ryladog]
DF: I talk about at least all the human senses, by touch hearing speech you are making sure people can perform
03:08:28 [JohnRochford]
SL: I would appreciate points such as, "when you are thinking about this, please keep that in mind".
03:09:01 [JohnRochford]
AC: We may need alternative ways of achieving a task.
03:09:27 [Lauriat]
How do we migrate people from WCAG 2.x to Silver from a conformance viewpoint? (for example, should WCAG 2.0 or WCAG 2.1 be grandfathered to Silver?
03:09:59 [JohnRochford]
SL: Should WCAG 2.x migrate to some level of Silver?
03:10:22 [Ryladog]
q+
03:10:35 [JohnRochford]
SL: How do we migrate people who are using WCAG 2.x?
03:10:44 [Fazio]
Fazio has joined #ag
03:10:50 [alastairc]
q+
03:11:11 [jeanne]
q+ to suggest "grandfather" rather than direct 1-1 congruence
03:11:42 [JohnRochford]
David: You could match Silver conformance levels to WCAG 2.x.
03:11:57 [alastairc]
q?
03:12:46 [JohnRochford]
Chuck: We bring over 2.x in a way that people following it don't break and yet meet Silver conformance levels.
03:12:49 [Lauriat]
ack alastairc
03:13:27 [JohnRochford]
AC: I don't want Silver to be restricted by matching to WCAG 2.x.
03:13:41 [jeanne]
q-
03:14:01 [JohnRochford]
Katie: We are trying to do more with Silver. It's a richer model than WCAG 2.x.
03:14:12 [alastairc]
q?
03:14:16 [alastairc]
ack ry
03:14:16 [Lauriat]
ack Ryladog
03:14:31 [JohnRochford]
Katie: The whole point with Silver is to stretch conformance.
03:14:48 [Chuck]
q+
03:16:08 [Ryladog]
q+
03:16:12 [alastairc]
ack ch
03:16:13 [Lauriat]
ack Chuck
03:16:21 [JohnRochford]
David: There may be a perception by companies that they may not have to follow Silver unless it becomes law as WCAG 2.x is.
03:17:20 [alastairc]
ack ry
03:17:20 [JohnRochford]
Chuck: There will be more friendlier views of following Silver if there is overlap between 2.x and Silver.
03:22:03 [JohnRochford]
SL: My motivation is that guidelines should reflect the experiences of PwD.
03:22:46 [JohnRochford]
SL: That also depends upon the platform and/or tools PwD use.
03:23:37 [JohnRochford]
AC: You are hamstringing yourself if you are trying to do 1 to 1 mapping.
03:24:49 [JohnRochford]
Katie: How can we future proof design, do vigorous testing, address gaps from lessons learned from 2.x?
03:25:14 [JohnRochford]
SL: We are going to have to discover future gaps.
03:25:47 [JohnRochford]
AC: We need to track where 2.x went into Silver.
03:26:20 [JohnRochford]
AC: We should provide a mapping/migration document.
03:27:20 [JohnRochford]
Janina: If we map 1 to 1, that will be a problem because it will box us in (restrict us).
03:28:01 [JohnRochford]
Welcome back, Mike.
03:28:25 [JohnRochford]
Chuck: Our current progress is not yet boxing us in.
03:28:32 [mbgower]
rrsagent, make minutes
03:28:32 [RRSAgent]
I have made the request to generate https://www.w3.org/2019/09/18-ag-minutes.html mbgower
03:30:18 [JohnRochford]
Chuck: Silver may have a smoother path to adoption if it has a subset minimum that is 2.x friendly.
03:30:52 [JohnRochford]
Chuck: Companies may adopt Silver more quickly if they don't think their WCAG work is wasted.
03:31:15 [JohnRochford]
SL: A mapping/migration doc should answer that quite well.
03:32:07 [JohnRochford]
SL: I'm not concerned about auditing. I am concerned about implementation.
03:32:57 [JohnRochford]
We have 2 docs: One is a snapshot from about a year ago. One is our working doc.
03:33:32 [mbgower]
q+ to say has there been any discussion of a scenario where 2.x persists as a baseline and 3x is the equivalent of a LEEDS certification?
03:34:00 [JohnRochford]
Jake: We must do mapping to ensure adoption. Do we have a choice?
03:34:33 [JohnRochford]
SL: I don't know yet if there will be a choice.
03:34:46 [Ryladog]
q+
03:35:03 [JohnRochford]
Janina: We will find out as we go through the process.
03:35:35 [LisaSeemanKest]
LisaSeemanKest has joined #ag
03:35:41 [JohnRochford]
Katie: Tools use the failures of the SC, but they will add more.
03:36:47 [alastairc]
ack mbg
03:36:47 [Zakim]
mbgower, you wanted to say has there been any discussion of a scenario where 2.x persists as a baseline and 3x is the equivalent of a LEEDS certification?
03:37:00 [Ryladog]
q-
03:37:19 [JohnRochford]
Mike: Will 2.x persist as a baseline?
03:37:30 [nicaise]
q+
03:37:48 [JohnRochford]
Mike: Would be the migration plan be complimentary and not a replacement?
03:38:19 [JohnRochford]
SL: I don't expect that because it would be too difficulty to have to follow both.
03:38:46 [JohnRochford]
s/difficulty/difficult
03:38:50 [alastairc]
q?
03:38:54 [alastairc]
ack ni
03:41:06 [mbgower]
k, thanks. so in 1hr 20
03:49:15 [MichaelC]
MichaelC has joined #ag
03:52:21 [mbgower]
mbgower has joined #ag
03:56:36 [mbgower_]
mbgower_ has joined #ag
04:03:43 [LisaSeemanKest]
LisaSeemanKest has joined #ag
04:04:17 [stevelee]
stevelee has joined #ag
04:06:19 [LisaSeemanKest_]
LisaSeemanKest_ has joined #ag
04:06:48 [mbgower]
mbgower has joined #ag
04:21:28 [jeff_]
jeff_ has joined #ag
04:33:38 [alastairc]
Re-starting around 13:45 (12 min from now)
04:38:15 [Ryladog]
Ryladog has joined #ag
04:38:53 [jeff]
jeff has joined #ag
04:45:43 [KimD]
KimD has left #ag
04:46:17 [LisaSeemanKest_]
LisaSeemanKest_ has joined #ag
04:48:43 [atai]
atai has joined #ag
04:49:52 [KimD]
KimD has joined #ag
04:49:56 [KimD]
Present+
04:50:29 [JakeAbma]
JakeAbma has joined #ag
04:50:35 [JakeAbma]
present+ JakeAbma
04:51:04 [LisaSeemanKest_]
present+
04:52:01 [LisaSeemanKest_]
anyone there?
04:52:33 [LisaSeemanKest_]
ah it is not just me
04:52:56 [alastairc]
Muted, unless you want to hear the post-lunch conversation?
04:53:20 [Nicaise]
Nicaise has joined #ag
04:54:23 [Ryladog]
Present+ Katie_Haritos-Shea
04:55:19 [AWK]
zakim, agenda?
04:55:19 [Zakim]
I see 4 items remaining on the agenda:
04:55:20 [Zakim]
1. AGWG Group dynamics and expectation setting [from AWK]
04:55:20 [Zakim]
2. Silver topics [from AWK]
04:55:20 [Zakim]
3. Finalise last WCAG 2.1 technique [from AWK]
04:55:20 [Zakim]
4. WCAG 2.2 Work [from AWK]
04:55:21 [Fazio]
Fazio has joined #ag
04:55:26 [AWK]
Zakim, close item 1
04:55:26 [Zakim]
agendum 1, AGWG Group dynamics and expectation setting, closed
04:55:28 [Zakim]
I see 3 items remaining on the agenda; the next one is
04:55:28 [Zakim]
2. Silver topics [from AWK]
04:55:31 [AWK]
zakim, close item 2
04:55:31 [Zakim]
agendum 2, Silver topics, closed
04:55:32 [Zakim]
I see 2 items remaining on the agenda; the next one is
04:55:32 [Zakim]
3. Finalise last WCAG 2.1 technique [from AWK]
04:55:42 [AWK]
Zakim, take up item 3
04:55:42 [Zakim]
agendum 3. "Finalise last WCAG 2.1 technique" taken up [from AWK]
04:55:46 [LisaSeemanKest_]
going to try apa
04:58:17 [ReinaldoFerraz]
ReinaldoFerraz has joined #ag
04:58:42 [Makoto]
Makoto has joined #ag
04:58:47 [mhakkinen]
mhakkinen has joined #ag
04:58:51 [alastairc]
https://raw.githack.com/w3c/wcag/Failure_for_135_AWK/techniques/failures/F_1_3_5.html
04:59:34 [MichaelC]
MichaelC has joined #ag
04:59:45 [mbgower]
mbgower has joined #ag
05:00:00 [mbgower]
present+
05:00:44 [Jemma_]
Scribe: Jemma
05:00:49 [alastairc]
scribe:Jemma_
05:02:43 [Jemma_]
Topic: Finalise last WCAG 2.1 technique
05:03:03 [JohnRochford]
JohnRochford has joined #ag
05:03:19 [JohnRochford]
present+ JohnRochford
05:03:31 [Fazio]
Fazio has joined #ag
05:04:10 [Jemma_]
awk: saftest failure will be having incorrect autocomplete.
05:04:46 [Jemma_]
awk: among three failures
05:05:37 [Jemma_]
jn:autocomplete failure needs context, ie. it depends on which name is
05:05:47 [Ryladog]
https://raw.githack.com/w3c/wcag/Failure_for_135_AWK/techniques/failures/F_1_3_5.html
05:06:21 [JakeAbma]
q+ ... in markup languages ... technologies
05:06:40 [JakeAbma]
q+ in markup languages Vs. technologies
05:06:47 [JakeAbma]
q+
05:07:08 [mbgower]
I think wrong uses of autocomplete is the fastest way to get a failure
05:07:24 [alastairc]
ack ja
05:07:37 [Jemma_]
awk: what do other people think about #2 procedure, "heck that the form field does not has a valid and well-formed autocomplete attribute and value pair that matches the purpose of the input."?
05:07:52 [Jemma_]
s/heck/check
05:08:57 [Jemma_]
jake: this does not need to be scoped to "mark up" languages.
05:09:04 [alastairc]
agenda?
05:09:14 [alastairc]
zakim, take up next item
05:09:14 [Zakim]
agendum 4. "WCAG 2.2 Work" taken up [from AWK]
05:09:37 [Jemma_]
rrsagent, make minutes
05:09:37 [RRSAgent]
I have made the request to generate https://www.w3.org/2019/09/18-ag-minutes.html Jemma_
05:10:31 [alastairc]
https://docs.google.com/spreadsheets/d/11IKqjRFvkRd2dAfUiyc5whhB3yIYXvSiirWct7KQIB0/edit#gid=0
05:11:27 [Rachael]
q+
05:11:37 [jeff]
jeff has joined #ag
05:11:50 [Rachael]
q-
05:12:23 [alastairc]
https://www.w3.org/WAI/GL/wiki/WCAG_2.2_Success_criterion_acceptance_requirements
05:12:25 [Jemma_]
things to do for this WCAG 2.2 topic is that 1) kdoes it meet the SC requirement, 2)if not how we are going to do it, 3) who can do the work?
05:13:00 [Jemma_]
alastairc: <showing the list of SC requirements on the screen>
05:13:41 [alastairc]
Disproportionately affects a user with a disability.
05:13:41 [alastairc]
Is automatically or manually testable.
05:13:41 [alastairc]
Different testers should get the same results.
05:13:41 [alastairc]
Describe the condition required to meet the criteria.
05:13:41 [alastairc]
Uses the WCAG 2.x A/AA/AAA level structure.
05:13:41 [alastairc]
Applies to all content across all websites.
05:13:41 [alastairc]
Applies across technologies to the greatest extent possible.
05:13:43 [alastairc]
Doesn’t overlap with existing Success Criterion.
05:13:45 [Jemma_]
s/kdoes/Does
05:14:41 [Jemma_]
alastairc: since we have a limited time, we will just go over the key points for each SC items.
05:15:08 [Jemma_]
1. Accessinble Authentification
05:16:20 [Jemma_]
s/Accessinble/Accessible
05:16:29 [mbgower]
However, it's still a cognitive function
05:17:33 [alastairc]
Full doc: https://docs.google.com/document/d/1J3NFw6NPyj7QGddBtRmagrtS-x4t9BWan8PYEdSpMZM/edit#heading=h.9a579gtg9i39
05:17:36 [mbgower]
q+ to say is this implying "any one of the following"
05:18:51 [alastairc]
ack mb
05:18:52 [Ryladog]
q+
05:18:52 [Zakim]
mbgower, you wanted to say is this implying "any one of the following"
05:19:41 [Jemma_]
group discusison about "not exclusively relying on" one of following
05:20:38 [Fazio]
+1 to expand wording from "does not rely on any"
05:20:52 [Jemma_]
katie and MC: this implies that it can supply the alternative methods.
05:21:37 [mbgower]
q+ to say I think you do not want to say 'at least 2' or anything. 'does not rely on any one of the following'
05:21:41 [alastairc]
q?
05:21:51 [Jemma_]
jake: remove "including..."phrase .. can be the solution?
05:22:24 [Jemma_]
katie: we add examples of cognitive function to other SC..
05:23:00 [mbgower]
+1 to sublist in the understanding doc or maybe Is it possible to have a definition for cognitive function to cover this?
05:23:32 [Jemma_]
jake: the list in the SC seems to be limited...
05:23:33 [mbgower]
q?
05:23:44 [alastairc]
ack ry
05:23:53 [Ryladog]
q+
05:24:27 [Jemma_]
awk: here in the list means that it includes the listitems more than ones stated.
05:24:49 [Rachael]
+1 to not making this at least two
05:25:12 [KimD]
+1 should not say "at least 2" because - future possible authentication methods
05:26:07 [Jemma_]
mike: cognitive function can be defined in normative doc and link to the doc will be helpful.
05:26:09 [Fazio]
q+
05:26:14 [alastairc]
ack mb
05:26:14 [Zakim]
mbgower, you wanted to say I think you do not want to say 'at least 2' or anything. 'does not rely on any one of the following'
05:26:45 [AWK]
ack r
05:26:47 [AWK]
ack da
05:26:49 [AWK]
ack fa
05:26:59 [Jemma_]
mike: "exceot for your own namem ...)" sounds like cumbersome to understand.
05:27:11 [AWK]
q+ to ask if there is any authentication that wouldn't be covered by this list
05:27:18 [Jemma_]
s/exceot/except
05:27:41 [alastairc]
ack aw
05:27:42 [Zakim]
AWK, you wanted to ask if there is any authentication that wouldn't be covered by this list
05:28:19 [Jemma_]
awk: can this be inclusive most of time?
05:28:29 [Rachael]
q+
05:28:34 [mbgower]
s/exceot for your own namem ...)" sounds like cumbersome to understand./add a normative definition of cognitive function instead of being in the SC text
05:28:39 [Jemma_]
mc: there is a chance new things come up anytime.
05:29:31 [mbgower]
q+ to say I would like to suggest this be called Accessible Re-Authentication
05:29:33 [Jemma_]
as authentification methods
05:29:57 [mbgower]
use of webauth can solve this without using any of these necessarily
05:30:12 [Jemma_]
q?
05:30:50 [Jemma_]
katie: we may need examples of two factor authentification...
05:31:15 [AWK]
ack Rach
05:31:22 [Jemma_]
davidF: may we have a chance to burden small bussinesses?
05:32:19 [Rachael]
When authentication is used, at least one method is available that allows a user to authenticate without relying on:
05:32:39 [mbgower]
that's why I was suggesting "any one of the following"
05:33:53 [alastairc]
https://1drv.ms/p/s!AqcLQeCk6CjwiKIUezUgJTtB7sgmBQ?e=4Ceh7W
05:34:07 [alastairc]
^ link to the powerpoint file
05:34:08 [Jemma_]
rach: I don't think we are talking here what we are trying to say in the statement
05:34:09 [Chuck]
q+
05:34:40 [JakeAbma]
q+ a specific biometric
05:34:49 [JakeAbma]
q+
05:35:27 [stevelee]
present+
05:35:28 [Chuck]
ack Chuck
05:35:48 [alastairc]
ack mb
05:35:48 [Zakim]
mbgower, you wanted to say I would like to suggest this be called Accessible Re-Authentication
05:37:50 [Chuck]
q+
05:38:38 [Fazio]
I agree with MG Login or re-authentication?
05:38:58 [Jemma_]
mg: I think my intention for SC aims to be more extensive rather than limitive. I am wondering whether we are considering "reauthentificaiton" using google or fb login..
05:39:27 [Jemma_]
johnrochford: I don't want to limit this SC only to re-authentification.
05:41:12 [Jemma_]
... because there is authentification system you dont need to initiate or create the login(authentification)
05:41:36 [Jemma_]
alastairc:talking about different authentificaiton system example...
05:42:24 [Jemma_]
johnRochford: for one example, you are just authentificated, it is because you are human,.
05:42:26 [Chuck]
ack Chuck
05:42:44 [Jemma_]
s/is because/is just because
05:43:16 [alastairc]
ack ja
05:43:30 [Jemma_]
Johnrochford: another example is birthdate authentificaiton.
05:43:54 [Rachael]
q+
05:44:25 [Jemma_]
??: the point of this SC is that if you are relying on one of these items, that means it fails.
05:44:35 [stevelee]
I agree the language needs to avoid complicated mental parsing loops :)
05:45:15 [mbgower]
removed "exclusively" from option A
05:46:08 [mbgower]
I think option A is what we want, without the word "exclusively"
05:46:20 [alastairc]
q?
05:47:45 [Jemma_]
jake: suggestion to change "a specific biometric input" to "a biometric input"
05:48:03 [Rachael]
When authentication is used, users can authenticate using a method that does not rely on:
05:48:34 [mbgower]
+1 I like that R
05:48:48 [stevelee]
+1 from me
05:49:04 [KimD]
-1
05:49:13 [Jemma_]
rach: focus on Users action, rather than specific software function.
05:49:26 [mbgower]
But it should be ...rely on any one of the following', right?
05:49:37 [alastairc]
ack ra
05:50:32 [mbgower]
as written a and b are quite different. A allows 2 of those to occur. B disallows any of them
05:52:03 [alastairc]
a) When authentication is used, a method is available that does not exclusively rely on any one of the following:
05:52:03 [alastairc]
b) When authentication is used, users can authenticate using a method that does not rely on:
05:52:39 [Jemma_]
awk: we will figure out the language.
05:53:18 [mbgower]
I really want the word "exclusively" removed from A :)
05:53:44 [KimD]
Is this what it's trying to say "When asking users to authenticate from one of the categories below, a second method from a different category must also be used. "
05:54:00 [Jemma_]
awk: technique will be completed once the SC language are completed.
05:54:12 [KimD]
q=
05:54:17 [Jemma_]
johnRochford and John Folio are working on this.
05:54:26 [KimD]
q+
05:54:47 [AWK]
ack kim
05:55:49 [AWK]
Web Authentication Spec: https://www.w3.org/TR/webauthn/
05:56:40 [Jemma_]
https://www.irccloud.com/pastebin/ELuIEmnB/
05:57:09 [Jemma_]
https://www.w3.org/TR/webauthn/#use-cases
05:57:25 [Jemma_]
use case for webauth can be found above,.
05:58:20 [Jemma_]
kim: I think there is the loophole in the concept.
05:58:36 [Lauriat]
Joining the wordsmithing party: "If a method of authentication relies on any of the following, at least one other method must also be available which does not rely on the same modality/modalities."
05:59:20 [Jemma_]
awk: one example is voice authentificaiton but if you have to say your passsword/put it in, there is a cognitive issue to consider as Kim said.
05:59:43 [Rachael]
+1 to lauriat's suggestion.
06:00:29 [atai]
atai has joined #ag
06:00:56 [Jemma_]
??: here i think authentification and captcha are mixed in the dicussion. chaptcha is the validation method, not authentification methods.
06:01:04 [mbgower]
I think it's useful and it is a strong candidate
06:01:07 [Fazio]
+1
06:01:18 [Jemma_]
awk: we will continue to consider this for WCAG 2.2
06:01:28 [KimD]
I think it needs work but is a good idea
06:01:48 [Jemma_]
awk: does anyone think that it is not going toward positive direction?
06:01:59 [Jemma_]
shawnlauriat: it is going with the positive direction.
06:02:06 [alastairc]
TOPIC: Touch target spacing
06:02:10 [mbgower]
s/??: here I think/mbgower: I think
06:02:14 [JakeAbma]
q+
06:02:39 [alastairc]
If the target for pointer inputs is less than 44 by 44 CSS pixels then there is a minimum of 8 CSS pixels between adjacent targets except when:
06:02:39 [alastairc]
- Inline The target is in a sentence or block of text;
06:02:39 [alastairc]
- Essential A particular presentation of the target is essential to the information being conveyed.
06:03:31 [Jemma_]
rrsagent, make minutes
06:03:31 [RRSAgent]
I have made the request to generate https://www.w3.org/2019/09/18-ag-minutes.html Jemma_
06:03:31 [alastairc]
ack ja
06:04:56 [Jemma_]
jakeabma: there was a discussion about lack of testing method for this SC.
06:05:27 [Jemma_]
s/this SC/SC Spacing between touch targets
06:06:10 [Jemma_]
alastairc: ?? was supposed to make updates.
06:06:33 [alastairc]
s/?? was supposed to/Kathy had a chance to
06:07:48 [Jemma_]
jakeabma: if people are using flexbox, this is going to be the problem.
06:08:13 [Jemma_]
awk: is there no way to set the minimum padding among flex box?
06:09:30 [Jemma_]
jakeamba: then it means that you have to add minimum px for each flexbox scenarios.
06:10:21 [Jemma_]
shawnlariat: you are talking about implementation possibilty.
06:10:39 [alastairc]
q?
06:11:22 [Jemma_]
... there is the way that we can test the padding depending on various layout sizes.
06:11:57 [JohnRochford]
q+
06:12:21 [alastairc]
ack jo
06:12:30 [Jemma_]
... there is the way most of failure cases can be automated.
06:12:38 [mbgower]
q+ to say that this SC seems redundant since UX practices and principles exceed this guidance https://uxmovement.com/mobile/optimal-size-and-spacing-for-mobile-buttons/
06:13:01 [JohnRochford]
q-
06:14:47 [mbgower]
How about making this Non-Text Targets?
06:15:40 [Jemma_]
please refer the "few exceptions" link in the SC google doc.
06:17:24 [Jemma_]
mbgower: two points. 1) this limits to non text target 2) Can topic be the candidate for Silver or UX experts in Apple or MS?
06:17:58 [Jemma_]
awk: these are from Apple design spec and compared with MS...
06:19:09 [Jemma_]
mbgower: I would rather to talk about this based on the research and by UX experts, not accessibiilty issues.
06:20:08 [Jemma_]
alastairc: for the sake of discussion, devel's advocate, ....
06:22:22 [KimD]
+1 this pattern with "small" buttons is all over
06:23:46 [alastairc]
Kim - is that a bad thing? I.e. are you +1ing this as a potential SC?
06:24:02 [AWK]
q+ to say that we should ask apple/google/microsoft about size and spacing and implementation
06:24:11 [mbgower]
q-
06:24:28 [AWK]
ack mbg
06:24:38 [AWK]
ack AWK
06:24:38 [Zakim]
AWK, you wanted to say that we should ask apple/google/microsoft about size and spacing and implementation
06:25:10 [alastairc]
q+ to ask about usability (tested?) interfaces, would making buttons bigger impact negatively?
06:25:20 [stevelee]
good point!
06:25:45 [Jemma_]
+1 to questions from AWK and alastairc
06:26:54 [mbgower]
icons in an application toolbar are somewhat of an 'exception' in that they are 'shortcuts' to functions offered in the menu.
06:27:15 [alastairc]
ack al
06:27:15 [Zakim]
alastairc, you wanted to ask about usability (tested?) interfaces, would making buttons bigger impact negatively?
06:28:05 [mbgower]
q+ to say that there should be language for 'relying' on the small targets
06:28:13 [KimD]
+1 you see less content. What happens when you zoom?
06:29:21 [alastairc]
q?
06:29:26 [AWK]
ack mbg
06:29:26 [Zakim]
mbgower, you wanted to say that there should be language for 'relying' on the small targets
06:30:00 [Jemma_]
sl: I am trying to understand/explain that what are the implications for this SC by pointing out different examples in google doc and android apps.
06:30:53 [alastairc]
q
06:30:55 [alastairc]
q?
06:31:31 [LisaSeemanKest_]
LisaSeemanKest_ has joined #ag
06:33:25 [LisaSeemanKest]
LisaSeemanKest has joined #ag
06:36:11 [Jemma_]
In summary, this SC require the discussion on 1) testability(UI) 2) asking questions to relevant parties such as apples/google/microsoft about size and spacing.
06:37:11 [AWK]
Notes: https://docs.google.com/document/d/1HqI19P0LUzdpbm1IM2PPhloXjXWHFC9Fo3QjoVQ4Irc/edit#
06:42:14 [LisaSeemanKest_]
LisaSeemanKest_ has joined #ag
06:42:14 [LisaSeemanKest_]
waiting for michale to join the webe
06:42:34 [LisaSeemanKest_]
sorry wrong channel
06:49:16 [AWK]
s/waiting for michale to join the webe/
06:49:27 [AWK]
s/sorry wrong channel/
07:00:48 [alastairc]
TOPIC: Focus visible
07:02:17 [JakeAbma]
JakeAbma has joined #ag
07:02:22 [JakeAbma]
present+ JakeAbma
07:02:26 [alastairc]
Focus visible doc: https://docs.google.com/document/d/1g9_WBgfhViWAaRFIWWt10CP5rBsEVIWm3vT1vWqrHvI/edit
07:02:43 [JakeAbma]
scribe: JakeAbma
07:03:19 [nicaise]
nicaise has joined #ag
07:04:13 [JakeAbma]
AC: intent is to be sure a visible change is clearly present when a UIC is focussed
07:04:17 [AWK]
(Alastair reads SC proposal)
07:05:56 [JakeAbma]
SL: is there research for this SC available?
07:06:29 [JakeAbma]
AC: only some ad hoc research
07:06:51 [alastairc]
https://alastairc.uk/tests/wcag22-examples/focus-more-visible-2.html
07:09:40 [JakeAbma]
AC: some work better than others
07:13:02 [JakeAbma]
Jake: doesn't this mean we will have big problems with 3 way contrast colors? As discussed with hover previously
07:14:22 [JakeAbma]
AC: that you have more options, like adding thicker border
07:16:39 [JakeAbma]
AC: example 3 shows that it is impossible for this SC
07:17:28 [JakeAbma]
AC: inverted focus works fine
07:17:35 [JakeAbma]
AC: example 5
07:21:03 [JakeAbma]
SL: does the caret have a use for 11b
07:21:17 [JakeAbma]
AC: didn't think about it yet
07:21:26 [JakeAbma]
AWK: noted
07:22:51 [JakeAbma]
AWK: it would be good to check against design systems from companies to check if it works
07:24:10 [alastairc]
q?
07:24:24 [Fazio]
Fazio has joined #ag
07:24:55 [Fazio]
Contrast Sensitivity chart resource from medical association: https://www.aoa.org/Documents/optometric-staff/Articles/Contrast-Sensitivity.pdf
07:26:32 [JakeAbma]
AWK: does it make sense for all of us, is it implementable?
07:27:22 [JakeAbma]
SL: need to make it easy to what the focus area is
07:32:45 [JakeAbma]
Jake: first time we will not allow default UA coloring?
07:33:11 [JakeAbma]
AWK: yes, if the default is not according to these rules, authors need to adjust
07:37:36 [KimD]
Do we need more clarity about what has to be measured in the third bullet?
07:38:24 [KimD]
will do
07:38:29 [JakeAbma]
AC: if you have suggestions, please provide
07:38:35 [AWK]
TOPIC: Essential Controls
07:39:06 [alastairc]
https://docs.google.com/document/d/1DPtCqWHjrhj3QZ4afsqzmWDd-zMSf39RsMqSpR2QGCg/edit#heading=h.oq5d847iraod
07:42:52 [Rachael]
q+
07:43:08 [alastairc]
ack ra
07:43:36 [shadi]
shadi has joined #ag
07:43:59 [song_jaeil]
song_jaeil has joined #ag
07:44:38 [JakeAbma]
AWK: Rachel said personalisation will be published on time for nr. 2
07:44:43 [alastairc]
Data simplification tag would be for part number
07:46:20 [Rachael]
https://www.w3.org/TR/personalization-semantics-content-1.0/#simplification-explanation
07:46:23 [KimD]
What about when a user is zoomed - a control that *was* visible may not be visible after zoomed. Would that be a violation?
07:47:44 [JakeAbma]
AWK: long forms with button at the end will make it difficult
07:52:04 [KimD]
It seems like there are so many ways to fail 1., that you'd always have to do 2.
07:57:39 [JakeAbma]
rachel: more clear if we take main navigation out?
07:57:51 [JakeAbma]
AWK: not sure if we need to do it right now
08:01:02 [JakeAbma]
Jake: can't we make it an extension of / like: input purpose, so we can rid of nr. 1?
08:03:03 [alastairc]
We've reduced a bit, but still going.
08:03:16 [alastairc]
s/We've reduced a bit, but still going/
08:03:18 [KimD]
Good point, Jake. Testing
08:07:59 [atai]
atai has joined #ag
08:14:04 [KimD]
Agree that WCAG is a brand and has meaning on its own
08:14:40 [alastairc]
Previous survey: https://www.w3.org/2002/09/wbs/35422/NamingSilver/results
08:14:45 [alastairc]
includes the names
08:15:25 [alastairc]
Several comments supporting keeping the WCAG acronym in some form, although realising that it shouldn't be 'content'
08:16:12 [alastairc]
"Web Creation Accessibility Guidelines"?
08:17:28 [alastairc]
trackbot end meeting
08:17:28 [trackbot]
Zakim, list attendees
08:17:28 [Zakim]
As of this point the attendees have been AWK, Chuck, JohnRochford, MichaelC, Fazio, Makoto, Katie_Haritos-Shea, JakeAbma, alastairc, Lauriat, achraf, jamesn, DavidClarke_,
08:17:31 [Zakim]
... ReinaldoFerraz, Laura, DavidClarke, mbgower, KimD, JaEunJemmaKu, Rachael, jeanne, jeff, LisaSeemanKest_, stevelee
08:17:36 [trackbot]
RRSAgent, please draft minutes
08:17:36 [RRSAgent]
I have made the request to generate https://www.w3.org/2019/09/18-ag-minutes.html trackbot