Re: LasyLoad

hello: as a screen reader user i don't think the list idea would work at
all after  all lists have fixed numbers of items and when the screen reader
moves in to them they are told how many items so it gets some what
distracting to here list of 5 items when there might be 10 20 or more
items. . i do like the button that says load more  but don't make it
invisible  as then when the keyboard only user moves to it they will not
know ware they are. i find the way that twitter does it works for me i
don't find my self not getting the next load if i navigate with the twitter
keyboard shortcuts and not the screen reader. maybe a  spoken  alert if it
takes to long that says "loading more content " would be help  full. thanks
lucy

On Wed, Jul 1, 2015 at 7:37 AM, Mandana Eibegger <mandana@schoener.at>
wrote:

>  Hi
>
> how about including an extra button "load more items" after the last
> list-item? - this button could be made only visible if you tab to it.
> or some appropriate info-element at the end "loading more items - please
> wait"?
>
> @next loaded item: maybe don't append the new items to the old list, but
> generate a new list which you place below the old list(s)
>
> Mandana
>
>
> On 01/07/15 15:28, Batusic, Mario wrote:
>
>  Hi All,
>
>
>
> Lasy load - loading data chunk by chunk is the new art of shoing lists of
> large data collections such as of search results or posts. Both LinkedIn
> and Twitter use it. The screen reader users have currently following
> accessibility barriers where this technique is used:
>
> 1.      By fast tabbing the user reaches the last loaded link in the list
> and with the next tab the following contents coming beneath the list in the
> HTML code.
>
> 2.      The user has no possibility to find the next loaded item easily.
>
> 3.      Through these both problems the user is confused - this situation
> is somewhat similar to automatic scrolling where blind users are also "lost
> in space".
>
> 4.      One possibility to solve the problem I think would be the use of
> list widgets (aria role=listbox) where the developer can implement the
> keyboard properly and so overcome the loading patchwork. But in most
> situations there is more than a single link or text entry building a list
> item. A single search result for example could contain a header, a main
> link and possibly a paragraph of text following the header, witch could
> also contain one or more links. That is too much for a simple list widget
> entry (role=option).
>
> Can somebody help with a solution? Or do you think the lasyLoad cannot be
> made accessible? Thanks in advance.
>
> Mario
>
>
>
>
>


-- 
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces