- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 25 Oct 2016 22:49:34 +0000
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- CC: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
> 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 Tuesday, 25 October 2016 22:50:08 UTC