- From: Detlev Fischer (TK) <detlev.fischer@testkreis.de>
- Date: Thu, 18 Jan 2018 16:51:28 +0100
- To: w3c-wai-gl@w3.org
Hi John, hyphenation is a slight improvement but I am not yet convinced we really need to spell out receiving and removing, visible and hidden. But I won't object to the SC on these grounds. Detlev Am 18.01.2018 um 15:48 schrieb John Foliot: > Just noticed that Detlev had a similar parsing concern as I. Detlev, > what do you think of my proposal to hyphenate the two terms? > > On Thu, Jan 18, 2018 at 9:47 AM, John Foliot <john.foliot@deque.com > <mailto:john.foliot@deque.com>> wrote: > > +1 with an extremely small editorial observation: I find this > somewhat difficult to parse, and suggest that we hyphenate two > 'compound terms' used here. > > Current: > > Where receiving and removing pointer hover or keyboard focus > triggers additional content to become visible and hidden, > respectively, the following are true: > > Suggested: > > Where receiving and removing pointer-hoveror keyboard-focus > triggers additional content to become visible and hidden, > respectively, the following are true: > > However, I wouldn't want this to be a blocking function, so I'm > good with what we have now (it's just a suggestion...) > > > JF > > On Thu, Jan 18, 2018 at 9:07 AM, Detlev Fischer (TK) > <detlev.fischer@testkreis.de <mailto:detlev.fischer@testkreis.de>> > wrote: > > +1 > Detlev > > The change to "Where receiving and removing pointer hover or > keyboard focus triggers additional content to become > visibleand hidden, respectively..." strikes me as harder to > understand, if more precise. I prefer the previous version of > this initial sentence, thinking that no formulation will ever > snuff out chances of misconstrual. But I won't stand in the > way of this one... > > > > Am 18.01.2018 um 01:08 schrieb Andrew Kirkpatrick: > > > Call For Consensus — ends Friday January 19th at 7pm > Boston time. > > The Working Group has discussed responses to the following > issues: > > 650: (https://github.com/w3c/wcag21/issues/650 > <https://github.com/w3c/wcag21/issues/650>) > > 655: (https://github.com/w3c/wcag21/issues/655 > <https://github.com/w3c/wcag21/issues/655>) > > 695: (https://github.com/w3c/wcag21/issues/695 > <https://github.com/w3c/wcag21/issues/695>) > > 711: (https://github.com/w3c/wcag21/issues/711 > <https://github.com/w3c/wcag21/issues/711>) > > Response to Issue 650: > https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#650 > <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#650> > > Response to Issue 655: > https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#655 > <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#655> > > Response to Issue 695: > https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#695 > <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#695> > > Response to Issue 711: > https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#711 > <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#711> > > The changes to the SC are implemented in this pull > request: https://github.com/w3c/wcag21/pull/739 > <https://github.com/w3c/wcag21/pull/739> > > The changed SC can be viewed here: > http://rawgit.com/w3c/wcag21/hover-focus-edits/guidelines/#content-on-hover-or-focus > <http://rawgit.com/w3c/wcag21/hover-focus-edits/guidelines/#content-on-hover-or-focus> > > If you have concerns about this proposed consensus > position that have not been discussed already and feel > that those concerns result in you “not being able to live > with” this decision, please let the group know before the > CfC deadline. > > Thanks, > > AWK > > Andrew Kirkpatrick > > Group Product Manager, Accessibility > > Adobe > > akirkpat@adobe.com <mailto:akirkpat@adobe.com> > <mailto:akirkpat@adobe.com <mailto:akirkpat@adobe.com>> > > http://twitter.com/awkawk > <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0 > <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>> > > > -- > --------------------------------------------------------------- > Detlev Fischer PhD > Testkreis > http://testkreis.de > > Telefon: +49-40-43 18 75-25 <tel:%2B49-40-43%2018%2075-25> > Mobile: +49-157 57 57 57 45 <tel:%2B49-157%2057%2057%2057%2045> > Fax: +49-40-43 18 75-45 <tel:%2B49-40-43%2018%2075-45> > E-Mail: detlev.fischer@testkreis.de > <mailto:detlev.fischer@testkreis.de> > > Anschrift: Werderstr. 34, 20166 Hamburg > Amtsgericht Hamburg HRB 58 167 > --------------------------------------------------------------- > > > > > > -- > John Foliot > Principal Accessibility Strategist > Deque Systems Inc. > john.foliot@deque.com <mailto:john.foliot@deque.com> > > Advancing the mission of digital accessibility and inclusion > > > > > -- > John Foliot > Principal Accessibility Strategist > Deque Systems Inc. > john.foliot@deque.com <mailto:john.foliot@deque.com> > > Advancing the mission of digital accessibility and inclusion -- --------------------------------------------------------------- Detlev Fischer PhD Testkreis http://testkreis.de Telefon: +49-40-43 18 75-25 Mobile: +49-157 57 57 57 45 Fax: +49-40-43 18 75-45 E-Mail: detlev.fischer@testkreis.de Anschrift: Werderstr. 34, 20166 Hamburg Amtsgericht Hamburg HRB 58 167 ---------------------------------------------------------------
Received on Thursday, 18 January 2018 15:52:01 UTC