WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: query on the lazy loading

for

From: Jonathan Cohn
Date: Aug 28, 2021 3:49PM

Hello, it can all depend on the Symantic and non semantic nature of the elements in question for your widget and also the screen reader. I am assuming by widget that you are talking about 2 or more HTML elements that the screen reader and user would consider ass one functional unit. Generally, the ARIA Naming algorithm should be used for this type of element, but sometimes it doesn't work correctly.
Can you give an example page or pseudo markup with examples of what is being lost by the screen reader?

Best wishes,

Jonathan Cohn



> On Aug 25, 2021, at 23:09, suman damera < <EMAIL REMOVED> > wrote:
>
> Hi Glen,
> yes, I am talking about skipping the widgets on point 2 from the main
> thread. aria-hidden is not set to true and it is proper. even then, the few
> widgets are getting skipped during down arrow navigation. Once we navigate
> through the entire page with down arrow and then use the up arrow, the
> skipped widget is discoverable. this is the because of lazy loading only
> and i need to understand how to overcome this issue
>
> Thank you.
>
> On Thu, Aug 26, 2021 at 12:58 AM glen walker < <EMAIL REMOVED> > wrote:
>
>> By issue 2 do you mean some elements are skipped when you arrow down with
>> the screen reader? If you're talking about elements that are *not* part of
>> the lazy loading section in that they exist on the page, then the main
>> cause of elements being skipped is because aria-hidden is set to true. It
>> might be set on the element itself (which is easy to spot) or it might be
>> set on a parent element or higher ancestor element and that takes a little
>> more work to find. It's hard to say for sure without seeing the page
>> you're talking about.
>>
>> On Wed, Aug 25, 2021 at 4:42 AM 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?
>>>
>>>
>>>
>> >> >> >> >>
> > > >