Re: Issue 650 Does the Hover or focus SC apply to tabbed interfaces?

but if they don't move their mouse to dismiss it, how are they expected to
dismiss it.... with the keyboard? If so, why not just say that?

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 Sun, Jan 7, 2018 at 9:51 PM, Andrew Kirkpatrick <akirkpat@adobe.com>
wrote:

> Yes, that is the intent, for example a user is happily using their mouse
> to review content/UI and the new content pops up and covers some of what
> the person is trying to read so the goal is to allow that user to be able
> to dismiss the content and continue.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>
> *From: *David MacDonald <david100@sympatico.ca>
> *Date: *Sunday, January 7, 2018 at 20:43
> *To: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Cc: *Alastair Campbell <acampbell@nomensa.com>, "Abma, J.D. (Jake)" <
> Jake.Abma@ing.nl>, Patrick Lauke <redux@splintered.co.uk>, WCAG <
> w3c-wai-gl@w3.org>
> *Subject: *Re: Issue 650 Does the Hover or focus SC apply to tabbed
> interfaces?
>
>
>
> Why do we need "without moving pointer hover"? Do we really want to say
> "without moving pointer hover off of the popup or trigger"?
>
>
>
> Do we really mean without moving it **at all** ?
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902 <(613)%20235-4902>
>
> LinkedIn
>
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fdavidmacdonald100&data=02%7C01%7Cakirkpat%40adobe.com%7Ceee7a72e14714e88c19308d556394792%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509726373642651&sdata=Dd42ROIHFi9RZFUgfJ%2BCzcgY2O7FEf2A6oS2xdx16HE%3D&reserved=0>
>
> twitter.com/davidmacd
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fdavidmacd&data=02%7C01%7Cakirkpat%40adobe.com%7Ceee7a72e14714e88c19308d556394792%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509726373642651&sdata=dW6uKevsS1MebqSVC%2BaM3QlBRWOL3%2BQiC4Uqq1o%2BUZg%3D&reserved=0>
>
> GitHub
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDavidMacDonald&data=02%7C01%7Cakirkpat%40adobe.com%7Ceee7a72e14714e88c19308d556394792%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509726373642651&sdata=3wLmunA76RGZ7w3GaEszDj%2F2i%2F15qaSFpuDP2ty2LJo%3D&reserved=0>
>
> www.Can-Adapt.com
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7Cakirkpat%40adobe.com%7Ceee7a72e14714e88c19308d556394792%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509726373642651&sdata=L%2FxQhREO1Pqf0lPEdLEbda0y4w0%2FpLOdERZLx%2FsW%2FNo%3D&reserved=0>
>
>
>
> *  Adapting the web to all users*
>
> *            Including those with disabilities*
>
>
>
> If you are not the intended recipient, please review our privacy policy
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.davidmacd.com%2Fdisclaimer.html&data=02%7C01%7Cakirkpat%40adobe.com%7Ceee7a72e14714e88c19308d556394792%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509726373642651&sdata=jkhZuqbOFd8Y0RXlHK5VdQcDkQMgC08riTIBLCWYjbo%3D&reserved=0>
>
>
>
> On Sun, Jan 7, 2018 at 4:23 PM, Andrew Kirkpatrick <akirkpat@adobe.com>
> wrote:
>
> And we can certainly clarify this in the understanding document.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7Cakirkpat%40adobe.com%7Ceee7a72e14714e88c19308d556394792%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636509726373642651&sdata=kr%2Bsk9ZWuhK7xQ0sswoxPE2qS3l42WbCl1Hf0U7BNXE%3D&reserved=0>
>
>
>
> *From: *Alastair Campbell <acampbell@nomensa.com>
> *Date: *Sunday, January 7, 2018 at 16:08
> *To: *"Abma, J.D. (Jake)" <Jake.Abma@ing.nl>, Andrew Kirkpatrick <
> akirkpat@adobe.com>, David MacDonald <david100@sympatico.ca>, Patrick
> Lauke <redux@splintered.co.uk>
> *Cc: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *RE: Issue 650 Does the Hover or focus SC apply to tabbed
> interfaces?
>
>
>
> I read “additional content” as something that is added to the page,
> essentially over-the-top of the current page.
>
>
>
> If you take a bit of content away and put something else in it’s place,
> that is new, but not additional. The note does say “and other nonmodal
> popups” so I don’t think many will read it as applying to tabs.
>
>
>
> Cheers,
>
>
>
> -Alastair
>
>
>
> *From:* Abma, J.D. (
>
> About the definition for “additional content”, as can be read in my other
> comments, it's not present and what's present doesn't fit with the SC.
>
>
>