WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Hidden headings with aria-labelledby or just aria-label best for for labelling landmark regions?

for

From: glen walker
Date: Jul 25, 2018 11:54AM

Good stuff, Jim.

Jonathan, you sort of answered your own question when you pointed out the
focus moving with skip links. You definitely want the focus to move to the
skip link destination. Whether that new focus results in a visual outline
or some other visual clue is more of a nicety *if* the focus is going to a
non-interactive element (such as a heading). If the focus moves to an
interactive object, then obviously a visible focus is necessary (2.4.7).
WebAIM chose to highlight the area that receives the skip link focus, which
I personally like and is a nice touch, but is not a conformance
requirement. However, if the skip link code just scrolls the page and
doesn't really move the focus, then my next TAB key will move the focus to
whatever interactive object was after the skip link. That's confusing and
I feel is a violation of 2.1.1 or possibly 2.4.3.

Also keep in mind that Internet Explorer will not move the focus to a
non-interactive element unless that element has tabindex="-1". I think
that's still the case and is documented on the microsoft site somewhere but
I don't have a reference to it offhand.

On Wed, Jul 25, 2018 at 11:36 AM, Jim Homme < <EMAIL REMOVED> >
wrote:

>
> I feel that skip links should be visible when someone tabs onto them, but
> do not necessarily have to be visible when focus is somewhere else. It's
> probably more friendly to the user to know they are there when focus is
> somewhere else. I feel that it is OK to compromise and let them be
> invisible. The important thing is that they are preferable first in the
> HTML order.
>
> Another consideration for people with motor and visual disabilities is to
> avoid changing the natural tab order. This helps people with disabilities
> with a predictable focus order. I've seen instances in which pages with
> forms try to help the user and change tab index so that the form fields are
> first in the tab order, but as a developer, I would think that you can't
> always predict what the user will do. And it's easy to get tab order
> incorrect.
>
> Thanks.
>
> Jim
>
>
>