WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Bypass blocks for a small website

for

From: Vaibhav Saraf
Date: Oct 5, 2020 5:17AM

Hi Patrick,

Thanks for the suggestion. I understand your concern regarding the
auto-focus in this case and will surely take it up in my team.

Thanks,
Vaibhav


On Mon, 5 Oct 2020 at 16:23, Patrick H. Lauke < <EMAIL REMOVED> >
wrote:

> 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
> > > > >