WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Bypass blocks for a small website

for

From: Vaibhav Saraf
Date: Oct 6, 2020 11:45AM

Hi Birker,

A screen reader user will have multiple options given you have the heading
navigation, landmark navigation, tab and normal arrow key navigation on
such a page.

Consider the case for a keyboard user who lands in the middle of the page
all because auto-focus have to do a non-intuitive action of 7 Shift tabs to
log out of the site. What will be the usability impact in such a case? Do
shortcuts like Ctrl + Home work for a normal keyboard user as well?

Thanks,
Vaibhav





On Mon, 5 Oct 2020 at 21:04, Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:

> WCAG 2.4.1 only requires mechanisms to bypass block of content (one or
> more of a skip link, headings and ARIA landmarks).
> So technically if the page has one heading or landmark it would pass
> (in the case of one landmark it would be borderline pass since ARIA
> requires that all content on the page resides in a landmark region).
> In your case, yes, I would use landmark regions for head/main/footer
> and leave focus at the top of the page when it loads (the only
> possible expceiotn being if there is a login page you may want to
> autofocus the username or the first input).
> The skip link is probably a good idea. For me, I use 10 tab stops as a
> rule of thumb indicator how important it is, but I generally recommend
> a global skip link on websites, even with as few as 5 tab stops.
>
>
>
> On 10/5/20, Anna Lewis < <EMAIL REMOVED> > wrote:
> > Hello,
> >
> > I'm not sure how I got added to this list. Can you please remove me?
> >
> > Thank you,
> > Anna
> >
> > On Mon, Oct 5, 2020 at 8:19 AM < <EMAIL REMOVED> >
> wrote:
> >
> >> And additionally to the skip link make sure that the main section is
> >> really
> >> a <main> section and starts with an H1. These features also support
> >> efficient navigation with screen readers. And they are a small effort on
> >> a
> >> small page.
> >>
> >>
> >>