On Mon, Oct 14, 2013 at 4:04 PM, Bruno Racineux <bruno@hexanet.net> wrote: > I've ran into the following layout issue while using the accessibility audit > extension on Chrome. > https://github.com/GoogleChrome/accessibility-developer-tools/issues/64 > > In brief, there is an accessibility issue with floated images within an > anchor element, > which is present on the web on a potentially large scale, making links to > images invisible to keyboard readers. > > Should the anchor tag be made to wrap around a floated image to address > this? > > Presumably, it'd think the container size should match that of the clickable > area? (instead of being 0 0) > > Or should a recommendation be made to float the anchor instead as the only > way to get around this? > > I would appreciate some feedback. This is a CSS issue, not an HTML one - floated elements don't affect the sizes of their container elements, so if you float out all the contents, it collapses to a 0-height element (and, for inlines, 0-width). The semantics are still fine. You can avoid any weirdness with focus outlines by floating the <a> instead - it should have the same effect. ~TJReceived on Tuesday, 15 October 2013 17:05:03 UTC
This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:11 UTC