W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2016

RE: objects as links

From: Joe Chidzik <joe.chidzik@abilitynet.org.uk>
Date: Tue, 29 Nov 2016 11:41:10 +0000
To: "Michael A. Peters" <mpeters@domblogger.net>
CC: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <HE1PR0701MB2665601DC188EC092EAF4216B38D0@HE1PR0701MB2665.eurprd07.prod.outlook.com>

> If #topbanner bad is wider than the image, a usability bug is introduced.
> Because the image is a child of the anchor, the anchor is not limited to physical
> screen space of the image and (at least in some
> browsers) empty white space to the right and left of the image will trigger the
> anchor.

Have you styled the <a href> element as a CSS block level element? This would cause it to include white space around the image, but inside the <a> element, as clickable and part of the link. To resolve, just make sure <a href> is styled as CSS display: inline. 

Otherwise, as per Chaals' reply, this sounds like a browser bug issue. What does the browser inspector say about the whitespace around the element; is it selectable as part of the <a href> element when using the inspector object selector? 


Received on Tuesday, 29 November 2016 11:41:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 29 November 2016 11:41:47 UTC