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.
> >>
> >>
> >> -----Original Message-----
> >> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> >> Patrick H. Lauke
> >> Sent: Monday, October 5, 2020 12:54 PM
> >> To: <EMAIL REMOVED>
> >> Subject: Re: [WebAIM] Bypass blocks for a small website
> >>
> >> On 05/10/2020 11:33, Vaibhav Saraf wrote:
> >> > Hi Everyone,
> >> >
> >> > We are working on a small website having 5 main pages. When a user is
> >> > on any page on the website the focus is managed to take him/her
> >> > directly to the main section of the page.
> >> >
> >> > If the user moves to the top of the webpage, he/she will need to go
> >> > through
> >> > 7 tab strokes (2 in header & 5 in navigation bar) to reach the main
> >> > section.
> >> >
> >> > In such a case does it become mandatory to provide a bypass mechanism
> >> > to the main content? How will it change if the on page load user is at
> >> > the top of the page and not in the main content?
> >>
> >> I would actually say that it's not really ideal to auto-focus/yank the
> >> focus
> >> to the main part of the page on load. Users may not be aware/know that
> >> this
> >> happened, and may completely miss the content that came before the bit
> >> where
> >> you forced their focus to be on load. So I'd recommend removing this.
> And
> >> then yes, add a simple skip link to allow user to jump directly to the
> >> main
> >> content.
> >>
> >> P
> >> --
> >> Patrick H. Lauke
> >>
> >> https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> >> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> >> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> >> > >> > archives
> >> at
> >> http://webaim.org/discussion/archives
> >> > >>
> >> > >> > >> > >> > >>
> >
> >
> > --
> > Anna Lewis RN, BSN
> > (913) 424-7531
> > <EMAIL REMOVED>
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >