WebAIM - Web Accessibility In Mind

E-mail List Archives

Fw: Regarding a Chrome bug for off-screen positioned active elements?

for

From: Bryan Garaventa
Date: May 10, 2012 7:12PM

FYI
Hopefully the Chrome focus issue will be a thing of the past in the near future.

So what is the consensus regarding off-screen positioning?

Personally I think 0 sizing should also be considered off-screen positioning, since hiding an element is what display:none and visibility:hidden are already designed to do.

----- Original Message -----
From: Dominic Mazzoni
To: <EMAIL REMOVED>
Sent: Thursday, May 10, 2012 4:35 PM
Subject: Re: Regarding a Chrome bug for off-screen positioned active elements?


Bryan, I agree about activating an element that has focus when set manually. That seems like a pretty clear bug.


Thanks for the pointers, Silvia. I think this is one of the areas that was underspecified before - we should figure out something all browsers can agree on and then test it heavily.



- Dominic


On Thu, May 10, 2012 at 3:59 PM, Bryan Garaventa < <EMAIL REMOVED> > wrote:

Thanks, I'm sure you mean whatsock.com.

I see what you mean in FF, but if you press shift+tab, it appears as well. I'm not sure why it's skipping the first link in the tab order. It's good to know there is a work around. If anyone else would care to join in whether 0 sizing qualifies as off-screen positioning, that would be helpful.

The most important issue here however, has to do with the lack of actual focus movement when setting focus to a non-actionable element.

This effects far more than just skip links, but dialogs, popups, menus, and many other dynamic control types where focus movement is used to ensure accessibility.

The problem is fully discussed at
http://webaim.org/discussion/mail_thread?threadF93

Thanks for looking into it. It may seem small, but this impacts many people.

----- Original Message -----
From: Dominic Mazzoni
To: <EMAIL REMOVED>
Sent: Thursday, May 10, 2012 3:33 PM
Subject: Re: Regarding a Chrome bug for off-screen positioned active elements?


Hi -


I just took a look at the example on whatsock.org. I can't get it to work without modifications in the latest Firefox either, could you double-check it?


It works correctly in both browsers if you get rid of font-size: 0, width: 0, and height: 0, and replace it with left: -999px to position it offscreen. Alternatively you can use opacity: 0 to make it invisible.


It's definitely not the intent of Chrome to make it impossible to have offscreen focusable elements, but elements with zero width or height are treated the same as invisible elements. Note that it's okay to set the font-size to 0 if you explicitly give it a width and height of at least 1 pixel.


I believe this is consistent with the latest web standards. If you think the standards say otherwise, we can definitely fix it.


- Dominic


On Thu, May 10, 2012 at 2:00 PM, Bryan Garaventa < <EMAIL REMOVED> > wrote:

That's alright, I often get the impression that I'm talking to myself...

----- Original Message ----- From: "Bryan Garaventa" < <EMAIL REMOVED> >
To: < <EMAIL REMOVED> >
Sent: Thursday, May 03, 2012 7:27 PM

Subject: Re: Regarding a Chrome bug for off-screen positioned active elements?



Does that mean there is a bug entered?


----- Original Message ----- From: "Ryan E. Benson" < <EMAIL REMOVED> >
To: < <EMAIL REMOVED> >
Sent: Thursday, May 03, 2012 5:39 PM
Subject: Re: Regarding a Chrome bug for off-screen positioned active elements?



Is this a known issue?

Yes it is, it has been mentioned here before. Not lately though.

--
Ryan E. Benson


On Thu, May 3, 2012 at 5:01 PM, Bryan Garaventa
< <EMAIL REMOVED> > wrote:

Hi,
I've recently discovered this behavior from a client, and it appears to be a
bug in Chrome. If you could help shed some light on this, it would be great.

So I've got a client side skip link implementation, the sample of which can
be seen at
http://whatsock.com/tmp/SkipLinkSample/demo.htm
and the source is available at
http://whatsock.com/tmp/SkipLinkSample.zip

The skip link is located at the top of the page so it is the first link in
the tab order, and is positioned off-screen to hide it visually.
Tabbing to the link will cause it to appear visually (via the :focus pseudo
class), and to disappear when focus moves away.
Pressing Enter on the link will set focus to the first heading on the page
(the H1 with tabindex="-1"), where tabbing will set focus to a link after
that point in the tab order.

This works perfectly in IE and FF, but not in Chrome. For some reason,
Chrome is detecting the off-screen styling and then removing the skip link
from the tab order entirely.

Also, when the skip link is activated from the keyboard (with CSS styling
removed to make it focusable again and with no screen reader running), focus
appears to be set to the first heading, but tabbing from that point moves
from the location of the skip link, and not from the heading that focus was
set to.

Is this a known issue?

Thanks,
Bryan


--
You received this message because you are subscribed to the Google Groups
"accessible" group.
To post to this group, send email to <EMAIL REMOVED> .
To unsubscribe from this group, send email to
accessible+ <EMAIL REMOVED> .
For more options, visit this group at
http://groups.google.com/group/accessible?hl=en.


--
You received this message because you are subscribed to the Google Groups "accessible" group.
To post to this group, send email to <EMAIL REMOVED> .
To unsubscribe from this group, send email to accessible+ <EMAIL REMOVED> .
For more options, visit this group at http://groups.google.com/group/accessible?hl=en.

--
You received this message because you are subscribed to the Google Groups "accessible" group.
To post to this group, send email to <EMAIL REMOVED> .
To unsubscribe from this group, send email to accessible+ <EMAIL REMOVED> .
For more options, visit this group at http://groups.google.com/group/accessible?hl=en.



--
You received this message because you are subscribed to the Google Groups "accessible" group.
To post to this group, send email to <EMAIL REMOVED> .
To unsubscribe from this group, send email to accessible+ <EMAIL REMOVED> .
For more options, visit this group at http://groups.google.com/group/accessible?hl=en.





--
You received this message because you are subscribed to the Google Groups "accessible" group.
To post to this group, send email to <EMAIL REMOVED> .
To unsubscribe from this group, send email to accessible+ <EMAIL REMOVED> .
For more options, visit this group at http://groups.google.com/group/accessible?hl=en.


--
You received this message because you are subscribed to the Google Groups "accessible" group.
To post to this group, send email to <EMAIL REMOVED> .
To unsubscribe from this group, send email to accessible+ <EMAIL REMOVED> .
For more options, visit this group at http://groups.google.com/group/accessible?hl=en.




--
You received this message because you are subscribed to the Google Groups "accessible" group.
To post to this group, send email to <EMAIL REMOVED> .
To unsubscribe from this group, send email to accessible+ <EMAIL REMOVED> .
For more options, visit this group at http://groups.google.com/group/accessible?hl=en.