IRC log of ag on 2017-08-08
Timestamps are in UTC.
- 14:51:07 [RRSAgent]
- RRSAgent has joined #ag
- 14:51:07 [RRSAgent]
- logging to http://www.w3.org/2017/08/08-ag-irc
- 14:51:09 [trackbot]
- RRSAgent, make logs public
- 14:51:12 [trackbot]
- Zakim, this will be WAI_WCAG
- 14:51:12 [Zakim]
- ok, trackbot
- 14:51:12 [trackbot]
- Meeting: Accessibility Guidelines Working Group Teleconference
- 14:51:12 [trackbot]
- Date: 08 August 2017
- 14:51:25 [Joshue108]
- Chair: AWK
- 14:51:35 [Joshue108]
- zakim, agenda?
- 14:51:35 [Zakim]
- I see 2 items remaining on the agenda:
- 14:51:36 [Zakim]
- 2. Concurrent Input Methods:https://www.w3.org/2002/09/wbs/35422/MATFSC_june/results (item 3 only) [from AWK]
- 14:51:36 [Zakim]
- 3. Personalization: https://www.w3.org/2002/09/wbs/35422/LatestPersonalization/results [from AWK]
- 14:52:07 [AWK]
- AWK has joined #ag
- 14:52:26 [KimD]
- KimD has joined #ag
- 14:52:34 [KimD]
- Present+
- 14:55:02 [AWK]
- Agend?
- 14:55:05 [AWK]
- Agenda?
- 14:55:18 [AWK]
- Zakim, clear agenda
- 14:55:18 [Zakim]
- agenda cleared
- 14:56:08 [AWK]
- agenda+ meeting time (https://www.w3.org/2002/09/wbs/35422/mastiempo/results)
- 14:56:11 [jeanne]
- jeanne has left #ag
- 14:56:52 [AWK]
- agenda+ Concurrent Input Mechanisms (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC8)
- 14:57:30 [AWK]
- agenda+ Popup Visibility (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc11)
- 14:57:40 [Joshue108]
- present+ Joshue108
- 14:57:56 [AWK]
- agenda+ timeouts (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC1)
- 14:58:19 [AWK]
- agenda+ personalization (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC13)
- 14:59:08 [Mike_Elledge]
- Mike_Elledge has joined #ag
- 14:59:19 [Mike_Elledge]
- Present+ Mike Elledge
- 15:00:20 [Glenda]
- Glenda has joined #ag
- 15:01:10 [Makoto]
- Makoto has joined #ag
- 15:01:15 [JF]
- JF has joined #ag
- 15:01:34 [Detlev]
- Detlev has joined #ag
- 15:01:43 [JF]
- Present+ JF
- 15:01:48 [Makoto]
- present+ Makoto
- 15:01:55 [kirkwood]
- kirkwood has joined #ag
- 15:02:07 [Detlev]
- present+ Detlev
- 15:02:34 [kirkwood]
- present+
- 15:02:57 [Alex]
- Alex has joined #ag
- 15:02:59 [Kathy]
- Kathy has joined #ag
- 15:03:02 [MelanieP]
- MelanieP has joined #ag
- 15:03:14 [jasonjgw]
- present+
- 15:04:06 [KimD]
- *yes, I had the same issue, Andew
- 15:04:06 [Detlev]
- The webex link above points to the Thursday meeting...
- 15:04:10 [MichaelC]
- MichaelC has changed the topic to: New WebEx: https://mit.webex.com/mit/j.php?MTID=m9f8734e8f254b985e44d0b1327fb805c meeting number 643 648 457
- 15:04:10 [steverep]
- steverep has joined #ag
- 15:04:11 [Kathy]
- present+ Kathy
- 15:04:42 [JakeAbma]
- present+ JakeAbma
- 15:04:57 [steverep]
- present+steverep
- 15:05:48 [MelanieP]
- present+ Melanie_Philipp
- 15:05:52 [bruce_bailey]
- bruce_bailey has joined #ag
- 15:06:25 [Glenda]
- present+ Glenda
- 15:06:28 [Detlev]
- Have trouble starting WebEx on the Mac... any ideas?
- 15:06:36 [Mike_Elledge]
- Looking for scribes
- 15:06:45 [bruce_bailey]
- present+ bruce-bailey
- 15:06:57 [Mike_Elledge]
- Alex will scribe next Thursday
- 15:07:09 [Detlev]
- damn
- 15:07:21 [AWK]
- Scribe: Mike_Elledge
- 15:07:43 [AWK]
- Zakim, take up item 1
- 15:07:43 [Zakim]
- agendum 1. "meeting time (https://www.w3.org/2002/09/wbs/35422/mastiempo/results)" taken up [from AWK]
- 15:08:57 [Mike_Elledge]
- Awk: Idea that we can use extra time. Everyone responding to survey said okay to add half hour. Tuesday 11-1. Thursday 7 can, 3 conflict.
- 15:09:04 [Mike_Elledge]
- awk: other thoughts?
- 15:09:38 [Alex]
- q+
- 15:09:44 [Mike_Elledge]
- awk: Would like us to get through the next couple of weeks and see if we need the extra time. Another option just do Tuesday with extra time and see if we need Thursday.
- 15:09:56 [Detlev]
- I'm in - Mac users, use Firefox, not Safari
- 15:10:21 [JF]
- ack JF
- 15:10:26 [alastairc]
- alastairc has joined #ag
- 15:10:32 [JF]
- ack Alex
- 15:10:35 [bruce_bailey]
- +1 to two hour call Tuesday, especially since I have not been able to make Thursday calls
- 15:11:21 [Mike_Elledge]
- alex: Depends where we are in process. Don't want to do perpetually. It would add up. If we can make real progress, don't fill up time by talking. Only if we help productivity.
- 15:11:39 [Mike_Elledge]
- alex: Make judgement a week in advance.
- 15:12:33 [Mike_Elledge]
- awk: agree. Challenging to make judgement a week in advance. Ppl don't have calendars set. For month of August seems worthwhile. Survey set to go. Beneficial and well-structuerd enought.
- 15:12:49 [Joshue108]
- q?
- 15:13:26 [david-macdonald]
- david-macdonald has joined #ag
- 15:13:30 [Mike_Elledge]
- jf: Don't know how got into queue. Having agenda with firm times will help. Have to be careful not to let it spill over. On board with adding time for next 6 weeks.
- 15:13:48 [david-macdonald]
- present+ david-macdonald
- 15:14:00 [Mike_Elledge]
- awk: Try for rest of August. Will reduce time if don't fill out schedule.
- 15:14:11 [Glenda]
- +1
- 15:14:28 [Mike_Elledge]
- awk: Start now or Thursday.
- 15:14:29 [Detlev]
- =1 for etending tues call now
- 15:14:34 [Detlev]
- =1
- 15:14:46 [Detlev]
- +1
- 15:15:10 [Mike_Elledge]
- awk: Start Thursday. Next week will split scribing in half too.
- 15:15:52 [Mike_Elledge]
- resolution: Extend the calls starting Thursday August 10. Split scribing for long call.
- 15:16:22 [Avneesh]
- Avneesh has joined #ag
- 15:16:32 [Mike_Elledge]
- RESOLUTION: Extend the calls starting Thursday August 10th. Split scribing for long call.
- 15:16:39 [alastairc]
- present+ alastairc
- 15:16:41 [Mike_Elledge]
- Zakim, next item
- 15:16:41 [Zakim]
- agendum 4. "timeouts (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC1)" taken up [from AWK]
- 15:16:46 [AWK]
- +AWK
- 15:16:59 [Avneesh]
- present+
- 15:17:05 [AWK]
- Zakim, take up item 2
- 15:17:05 [Zakim]
- agendum 2. "Concurrent Input Mechanisms (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xSC8)" taken up [from AWK]
- 15:17:09 [Mike_Elledge]
- awk: Reminder use + with name to sign in.
- 15:17:16 [JF]
- agenda?
- 15:18:23 [Mike_Elledge]
- awk: Discussed last week after ppl had dropped off. Survey: 12 ready to go, 1 have issues. Jason: Make sure do work in other document. Agree. Alex: wordsmithing. Saw wordsmithing and raised you!
- 15:18:31 [Mike_Elledge]
- awk: have you seen?
- 15:18:34 [AWK]
- AWK's edits: Web content does not restrict use of input modalities available on a platform except if the restriction is necessary to ensure the security of the content, or if the restriction would invalidate an activity or override a user setting.
- 15:18:36 [Mike_Elledge]
- alex: just did.
- 15:19:08 [Alex]
- q+
- 15:19:16 [Mike_Elledge]
- awk: Believe says same thing as intended. Addresses potential confusion of meaning.
- 15:19:16 [AWK]
- ack a
- 15:20:06 [Mike_Elledge]
- alex: My intention was use of essential. Essential well-known in wcag 2.0.
- 15:20:17 [david-macdonald]
- 2.2.1 Essential Exception: The time limit is essential and extending it would invalidate the activity;
- 15:20:33 [Mike_Elledge]
- awk: Use essential.
- 15:20:51 [Wilco]
- Wilco has joined #ag
- 15:20:55 [david-macdonald]
- q+
- 15:20:55 [Mike_Elledge]
- alex: use negative term now. would invalidate. not same language.
- 15:21:49 [Mike_Elledge]
- awk: does security fall under essential as well?
- 15:21:59 [Mike_Elledge]
- alex: don't know, ususally content not security.
- 15:22:23 [Mike_Elledge]
- dm: do have a precedent for invalidate. not close enough to say.
- 15:22:59 [Mike_Elledge]
- detleve: IRC
- 15:23:09 [AWK]
- AWK: Web content does not restrict use of input modalities available on a platform except if the restriction is essential, or is required to ensure the security of the content.
- 15:23:30 [Mike_Elledge]
- awk: suggestion, captures security as well as content.
- 15:23:49 [Kathy]
- q+
- 15:23:59 [Mike_Elledge]
- dm: looks alright.
- 15:23:59 [AWK]
- ack d
- 15:23:59 [alastairc]
- "except if" sounds odd, wouldn't it be: "except content where"
- 15:24:02 [AWK]
- ack kathy
- 15:24:16 [Alex]
- Web content does not restrict use of input modalities available on a platform except if the restriction is essential, or is required to ensure the security of the content or respect user setting
- 15:24:21 [Detlev]
- you are very quiet
- 15:24:34 [Mike_Elledge]
- kathy: fine. add understanding to clarify the point. make sure Thursday callers okay with that.
- 15:24:45 [Alex]
- q+
- 15:25:14 [Mike_Elledge]
- kathy: need to make sure lisa is okay with that.
- 15:25:23 [Mike_Elledge]
- alex: user setting for platform or content?
- 15:25:38 [AWK]
- ack ale
- 15:25:38 [Mike_Elledge]
- jf: could be user settings in future.
- 15:25:57 [Mike_Elledge]
- alex: which is it for? user agent or AT?
- 15:26:34 [Mike_Elledge]
- jf: user agent stands for user, AT, browser, don't really care so long as it is respected.
- 15:26:46 [Mike_Elledge]
- alex: if ambiguous hard to tell what failed.
- 15:27:12 [Mike_Elledge]
- alex: shouldn't it be about the content.
- 15:27:19 [AWK]
- Possible new version, based on Alex's:
- 15:27:20 [AWK]
- Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or respect user settings
- 15:27:41 [Mike_Elledge]
- jf: wondering if we have examples where it is happening today. alsmost testing for negative, but still valid.
- 15:28:06 [Mike_Elledge]
- jf: not aware of any code that's restricting it today. could test it then.
- 15:28:13 [Alex]
- q+
- 15:28:32 [Detlev]
- q=
- 15:28:39 [Detlev]
- q+
- 15:28:45 [Mike_Elledge]
- awk: didn't get any examples. Kathy and Patrick worked on it and fixed. Ppl provided examples of how it could take place.
- 15:29:40 [Mike_Elledge]
- alex: philosophically, do we want criteria where we don't find a real world situation. applies to a lot of content. "don't break something we haven't seen anyone break in a while."
- 15:29:41 [david-macdonald]
- q+
- 15:29:47 [AWK]
- ack alex
- 15:30:06 [david-macdonald]
- q-
- 15:30:19 [JF]
- Q+
- 15:30:20 [AWK]
- ack detlev
- 15:30:23 [Mike_Elledge]
- kathy: look at video that was posted? patrick showed the issue. but it has since been fixed. Have found it.
- 15:31:10 [Mike_Elledge]
- detlev: some sites are coded for touch, but would not work for mouth. there are ways to do that. keyboard on ios devices, may need a keyboard for some inputs.
- 15:31:11 [AWK]
- ack JF
- 15:32:13 [Mike_Elledge]
- jf: agree that don't want to create requirements for things not in real world. strobing is a requirement, but not seen often. doesn't mean it doesn't exist if don't have lots of examples. will only grwo. so let's be pre-emptive.
- 15:32:26 [david-macdonald]
- q+
- 15:32:32 [david-macdonald]
- https://www.youtube.com/watch?v=f_2GKsI9TQU
- 15:32:51 [AWK]
- Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or respect user settings
- 15:33:15 [Mike_Elledge]
- mike: +1
- 15:33:26 [Mike_Elledge]
- alex: ok
- 15:33:29 [Detlev]
- +1 to that
- 15:33:33 [marcjohlic]
- +1 to AWK's wording
- 15:33:35 [Kathy]
- +1
- 15:33:41 [alastairc]
- +1
- 15:33:47 [Alex]
- q+
- 15:33:53 [kirkwood]
- +1
- 15:33:54 [Joshue108]
- +1 to AWK
- 15:34:00 [AWK]
- ack da
- 15:34:00 [Mike_Elledge]
- awk: valuable even if not common?
- 15:34:02 [KimD]
- +1
- 15:34:43 [Mike_Elledge]
- dm: we could put in draft. ask for more examples before we put it in. extra burden with each sc. onus to provide real world examples.
- 15:34:46 [AWK]
- ack alex
- 15:34:47 [david-macdonald]
- +1
- 15:35:26 [Mike_Elledge]
- alex: david took words out of my mouth. need real examples so we're not making it up.
- 15:35:44 [Mike_Elledge]
- awk: put in editors draft?
- 15:35:52 [Mike_Elledge]
- mike e: +1
- 15:35:54 [Detlev]
- +1
- 15:35:57 [Joshue108]
- +1
- 15:36:14 [kirkwood]
- +1
- 15:36:29 [Mike_Elledge]
- awk: any objection to put in editor's next public working draft (npwf)?
- 15:36:30 [Glenda]
- +1
- 15:36:41 [Kathy]
- I will update Github
- 15:36:52 [AWK]
- Kathy will update SC text with "Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or respect user settings"
- 15:36:59 [Kathy]
- yes
- 15:37:20 [Mike_Elledge]
- RESOLUTION: Accept as amended.
- 15:37:43 [Mike_Elledge]
- zakim, take up item 3
- 15:37:43 [Zakim]
- agendum 3. "Popup Visibility (https://www.w3.org/2002/09/wbs/35422/Final_prelockdown_set/results#xsc11)" taken up [from AWK]
- 15:37:45 [Joshue108]
- \0/
- 15:38:26 [Joshue108]
- https://github.com/w3c/wcag21/issues/75
- 15:38:33 [Mike_Elledge]
- awk: issue 75: 6 ready, 7 issues.
- 15:38:51 [JF]
- I've not yet submitted the survey, but I too have concerns/issues
- 15:39:26 [Mike_Elledge]
- alex: mostly text is not clear. unintended consequences of ambiguous language. didn't have opportunity to connect with steve. no conclusion yet.
- 15:41:00 [Mike_Elledge]
- steve: made changes. interference to visibility. editorial to keyboard focus, another? term popup still an issue for some ppl. only term very close is hoverbox.
- 15:41:15 [steverep]
- https://en.wikipedia.org/wiki/Hoverbox
- 15:41:23 [Detlev]
- hover box even after receiving kb focus?
- 15:41:24 [Mike_Elledge]
- steve: not really used much--to our adnvantage?
- 15:41:30 [Mike_Elledge]
- jf: modal dialog?
- 15:41:57 [AWK]
- AWK: don't think that this is talking about modals
- 15:42:07 [Joshue108]
- JOC: No - thats why, popover as a term was discussed last week.
- 15:42:11 [Mike_Elledge]
- alex: popup is generic, defines many things. tool tip, modal dialog, problematic.
- 15:42:22 [AWK]
- current definition for popup: content which becomes visible only when associated content, called the trigger, gains keyboard focus or pointer hover
- 15:42:24 [Mike_Elledge]
- alex: is that covered.
- 15:42:33 [Mike_Elledge]
- jf: js alert a popup?
- 15:42:36 [Detlev]
- that was steve, not alex I believe
- 15:42:44 [Mike_Elledge]
- alex: only if appears in hover focus.
- 15:42:55 [Alex]
- Mike, that's not me talking
- 15:42:59 [Detlev]
- Mike it is Steve speaking I b
- 15:43:11 [jasonjgw]
- q+
- 15:43:48 [Alex]
- q+
- 15:44:05 [KimD]
- * "Hoverbox" - I like that it's not used often. We can define/refine the word's meaning
- 15:44:18 [AWK]
- s/alex: is that/Steve: is that
- 15:44:18 [Glenda]
- +1 (agree with KimD)
- 15:44:23 [Mike_Elledge]
- steve: disadvantage for hover focus. can appear on focus only. generally would be calendar or number pad popup. less probelmatic to users. hover seems to dissuade ppl from popup definition.
- 15:44:33 [AWK]
- s/alex: popup is generic/steve: popup is generic
- 15:44:36 [Detlev]
- q+
- 15:44:47 [Joshue108]
- JOC: Hoverpop would be nice.
- 15:44:55 [AWK]
- s/alex: only if/steve: only if
- 15:44:57 [Mike_Elledge]
- steve: don't know how we would reword.
- 15:44:57 [AWK]
- ack jas
- 15:46:21 [Mike_Elledge]
- jas: not telling what we want it to, since not well-accepted term. wouldn't worry to use it in a draft. haven't heard any objections so far. putting in draft could inspire ppl to come up with different term.
- 15:46:30 [allanj]
- +1 to put in draft, get wider feedback/review
- 15:46:37 [AWK]
- ack alex
- 15:47:12 [david-macdonald]
- I think "hover box" is the way to go with a definition for it provided, to ensure we have what we need.
- 15:47:30 [Mike_Elledge]
- alex: couple of things. popup won't work. popup blocker wouldn't apply. need to invent term. lots of questions if trigger condition is problem and how it is a problem.
- 15:48:02 [jon_avila]
- jon_avila has joined #ag
- 15:48:05 [AWK]
- AWK: If we are trying to suggest device independence I would discourage "hover box"
- 15:48:33 [Mike_Elledge]
- detlev: transient content. hover box has disadvantage of multi-centric?
- 15:50:25 [Mike_Elledge]
- steve: condition on the trigger is there to ppl with vision problems have to re-focus all teh time. Not expexting it. moving focus difficult if magnifying. may have have to pan screen if can't turn it off or if it doesnt appear near trigger.
- 15:51:23 [Mike_Elledge]
- steve: under magnification outside of view have to move pointer to other part of screen, or have to scroll.
- 15:51:31 [AWK]
- q+
- 15:51:41 [AWK]
- ack det
- 15:51:58 [Mike_Elledge]
- steve: could have either or condition.
- 15:52:04 [Mike_Elledge]
- dm: what if button?
- 15:52:22 [Mike_Elledge]
- steve: rare if it appears over button. not covering re-styling.
- 15:52:47 [Mike_Elledge]
- dm: if popup obscures image, would want to press escape.
- 15:52:52 [AWK]
- ack a
- 15:53:00 [Mike_Elledge]
- steve: most apps don't have that programmed in.
- 15:53:33 [Joshue108]
- q?
- 15:53:57 [Mike_Elledge]
- awk: don't have objectin to using popup, but hear what alex is saying. could find a new term, whether transient content or whatever, let's just call it "x". What precsiely are we trying to solve?
- 15:54:43 [Mike_Elledge]
- awk: feels like one scenario when going to menu, try to move mouse on content that has come up, go outside of trigger area and not to content, it will go away. Have to be very careful--drives me crazy.
- 15:54:49 [steverep]
- q+
- 15:54:55 [Mike_Elledge]
- awk: not sure that text covers that.
- 15:55:06 [Rachael]
- Rachael has joined #ag
- 15:55:31 [AWK]
- ack st
- 15:56:06 [Mike_Elledge]
- steve: in my experience problem when you don't have interactive components in content, then author makes it that only the trigger will cause hover. If move away it disappears.
- 15:56:13 [Detlev]
- maybe Jon Avila can add his view what we want to focus on?
- 15:56:42 [Mike_Elledge]
- steve: try to follow a narrow path to popuup, don't know how to describe w/o getting into pixels.
- 15:56:49 [Mike_Elledge]
- awk: example?
- 15:57:10 [Mike_Elledge]
- steve: examples page.
- 15:57:34 [Mike_Elledge]
- steve: wiki editor. comments button.
- 15:58:05 [Mike_Elledge]
- awk: "add your reaction". don't think of magnification situation where user can't see all the content.
- 15:58:20 [Mike_Elledge]
- steve: if using mouse could move it off and have it disappear.
- 15:58:36 [Mike_Elledge]
- awk: other use cases?
- 15:59:03 [Mike_Elledge]
- alex: hovering at "add your reaction".
- 15:59:37 [allanj]
- see also - https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover#Perkins
- 15:59:45 [jon_avila]
- The member tooltip is an example that has more text.
- 15:59:46 [Mike_Elledge]
- awk: tooltip is pretty clsoe by to trigger, but sometime AT will read text on hover, will start to lose what's in tooltip, when move toward text it goes away.
- 16:00:06 [allanj]
- q+ to say example
- 16:00:21 [Mike_Elledge]
- steve: if you move your pointer towoard text goes away, but not if toward smiley face.
- 16:01:01 [jon_avila]
- Another example is on a screen that horizontally scrolls and the tooltip appears cutoff but when you scroll to see the rest of the tooltip the tooltip goes away
- 16:01:06 [Mike_Elledge]
- steve: want it to be clsoe enough not to trigger, but not so far away that it goes away when you zoom.
- 16:01:49 [Mike_Elledge]
- awk: for example, lengthy definition of a term can zoom in and not be able to see all. move to see rest and it disappears.
- 16:02:07 [Alex]
- q+
- 16:02:16 [AWK]
- ack all
- 16:02:16 [Zakim]
- allanj, you wanted to say example
- 16:02:16 [Mike_Elledge]
- steve: if have lots of AT large pointers and accents, want to move to see it all.
- 16:02:55 [allanj]
- example https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover#Cursor_Overlapping_Tooltip_Text_on_Hover_Example
- 16:03:25 [Mike_Elledge]
- jim: put link that says perkins above. hover over name and to goes away have to go very quickly to get to link that's in the middle.
- 16:03:43 [Mike_Elledge]
- jim: another example as well above.
- 16:04:12 [Mike_Elledge]
- awk: may be a platform issue, so need exception for situation where user agent controls hover.
- 16:04:58 [Mike_Elledge]
- jim: tooltip with actual information, ppl objected to <title> attribute.
- 16:04:59 [jon_avila]
- present+jon_avila
- 16:04:59 [steverep]
- q+
- 16:05:06 [AWK]
- ack alex
- 16:05:59 [Mike_Elledge]
- alex: when you hover over any link, browser edge and chrome shows destination in lower left hand side of window; won't work in this case. browser dictates it.
- 16:06:14 [Mike_Elledge]
- awk: would be a problem for users, but not covered in this sc.
- 16:06:23 [AWK]
- ack steve
- 16:06:24 [Mike_Elledge]
- alex: it is a predicament.
- 16:07:15 [Mike_Elledge]
- steve: two schools of thought. Content therefore have to accept it. Or not content, generated by agent so should address it.
- 16:07:18 [jon_avila]
- Also hover content that is off the edge of the screen
- 16:08:08 [Mike_Elledge]
- ja: other issue is when hover is cut-off. when try to scroll to see it it goes away.
- 16:08:38 [Mike_Elledge]
- awk: do magnification tools compensate for this? a way to pan within an area without triggering?
- 16:09:07 [Mike_Elledge]
- alex:not using mag software. see it in github. tooltip off right of screen.
- 16:09:33 [Alex]
- Mike, that was steve talking :)
- 16:09:49 [Mike_Elledge]
- steve: not sure, it's not the default. dk if there's a keyboard short-cut or if it's programmed in. wouldn't be heavily used if it was. can check.
- 16:10:01 [AWK]
- s/alex:not/steve:not
- 16:10:06 [Mike_Elledge]
- awk: wouldn't matter for the solution anyway, not everyone using mag tools.
- 16:10:40 [allanj]
- github uses CSS to display the aria-label
- 16:10:54 [Joshue108]
- q?
- 16:10:58 [Mike_Elledge]
- awk: just talking about when things are hovered over or focus; not clicking? like when menu popups options.
- 16:11:06 [Mike_Elledge]
- alex: yes in general.
- 16:11:16 [Alex]
- Mike, that's steve
- 16:11:21 [Alex]
- not Alex
- 16:11:22 [AWK]
- s/alex: yes in general/steve: yes in general
- 16:12:09 [Mike_Elledge]
- steve: managing focus is a way to get around some of these issues. like mega menu, can put focus on component so you can pan around without worrying about it going away.
- 16:12:48 [Mike_Elledge]
- steve: goes away and you try to see subitem one, then try to see content on subitem two and it goes away.
- 16:13:05 [Mike_Elledge]
- dm: does same thing on focus as on hover will fail people.
- 16:14:13 [Mike_Elledge]
- steve: in many cases would cover it. if get content on hover with clickable components, will put focus to move it away, disappears.
- 16:15:00 [Mike_Elledge]
- dm: in general if hover over popup it will stay. move off of popup to make it go away.
- 16:15:38 [Joshue108]
- q+
- 16:16:19 [Joshue108]
- ack me
- 16:16:21 [AWK]
- ack jo
- 16:16:22 [Mike_Elledge]
- awk: From survey: some issues: 1) using word popup. 2) make it clearer what it's trying to solve. 3) wordsmithing. What should we do.
- 16:16:25 [jasonjgw]
- q+
- 16:16:55 [steverep]
- q+ should I change to "hoverbox"?
- 16:17:07 [AWK]
- Josh: Suggests "reducce popup interference" as a good phrase
- 16:17:11 [Mike_Elledge]
- jo: found it useful to think in terms of popup interference. relates to megamenus being triggered accidentally too.
- 16:17:13 [AWK]
- ack jas
- 16:18:10 [Mike_Elledge]
- jason: what happens with rationale text. when ppl are deciding on proposal would be helpful to have rationale. useful also if tightening sc that we already have.
- 16:18:35 [Mike_Elledge]
- jason: good rationale is helpful for review.
- 16:19:16 [allanj]
- -1 hoverbox
- 16:19:24 [Detlev]
- I prefer transient content
- 16:19:26 [Mike_Elledge]
- awk: change popup to hover box? Hover box refers to pointer-specific functionality, wouldn't be right term for keyboard instance.
- 16:19:27 [david-macdonald]
- transient popup
- 16:19:34 [Joshue108]
- dont like the box in hover
- 16:19:40 [JF]
- -1 to hoverbox
- 16:19:41 [JakeAbma]
- -1 hoverbox
- 16:19:47 [Rachael]
- -1 hoverbox
- 16:19:57 [Joshue108]
- Something like popover was better..
- 16:20:02 [alastairc]
- I don't like the 'hover' in 'hoverbox'. Or box.
- 16:20:08 [Kathy]
- no preference as long as it is defined well
- 16:20:11 [Joshue108]
- lol
- 16:20:28 [Mike_Elledge]
- mike: hover content?
- 16:20:30 [Detlev]
- straw poll on transient content, perhaps?
- 16:20:48 [Joshue108]
- transoveronhoverentity?
- 16:20:56 [alastairc]
- NB: I'm not going to object though, I'd rather see it in the draft.
- 16:21:10 [Mike_Elledge]
- awk: address remaining issues. not insurmountable. but need clarification before goes in editor's draft. What do you think.
- 16:21:11 [Joshue108]
- I wont object,,
- 16:21:21 [Mike_Elledge]
- dm: put in editor's draft, clean up later.
- 16:21:22 [Kathy]
- I would like the definitions clarified first
- 16:21:27 [Joshue108]
- I think Jason is right about the definition being important
- 16:21:34 [steverep]
- +1 to David, cleanup later
- 16:21:45 [Glenda]
- +1 to put in editor’s draft (and wordsmith as we get public feedback)
- 16:21:48 [Joshue108]
- +1 to getting it in
- 16:21:48 [Mike_Elledge]
- jf: wordsmithing on list. general principle has acceptance.
- 16:22:00 [bruce_bailey]
- +1 to including in next draft
- 16:22:08 [Mike_Elledge]
- dm: require that it disappear...
- 16:22:15 [KimD]
- Agree, more wordsmithing issue than content/concept
- 16:22:32 [Alex]
- more wordsmithing
- 16:23:03 [jon_avila]
- can we put a note about the term pop telling people we will be coming up with a different term?
- 16:23:05 [JF]
- +1 to attempting to wordsmith on-list, and revisit on Thursday
- 16:23:05 [allanj]
- +1 in now
- 16:23:07 [steverep]
- Would anyone to object to a CFC now? I can add an editor's note.
- 16:23:08 [Kathy]
- can we update the definitions
- 16:23:10 [Mike_Elledge]
- awk: editor's draft, requires cfc. or take it up thursday. should be able to get in w/o lots of extra tiem by 22nd.
- 16:23:15 [Detlev]
- +1 include with some wordsmithing and a good def
- 16:23:29 [david-macdonald]
- +1 in now
- 16:23:31 [marcjohlic]
- +1 to add now - let's put a stake in the ground on a term and add it..
- 16:23:35 [Joshue108]
- +1 in now
- 16:23:45 [KimD]
- I'd be ok with putting in as is, with note as Jon said
- 16:23:47 [Mike_Elledge]
- awk: no consensus.
- 16:24:19 [Mike_Elledge]
- awk: let's do wordsmithing so we can wrap up thursday.
- 16:24:34 [MichaelC]
- q+
- 16:24:47 [Kathy]
- the definitions need to be updated
- 16:24:50 [Mike_Elledge]
- steve: when can we put in stake? other than popup? nothing out there matches it better.
- 16:24:56 [Joshue108]
- q?
- 16:25:05 [kirkwood]
- +1 to put in editor draft define term popup
- 16:25:12 [Mike_Elledge]
- jf: so long as have clear definition okay. must define popup better.
- 16:25:22 [AWK]
- ack mic
- 16:25:26 [david-macdonald]
- "transient popup" distinguishes it from triggered popup on ENTER
- 16:25:29 [bruce_bailey]
- q+ to ask JF where definition fails?
- 16:25:42 [Detlev]
- agree with speaker before that popup is used by browsers (blocker) and shouldn't be used
- 16:26:01 [jon_avila]
- +1 to Michael
- 16:26:03 [allanj]
- definition: content which becomes visible only when associated content, called the trigger, gains keyboard focus or pointer hover
- 16:26:15 [Glenda]
- +1 put it in now with editor note about definition. Stop taking up working group time on this one.
- 16:26:16 [Joshue108]
- +1 to Michael so I'd accept hoverbox as a more semantically accurate term
- 16:26:17 [Detlev]
- ok +1 to Michael
- 16:26:17 [Mike_Elledge]
- mc: think about timelien. throw it in for path. in past have put notes that will be working on it. put in now. ppl can work on it. not take more time.
- 16:26:36 [Glenda]
- Public Working draft is not a FINAL
- 16:26:36 [jon_avila]
- I didn't hear that we were still talking about what's in and out
- 16:26:45 [allanj]
- perhaps we need a wider view of what's in/out
- 16:26:47 [Mike_Elledge]
- alex: still talking about what is in and out. far cry from saying "let's move forward".
- 16:26:49 [jon_avila]
- I formerly disagree with Alex
- 16:26:50 [Glenda]
- Public Working Draft is to get public feedback
- 16:27:05 [Mike_Elledge]
- alex: what is in and what is out?
- 16:27:16 [jon_avila]
- deferring it will kill it.
- 16:27:21 [AWK]
- s/alex: what is in and what is out?/steve: what is in and what is out?
- 16:27:31 [JF]
- Q+ to ask why we cannot continue to fine-tune this over the next 48 hours, and revisit on thursday
- 16:27:31 [Mike_Elledge]
- steve: have to be clear what we are asking people to do
- 16:27:32 [Joshue108]
- q?
- 16:27:33 [JF]
- +1 to Alex
- 16:27:34 [Joshue108]
- q+
- 16:27:41 [AWK]
- ack b
- 16:27:41 [Zakim]
- bruce_bailey, you wanted to ask JF where definition fails?
- 16:28:08 [Mike_Elledge]
- bb: not undestanding what alex and john f can't live with. popup poor, not perfect, but what can't you live with.
- 16:28:08 [AWK]
- q+ AWK
- 16:28:15 [alastairc]
- https://rawgit.com/w3c/wcag21/popup-interference_ISSUE-75/guidelines/#dfn-popup
- 16:28:20 [Mike_Elledge]
- jf: don't see popup definition.
- 16:28:22 [allanj]
- definition https://rawgit.com/w3c/wcag21/popup-interference_ISSUE-75/guidelines/terms/21/popup.html
- 16:28:26 [alastairc]
- content which becomes visible only when associated content, called the trigger, gains keyboard focus or pointer hover
- 16:28:26 [Mike_Elledge]
- bb: it's in draft.
- 16:28:37 [Mike_Elledge]
- jf: sorry not seeing it in actual draft.
- 16:28:38 [Joshue108]
- https://rawgit.com/w3c/wcag21/popup-interference_ISSUE-75/guidelines/terms/21/popup.html
- 16:28:48 [Mike_Elledge]
- bb: look into github.
- 16:28:53 [Joshue108]
- q?
- 16:29:00 [Mike_Elledge]
- bb: works as is.
- 16:29:19 [Mike_Elledge]
- steve: posted question about it this morning.
- 16:30:09 [AWK]
- ack JF
- 16:30:09 [Zakim]
- JF, you wanted to ask why we cannot continue to fine-tune this over the next 48 hours, and revisit on thursday
- 16:30:10 [Mike_Elledge]
- alex: trigger point, if you have very large trigger, how is it a trigger.
- 16:30:49 [Mike_Elledge]
- jf: we're discussing for 20 minutes plus. still needs further discussion. don't see risk for letting it simmer for 48 hours.
- 16:30:49 [AWK]
- +1 JF point on working for 48 hours
- 16:30:51 [Joshue108]
- ack me
- 16:30:51 [AWK]
- ack josh
- 16:30:53 [jon_avila]
- would be open to allow hover to cover trigger area that doesn't contain content. That is it's ok to cover empty space of trigger
- 16:31:17 [alastairc]
- Suggested def: "An element that appears when the mouse is placed over a triggering element, or the keyboard focus is on the triggering element."
- 16:31:21 [Mike_Elledge]
- jo: fine with that. have you been on call from last week?
- 16:32:20 [Mike_Elledge]
- jo: agree with michael c. my conclusion is that we have reasonable definition, term not perfect, but would like to see it go in. in case of use case went over it quite well with mouseover.
- 16:32:20 [AWK]
- ack AWK
- 16:32:43 [Mike_Elledge]
- jf: burned a lot of time haven't reached a resolution. two more days is reasonable.
- 16:33:24 [Mike_Elledge]
- awk: waiting another couple of days okay, willing to look at definitions. as long as people can look at before hand.
- 16:33:28 [Mike_Elledge]
- q+
- 16:33:34 [david-macdonald]
- I agree that there are some situations where we don't want to forbid the popup from overlapping the trigger
- 16:33:46 [Mike_Elledge]
- awk: some valid concerns: tooltip covering large area.
- 16:34:18 [Mike_Elledge]
- awk: let's work on this, take it up on Thursday.
- 16:34:59 [Mike_Elledge]
- awk: this, personalization, time-outs on Thursday. Please look at CFCs.
- 16:35:12 [Mike_Elledge]
- jf: moving to two hours on thursday.
- 16:35:15 [AWK]
- Zakim, list attendees
- 16:35:15 [Zakim]
- As of this point the attendees have been AWK, Rachael, Kathy, Joshue108, JF, shadi, MikeGower, david-macdonald, KimD, alastairc, Elledge, Makoto, Detlev, kirkwood, jasonjgw,
- 16:35:18 [Zakim]
- ... JakeAbma, steverep, Melanie_Philipp, Glenda, bruce-bailey, Avneesh, jon_avila
- 16:35:28 [Mike_Elledge]
- trackbot, end meeting
- 16:35:28 [trackbot]
- Zakim, list attendees
- 16:35:28 [Zakim]
- As of this point the attendees have been AWK, Rachael, Kathy, Joshue108, JF, shadi, MikeGower, david-macdonald, KimD, alastairc, Elledge, Makoto, Detlev, kirkwood, jasonjgw,
- 16:35:31 [Zakim]
- ... JakeAbma, steverep, Melanie_Philipp, Glenda, bruce-bailey, Avneesh, jon_avila
- 16:35:36 [trackbot]
- RRSAgent, please draft minutes
- 16:35:36 [RRSAgent]
- I have made the request to generate http://www.w3.org/2017/08/08-ag-minutes.html trackbot
- 16:35:37 [trackbot]
- RRSAgent, bye
- 16:35:37 [RRSAgent]
- I see no action items