Re: side conversation on 386, 659, and 660, 669, and 688 on Character Key Shortcuts

I'm fine either way, I don't want to lose the SC over it.

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Wed, Jan 17, 2018 at 4:19 PM, Michael Gower <michael.gower@ca.ibm.com>
wrote:

> I prefer my suggestions to resolve, but I can live with your response
> rather than risk harpooning the SC.
> +1
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
>  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> gowerm@ca.ibm.com
> voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034
>
>
>
> From:        Andrew Kirkpatrick <akirkpat@adobe.com>
> To:        Michael Gower <michael.gower@ca.ibm.com>
> Cc:        James Nurthen <james.nurthen@oracle.com>, WCAG <
> w3c-wai-gl@w3.org>
> Date:        2018-01-17 12:46 PM
> Subject:        Re: side conversation on 386, 659, and 660, 669, and 688
> on Character     Key Shortcuts
> ------------------------------
>
>
> The issue from multiple commenters was the definition (which was for
> “character key”).
>
>
>
> The definition was: “single printable Unicode code point, any keyboard
> character that is printable, i.e. letters of the alphabet including
> capitals, punctuation, numbers, and symbols. Note that the Space and Enter
> keys, which return empty spaces rather than characters, are not character
> keys”.
>
>
>
> Commenters said that we are trying to redefine a commonly used term in
> order to exclude printable keys like space.  So, I tried to play with the
> definition and the SC just kept getting longer and longer, until  I removed
> the definition and just used what the SC was requiring before:
>
>
>
> In the second half, we were using “non-character key” and interpreting
> that as the opposite of character key, and that was expanded out also.
> Since space and enter were excluded from being character keys, they are
> “non-character keys”.
>
>
>
> It is true that a keyboard shortcut “b” could be replaced by “enter” in
> the final exception, but I don’t think that is too likely to happen. The
> only people who are going to use enter (and probably space) are going to be
> very aware of what they are doing, and like James indicates are going to
> need to be in the clear to do so.
>
>
>
> The current last exception reads:
>
> A mechanism is available to remap the shortcut to use one or more
> non-printable keyboard characters (e.g. Ctrl, Alt, Shift, etc.) or the
> Space or Enter keys.
>
>
>
> I’m happy to remove “shift” and maybe can clarify the final exception.
>
>
>
> A mechanism is available to remap the shortcut to use one or more* of
> either *non-printable keyboard characters (e.g. Ctrl, Alt, etc.) or the
> Space or Enter keys.
>
>
>
> Does any of this help?
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>
> *From: *Michael Gower <michael.gower@ca.ibm.com>
> *Date: *Wednesday, January 17, 2018 at 15:07
> *To: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Cc: *James Nurthen <james.nurthen@oracle.com>, WCAG <w3c-wai-gl@w3.org>
> *Subject: *Re: side conversation on 386, 659, and 660, 669, and 688 on
> Character Key Shortcuts
>
>
>
> Shift creates confusion. One can make a pretty good argument that an
> author who is failing this with "b" can now do Shift+b and pass. But
> Shift+b is equivalent to B, which we also don't want to allow as a
> single-character shortcut. It just becomes a bit wierder with the new
> language about "upper- and lower-case letters". I consider that a side
> issue though, so let me focus on the larger consideration.
>
> Previously, this was the basic logic flow of this SC:
>
> 1.        using one or more character keys alone as a shortcut?
> 1.        if yes, does it only work when component for which it is
> intended has focus?
> 1.        If yes, fine.
> 2.        If no, also use a modifier, or turn it off.
> 2.        If no, fine.
>
>
> Now we have:
>
> 1.        Using *letter, punctuation, number or symbol characters*alone
> as a shortcut?
> 1.        if yes, does it only work when component for which it is
> intended has focus?
> 1.        If yes, fine.
> 2.        If no, use a modifier, or turn it off, *or make the shortcut be
> Enter or Spacebar*.
> 2.        If no, fine.
>
>
>
> The other change is that "printable character" was previously defined:
> > single printable Unicode code point, any keyboard character that is
> printable, i.e. letters of the alphabet including capitals, punctuation,
> numbers, and symbols
> > Note that the Space and Enter keys, which return empty spaces rather
> than characters, are not character keys.
>
> So  Space and Enter keys were previously explicitly *excluded * from
> considerationin the definition*. *That was the only mention of them. If
> you used Spacebar or Enter as a shortcut, the SC didn't apply.
> The same exclusion happens now, since they are do not meet any of the
> criteria in the list, but it isn't explicit. But now they are *also*
> being called out as a new sanctioned way to overcome the problem. So now
> the direction is: "in any cirucumstance, make the shortcut into Enter or
> Spacebar and you pass!"
>
> I think that is problematic. If you want to have an explicit mention of
> Spacebar and Enter, they should be at the end in a note as an exclusion,
> not dumped into the second bullet. For instance, it could read "Note that
> Space and Enter keys are not considered letter, punctuation, number or
> symbol characters."
>
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
>  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> gowerm@ca.ibm.com
> voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034
>
>
>
> From:        Andrew Kirkpatrick <akirkpat@adobe.com>
> To:        Michael Gower <michael.gower@ca.ibm.com>
> Cc:        James Nurthen <james.nurthen@oracle.com>, WCAG <
> w3c-wai-gl@w3.org>
> Date:        2018-01-17 11:13 AM
> Subject:        Re: side conversation on 386, 659, and 660, 669, and 688
> on Character    Key Shortcuts
> ------------------------------
>
>
>
> Why is adding “shift” bad? With the current language shift would certainly
> count as a non-character key, so it would be ok for a mechanism to allow a
> shortcut “b” to become “shift+b” – this would solve the core issue that the
> single key shortcut created.  That said, I don’t mind removing shift from
> being explicitly mentioned.
>
>
>
> James has indicated a concern about space that would necessitate leaving
> it (and I should say that we have a product that currently uses space in a
> combination shortcut) and enter is a concern as a developer who needs to
> implement default form submission in a custom form would likely need to use
> it.
>
>
>
> Can you explain what is different in the SC now as opposed to when we
> referenced “character key” in the glossary and defined it as any printable
> key, not counting space or enter?
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> *http://twitter.com/awkawk*
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Ftwitter.com-252Fawkawk-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C38266e9a39d54d22c88a08d55de5e653-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636518164356826211-26sdata-3DHJ2f79lPfIDf9c-252F8XxDGS-252BkKh45tDddlC48GB3739KE-253D-26reserved-3D0&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=0FyoL9zNSMSfjbd10AIIip3mBxnU6sRFCZP1r-ruXcM&s=QJf_R78Q3nzDwmVclMMGLjaqZHHar_4pHtgEHislDmE&e=>
>
>
>
> *From: *Michael Gower <michael.gower@ca.ibm.com>
> *Date: *Wednesday, January 17, 2018 at 13:59
> *To: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Cc: *James Nurthen <james.nurthen@oracle.com>, WCAG <w3c-wai-gl@w3.org>
> *Subject: *Re: side conversation on 386, 659, and 660, 669, and 688 on
> Character Key Shortcuts
>
>
>
> I believe Kathy was the primary initiator of this SC, so I would encourage
> her to be consulted. BTW, I also find the inclusion of "Shift" in the
> wording now problematic, since arguably, a user could meet it with
> SHIFT+letter. So I have removed it and the etc, and would recommend
> including clarification about modifiers in the understanding document.
>
> To restate, I am requesting a change for the second Remap bullet, to
> become:
>
> "A mechanism is available to remap the shortcut to include one or more
> non-printable keyboard characters (e.g., Ctrl, Alt)"
>
> The current proposal reads like this:
>
>
> If a *keyboard shortcut*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Frawgit.com-252Fw3c-252Fwcag21-252Fcharacter-5Fchanges-252Fguidelines-252Findex.html-2523dfn-2Dkeyboard-2Dshortcuts-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C77c7c98cdeb04e9a082a08d55ddc7579-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636518123806038211-26sdata-3DVA-252BO7K5b61xxZ-252FD-252FQx13j7zIaZgQYN7LYRMEM9KmOhs-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DO6H_hMJoxDiwKF0PCkV5NbE9jDfyj1DLAVOEQ9rt5gA%26s%3DsvVPmpTedFwF9BQMuOoYlF-hK_ZDfjziDfm4QhVW5qo%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C38266e9a39d54d22c88a08d55de5e653%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518164356826211&sdata=ifSc0JdknOHJWtlchz3YjJ8l5fMgZ0oTJZ%2FlA7xSXwg%3D&reserved=0>is
> implemented in content using only letter (including upper- and lower-case
> letters), punctuation, number, or symbol characters, then at least one of
> the following is true unless the keyboard shortcut for a *user interface
> component*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Frawgit.com-252Fw3c-252Fwcag21-252Fcharacter-5Fchanges-252Fguidelines-252Findex.html-2523dfn-2Duser-2Dinterface-2Dcomponents-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C77c7c98cdeb04e9a082a08d55ddc7579-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636518123806038211-26sdata-3DBqFD-252F-252BEv0fD4XeKDmiCfPBD8r2YTZZfEScipHah1miQ-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DO6H_hMJoxDiwKF0PCkV5NbE9jDfyj1DLAVOEQ9rt5gA%26s%3DWxvNfhPwO9_-V29tKo4EE9M6I-zMI26Jmhvj6u0mWgk%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C38266e9a39d54d22c88a08d55de5e653%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518164356826211&sdata=fJ57KrMd8dxyXJPC47L7XBDElgvdVNwkL5IRp7m%2FUBg%3D&reserved=0>is
> only active when that component has focus:
>
> Turn off
>
> A *mechanism*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Frawgit.com-252Fw3c-252Fwcag21-252Fcharacter-5Fchanges-252Fguidelines-252Findex.html-2523dfn-2Dmechanism-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C77c7c98cdeb04e9a082a08d55ddc7579-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636518123806038211-26sdata-3DNR4-252FYXd-252B-252BgkNr2Hqf6-252BLsK3T0ELoregWmP4YliBrII0-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DO6H_hMJoxDiwKF0PCkV5NbE9jDfyj1DLAVOEQ9rt5gA%26s%3D6HqDoXgJ54YOhW2eq4tZGMwnliN4o6CX7-vhhgcd4VM%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C38266e9a39d54d22c88a08d55de5e653%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518164356826211&sdata=4sMllZ786NGHf%2FJ%2Bux8P%2B%2BKZv71O12ltpAD%2FwyxCUX4%3D&reserved=0>is
> available to turn the shortcut off;
>
> Remap
>
> A mechanism is available to remap the shortcut to use one or more
> non-printable keyboard characters (e.g. Ctrl, Alt, Shift, etc.) or the
> Space or Enter keys.
>
>
>
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
>  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> gowerm@ca.ibm.com
> voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034
>
>
>
> From:        Andrew Kirkpatrick <akirkpat@adobe.com>
> To:        Michael Gower <michael.gower@ca.ibm.com>
> Cc:        James Nurthen <james.nurthen@oracle.com>, WCAG <
> w3c-wai-gl@w3.org>
> Date:        2018-01-17 10:20 AM
> Subject:        side conversation on 386, 659, and 660, 669, and 688 on
> Character   Key Shortcuts
> ------------------------------
>
>
>
> Mike,
>
> Who needs to discuss it? We have about 4 hours.
>
>
>
> James, any thoughts?
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> *http://twitter.com/awkawk*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Ftwitter.com-252Fawkawk-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C77c7c98cdeb04e9a082a08d55ddc7579-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636518123806038211-26sdata-3DyaemkQSwc66vdCZL7dIpqXsQOsEsRRLUNxFNVxt8t48-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DO6H_hMJoxDiwKF0PCkV5NbE9jDfyj1DLAVOEQ9rt5gA%26s%3DgjGvb-ZsTMdlK-PNbF0lbs49Nvryzxkw0vU_TriPR2E%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C38266e9a39d54d22c88a08d55de5e653%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518164356826211&sdata=8TC7%2FRaCJ0FhLSwK2icYQw%2ByTyAlRBzvMufYit61qIU%3D&reserved=0>
>
>
>
> *From: *Michael Gower <michael.gower@ca.ibm.com>
> *Date: *Wednesday, January 17, 2018 at 13:17
> *To: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Cc: *James Nurthen <james.nurthen@oracle.com>, WCAG <w3c-wai-gl@w3.org>
> *Subject: *Re: CFC - Response to issues 386, 659, and 660, 669, and 688
> on Character Key Shortcuts
>
>
>
> -1
> Andrew, I would really like to get some more folks looking at this,
> because I do not read it that way. It seems far from clear, and could lead
> to some unfortunate implementations.
>
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
>  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> gowerm@ca.ibm.com
> voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034
>
>
>
> From:        Andrew Kirkpatrick <akirkpat@adobe.com>
> To:        Michael Gower <michael.gower@ca.ibm.com>, James Nurthen <
> james.nurthen@oracle.com>
> Cc:        WCAG <w3c-wai-gl@w3.org>
> Date:        2018-01-15 01:11 PM
> Subject:        Re: CFC - Response to issues 386, 659, and 660, 669, and
> 688 on Character  Key Shortcuts
> ------------------------------
>
>
>
> Mike,
>
> I don’t think that this is any different now.
>
>
>
> Originally, the SC said:
>
> If keyboard uses only character keys (doesn’t include space and enter)
> then a mechanism  to turn off the shortcut must exist or they need to be
> able to remap the shortcut to use at least one “non-character key” (keys
> that don’t count as character keys, including space and enter).
>
>
>
> Now it says the same thing, I believe.
>
>
>
> Authors might include space and enter – e.g. a mail application might use
> alt+enter to send a message, or space in a similar way. They are unlikely
> to use space or enter entirely independently.
>
>
>
> Enter could be used to trigger a default button in a custom form, so that
> one should probably stay. Space was mentioned by James Nurthen, but I’m not
> sure what the use case is – it seems to be more applicable when a control
> is focused.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> *http://twitter.com/awkawk*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Ftwitter.com-252Fawkawk-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C47440b8c4d4f4d38344f08d55dd68e9a-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636518098466995822-26sdata-3DLwi67pEpf2S45eMqpPYsOkYQoAXeSIp9AAYtBK8nvAk-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DJsbTENWb-yT7QWe-UsS4MygjMKBwDuyXKvgQo8_VrmA%26s%3D4pywp-Twt9UWIoup6Poj1Szz5cgMklE78kZvjc44tzY%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C77c7c98cdeb04e9a082a08d55ddc7579%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518123806038211&sdata=yzbq2My0dJPqJOto8x9xDEkRvmRBLlZnHoAeowYBAxk%3D&reserved=0>
>
>
>
> *From: *Michael Gower <michael.gower@ca.ibm.com>
> *Date: *Monday, January 15, 2018 at 14:56
> *To: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Cc: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *Re: CFC - Response to issues 386, 659, and 660, 669, and 688
> on Character Key Shortcuts
>
>
>
> I'm concerned with the rewording of Remap, both the addition of "or the
> Space or Enter keys" and the wording "to use".
> *https://github.com/w3c/wcag21/pull/732/files*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fpull-252F732-252Ffiles-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DkHbz4sNUxtaja4drJmEb4Re5pP3J5uD0YbPRcGFNNkw-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3D6SHjHUF_8rRPzOgpkqf7u1R2ySduxpsUURcM6ZsCR60%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=HPGvswaR9K33koYTBACxCGZOX0mVGMBKyZScQIDpJX8%3D&reserved=0>
> It is now proposed to read:
>
> <dd>A mechanism is available to remap the shortcut to use one or more
> non-printable keyboard characters (e.g. Ctrl, Alt, Shift, etc.) or the
> Space or Enter keys.</dd>
>
> In the original wording, Space and Enter were excepted from counting as
> character keys. That has now been altered to state that authors can use
> Space and Enter to replace author-created shortcuts. However, Space and
> Enter tend to be assigned by the user agent for specific activations. We
> should not be encouraging their use for remapping purposes, especially
> without the use of a modifier key. This will potentially lead to exactly
> the same issues with Speech operation that the SC was attempting to
> overcome.
>
> The concerns that were raised by the definition of character key seem to
> have been addressed by replacing 'character keys' with the phrase "using
> only letter (including upper- and lower-case letters), punctuation, number,
> or symbol characters ", which does not include Space or Enter. So it does
> not seem neccesary to later specify them in the remap definition. I would
> advocate that "or the Space or Enter keys" be removed.
>
> As well, the rewording infers that *just*a modifier key can now be used.
> I think this can be overcome by changing "use" to "include". The resulting
> Remap's definition would read:
>
> A mechanism is available to remap the shortcut to include use one or more
> non-printable keyboard characters (e.g. Ctrl, Alt, Shift, etc.).
>
>
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
>  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> gowerm@ca.ibm.com
> voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034
>
>
>
> From:        Andrew Kirkpatrick <akirkpat@adobe.com>
> To:        WCAG <w3c-wai-gl@w3.org>
> Date:        2018-01-14 11:30 PM
> Subject:        CFC - Response to issues 386, 659, and 660, 669, and 688
> on Character  Key Shortcuts
> ------------------------------
>
>
>
> Call For Consensus — ends Wednesday January 17th at 2:30am Boston time.
>
>
>
> The Working Group has discussed responses to the following issues:
>
> 386: What do 'character key' and 'printable' mean? (
> *https://github.com/w3c/wcag21/issues/386*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fissues-252F386-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DaWMX5cslqgiWnhgV8VQfe9c4SVZ8DtlJPbfVDC-252FVQQA-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3D_24xymbAjAZG-7VddwHvztSX9AHq7GPaQW_v8DwpPqE%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=hkTsE78vqs42sdp%2BKjV8cP3INKuikhlgBZXHKqdSNxg%3D&reserved=0>
> )
>
> 659: Ambiguous definition (*https://github.com/w3c/wcag21/issues/659*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fissues-252F659-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DcgtGJx5KW7QVoGK3UNmD991YqsPQTrrAosEcirzy2nA-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3D8qRAYkC0f9W0ePZGPXK37ZJcd-apPbCdd4jxfAdr0Qk%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=DAFTFPL4hMSyw5aE9PmpAdQ6psjy40wZuunc%2F35ndoQ%3D&reserved=0>
> )
>
> 660: Characters (*https://github.com/w3c/wcag21/issues/660*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fissues-252F660-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DFtCf11V-252Bg-252FkuzkMmBFPqJedKmb5F68UJqlCozGs-252Fgfc-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3D3ndtmgnT3yxywt6yhGM0mIFBxnTQpEoZOFv61VWnfhA%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=gelZxVANVEIC2rb55mJzwPRztlaHEwf7LmfYZuIYTIM%3D&reserved=0>
> )
>
> 669: SC 2.4.11 Character Key Shortcuts - Proposal for change of wording (
> *https://github.com/w3c/wcag21/issues/669*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fissues-252F669-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3Dqgu8Wt-252FNcNTvJjIpmwVjqZskSFBzqG160ByrtZc70PY-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3DLGVAoY5DHMj862f4OYthW_JGv2kbpKMrocS-bpljFnw%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=c%2FeXMtKb6QOaJQ97NIR2TPKShBw80%2FjstXhw0fUoCoU%3D&reserved=0>
> )
>
> 688: Comment on 2.4.11 (*https://github.com/w3c/wcag21/issues/688*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fissues-252F688-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DQ-252Bcfw7bxxKzVB9-252BPZpcRCv6styCM87do4u8JmBUV1fk-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3D_s4n7lOstY5X3xaCNioUAAFQz6TYgLvEdclC23TEMcc%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=N1ja%2BglRyRHeygwb5M1bJLaHm1uI1XmMgdeLReTC%2Frg%3D&reserved=0>
> )
>
>
>
> Response to Issue 386:
> *https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#386*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FWAI-252FGL-252Fwiki-252FDraft-5FResponses-5Fto-5FDec-5FWD-5FIssues-2523386-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DWIINb7Z9ulgSmH6XDteCobZwQF3DS83T4t30gGMJEF4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3DYp5DvZbuHjpti33z6TC68BxaFwOWuQ8e9LPx5B5gHxE%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=Im%2BEgL2fHT28V7Ad0Zu%2F9EdFYmSuiSywKPEK1BXlY4E%3D&reserved=0>
>
> Response to Issue 659:
> *https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#659*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FWAI-252FGL-252Fwiki-252FDraft-5FResponses-5Fto-5FDec-5FWD-5FIssues-2523659-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DcLrt1xjgGyyAFWqKWXGXoOq7pzlYtoaBKYEgbqWT1mc-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3De1EJtazdPG_0xBQ1uTURwEVc3M39AOiS3R3gJz_9Mh8%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=hR%2BwIMElBs%2FPQw6XLuqocyUNNScZeY86kccLqdDaNFo%3D&reserved=0>
>
> Response to Issue 660:
> *https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#660*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FWAI-252FGL-252Fwiki-252FDraft-5FResponses-5Fto-5FDec-5FWD-5FIssues-2523660-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DEOsc8fzyeTxa-252FOILeN-252Bg0SSE-252BzPu-252BFmlgpdQRzu4xaA-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3DDV5T8_Yj6bZTA0Q7mw947kDsj6vkvTbUiaS8VrqS2M0%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=yOpsKvZqbL34YrmquDMk8DjSwqI7vrf30ws3L5JJvIg%3D&reserved=0>
>
> Response to Issue 669:
> *https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#669*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FWAI-252FGL-252Fwiki-252FDraft-5FResponses-5Fto-5FDec-5FWD-5FIssues-2523669-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3Dt0kNd-252FkYN8B6zSrEt5C-252BuiGcHbX21imHCb5L0Nuf2fQ-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3DuY4keLEoardgCTiQck_HFD3-vE1wLxYiq7FRtM2RfW8%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=N2egWmxZ7GfIAnuYzRoLgXZiKyYMgX9XwbrVJTK3OhI%3D&reserved=0>
>
> Response to Issue 688:
> *https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#688*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fwww.w3.org-252FWAI-252FGL-252Fwiki-252FDraft-5FResponses-5Fto-5FDec-5FWD-5FIssues-2523688-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DdrsT1i2HttaeNLQrmjPQOGEcVNvmapxyqfWm7176uNc-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3DYnw1iwVEzqEGrEctcD9ANaRDyIrs0o6cgqcdhKyQNQA%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=cCwgvjPYbHiNWzz8j7b6Bb2sGayMbTfVF5f8Ki9BOuQ%3D&reserved=0>
>
>
>
> The changes to the SC are implemented in this pull request:
> *https://github.com/w3c/wcag21/pull/732*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fgithub.com-252Fw3c-252Fwcag21-252Fpull-252F732-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DTm1IP0ekF4Ern8TzFeE3TWUih2A8WvAJRuVz6gvcHA0-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3DbHsE56Gj7DN62XCKuMMXxxmimQ--tDHCMTamt9cvi68%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=ePyaTrFugdV8bWV8W%2F80MziwzV%2BYo4VYbujarUafRew%3D&reserved=0>
>
> The changed SC can be viewed here:
> *http://rawgit.com/w3c/wcag21/character_changes/guidelines/index.html#character-key-shortcuts*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Frawgit.com-252Fw3c-252Fwcag21-252Fcharacter-5Fchanges-252Fguidelines-252Findex.html-2523character-2Dkey-2Dshortcuts-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C23bfa30358854e50ffc808d55c52006d-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636516429627695916-26sdata-3DvgDNDq5yNqRY-252Fu-252FROJ3Ku9j6YuVxsZBVTYw1YQprxl4-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3Do0daxkHGHraHNw9i2iAgh1-u02Hps_TQhDkH1KZHuuQ%26m%3DSGu3s-aqIttQGHkoo_95d63cSn2_9Fuaa3f3zxbd7eQ%26s%3DwTTD5ryiHKbPVl5Y2WaNCQCQDr1wA8Cj8tM-kaPbpTU%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C47440b8c4d4f4d38344f08d55dd68e9a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636518098466995822&sdata=AUDE3A9qaFffEUNlXkuphd99Es9wr1fWW2j1X6nyaB0%3D&reserved=0>
>
>
>
> 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* <akirkpat@adobe.com>
>
> *http://twitter.com/awkawk*
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Ftwitter.com-252Fawkawk-26data-3D02-257C01-257C-257C54093524ef264326424008d51cd66c05-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636446629619786436-26sdata-3Dc5UP0xiniJIppvd6Esu1XA-252FbX1ykpABkhgCCmBp-252Fht8-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DX00PM93bEDvpNDPO1YFKMrnPyV5h_Kbm3Ao2RW7gG6A%26s%3D_xITGpoKEmuCNwm_e9Sk7LlvqY3zzObbTGh7DsC48qU%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C23bfa30358854e50ffc808d55c52006d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636516429627695916&sdata=uOaXQKWoj%2FogNBj1%2B472dGVEfEg%2BfNotLZW3gS88BzI%3D&reserved=0>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Received on Wednesday, 17 January 2018 21:41:06 UTC