Re: Badly done hover

>From a cognitive disability perspective this is very frustrating as well.
It throws a lot out of focus.

*Jonathan Paul Katz*

*jpkatz@uchicago.edu <jpkatz@uchicago.edu>*


On Tue, Jul 25, 2017 at 12:05 PM, Balusani, Shirisha <sirib@uillinois.edu>
wrote:

> The download button should available on the image all the time instead of
> showing it on hover.
> Once the image is downloaded, it is little easier to read the content.
>
> -----Original Message-----
> From: Jonathan Avila [mailto:jon.avila@levelaccess.com]
> Sent: Tuesday, July 25, 2017 10:39 AM
> To: Michael A. Peters <mpeters@domblogger.net>; w3c WAI List <
> w3c-wai-ig@w3.org>
> Subject: RE: Badly done hover
>
> > It made the page behind the hover have bigger text but the actual hover
> actually got smaller.
>
> This is something I've seen a lot and have commented on as well.  Zooming
> in can make content get smaller as other regions of the page expand in
> fluid design.
>
> The wheel of the mouse can be taken over so control+wheel no longer
> scrolls but does some other action.  While this can be worked around with
> the keyboard this seems problematic.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> Level Access, inc. (formerly SSB BART Group, inc.)
> (703) 637-8957
> Jon.avila@levelaccess.com
> Visit us online: Website | Twitter | Facebook | LinkedIn | Blog Looking to
> boost your accessibility knowledge? Check out our free webinars!
>
> The information contained in this transmission may be attorney privileged
> and/or confidential information intended for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution or copying of this communication is strictly prohibited.
>
> -----Original Message-----
> From: Michael A. Peters [mailto:mpeters@domblogger.net]
> Sent: Monday, July 24, 2017 3:48 PM
> To: w3c WAI List <w3c-wai-ig@w3.org>
> Subject: Badly done hover
>
> http://gdprcoalition.ie/infographics/
>
> Clicked on an image, rather than just presenting the image, it presented
> the image in a JS hover.
>
> Text on image too small for me to read.
>
> Ctrl+ is what I do in those cases.
>
> It made the page behind the hover have bigger text but the actual hover
> actually got smaller.
>
> Things like that should really be tested for. Text on bitmap graphics is
> often problematic anyway but making the image show in a hover that doesn't
> respond to standard Ctrl-+ as expected is really bad.
>
>