W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > October 2016

RE: Metadata on Mouse-Over SC

From: <alands289@gmail.com>
Date: Wed, 26 Oct 2016 08:19:01 -0400
Message-ID: <58109f39.5667370a.becae.41d3@mx.google.com>
To: Laura Carlson <laura.lee.carlson@gmail.com>, Alastair Campbell <acampbell@nomensa.com>
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Alastair,

Thank you for your work to reword this.

I feel this gets to the heart of the matter and keeps it technology independent.

Thank you for taking my criticism of the previous work as I know there was a lot of work in getting it to where it was.

This is much better and should have a better chance of approval.

Alan

Sent from Mail for Windows 10

From: Laura Carlson
Sent: Wednesday, October 26, 2016 7:40 AM
To: Alastair Campbell; ALAN SMITH
Cc: public-low-vision-a11y-tf
Subject: Re: Metadata on Mouse-Over SC

Hi Alastair and all,

Thank you for your work on this. Very much appreciated. I'll check it out.

Alan, can you live with this latest version?

Kindest Regards,
Laura

On Oct 25, 2016 5:49 PM, "Alastair Campbell" <acampbell@nomensa.com> wrote:

> > Ideas on how best to do that?
>
> It was next in my list!
>
> I've updated the wiki page [1] with this:
> "Hidden content or metadata that is necessary for understanding is
> available using any available input method."
>
> So the intent was:
> - It should be important information for the page, supplemental
> information is ok.
> - It should be hidden information, including metadata/attributes.
> - It should not be input specific, essentially it should be available via
> keyboard, mouse, touch, whatever is available in that technology / device.
>
> For me it is closely related to 2.1.1 Keyboard, but it could fit under 1.4
> instead.
>
> I think historically many cases would be covered by 'functionality' being
> available to keyboard users, as the vast majority of hidden content would
> be in components like accordion show/hide things.
>
> If we are aiming for minimum overlap of SCs in WCAG 2.1, then I would take
> out the "content or" and just have "metadata", but the general version
> makes sense to me.
>
> Looking at the examples, I realise this doesn't explicitly address the
> issue with expanding cursors obscuring tool-tips, but I think it does rule
> out that use-case as an author would have to use a method available via the
> keyboard as well.
>
> If it were available via keyboard/touch, you wouldn't have to mouse-over
> to get the content, and it wouldn't disappear when you move the large
> cursor away.
>
> Cheers,
>
> -Alastair
>
> 1] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_On_Hover
Received on Wednesday, 26 October 2016 12:19:36 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 14:44:31 UTC