WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: best practise to handle scrolling of text.

for

From: Isabel Holdsworth
Date: Dec 6, 2018 4:47AM

I wouldn't move the focus at all. If you were to move it to the first
newly visible item, how would users get back to where they came from?
By tabbing back through all of the items they just made invisible
when they scrolled the page down, thereby scrolling it back up again?

They could add a screenreader-only alert that says "Page scrolled
down" or something to that effect.

Cheers, Isabel

On 03/12/2018, <EMAIL REMOVED> < <EMAIL REMOVED> > wrote:
> All,
>
>
>
> I have just looked at a page. The developers were using aria-hidden to hide
> a scroll down button from screen reader users. Since the button was not in
> the accessibility tree. The focus would still land on the button. Jaws in
> Firefox 63 would read out the <ul> in full. A keyboard user would see where
> the focus was and could see how the content would scroll down.
>
>
>
> Firstly, I feel the aria-hidden should be removed altogether and the scoll
> down button is revealed. This brings to my question. What would be best
> practise when someone presses this scroll down button and is a screen
> reader
> user. Should the focus move to the first item which has been brought into
> the viewport which can be interactive with?
>
>
>
> Sean
>
>
>
> > > > >