WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: query on the lazy loading


From: Birkir R. Gunnarsson
Date: Aug 25, 2021 5:31AM

Ideally, offer next/previous buttons to keep loading content, creates
consistency, predictability and works with the keyboard.
Screen reader only instructions differ between screen readers (how
they handle their virtual buffer navigation methods and scrolling) so
you may have to end up providing 2 or 3 sets of instructions depending
what screen readers people are using.
Maybe you can just present the intire page and visually hide the
portions of the page that scroll into view, though it could make for a
very large page.
Sadly, lazy loading just isn't a very good/usalbe/predictable
experience, but sometimes we have to go along and make the best of it.

On 8/25/21, suman damera < <EMAIL REMOVED> > wrote:
> Thank you Glen for your input.
> providing visually hidden text helps the user to navigate all the elements
> with the help of screen reader keyboard shortcut keys and kind of this
> problem is resolved. How about point 2 issue in the main thread?
> On Tue, Aug 24, 2021 at 7:12 PM glen walker < <EMAIL REMOVED> > wrote:
>> One option is to have visually hidden text that explains, upon the first
>> page load, that the user must go to the end of the page (Ctrl+End or
>> Cmd+DownArrow) to fully load the page before they navigate via screen
>> reader shortcut keys.
>> Another option is to let the user choose if they want lazy loading. You'd
>> probably need visually hidden text in this case too, explaining where the
>> "settings" dialog is so they can change the loading option.
>> Or a combination of the two. A message that says the page isn't fully
>> loaded until they scroll to the bottom and if they want to permanently
>> turn
>> off that feature, go to the settings dialog.
>> >> >> >> >>
> > > > >

Work hard. Have fun. Make history.