W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

Re: Page length and number of links

From: <deborah.kaplan@suberic.net>
Date: Fri, 21 Jun 2013 11:40:47 -0400 (EDT)
To: David Hilbert Poehlman <poehlman1@comcast.net>
cc: Jim Tobias <tobias@inclusive.com>, w3c-wai-ig@w3.org
Message-ID: <Pine.LNX.4.64.1306211138590.22290@suberic.net>
Particularly the problem is the way those pages scroll endlessly.
You can't click the back button and come back to where you were,
for example. A Twitter timeline begins at the start, and every
time you reach the bottom of the page more material is
dynamically added. But if you return to the page, you are back at
the top (or where the top is now). Moreover, all the links on the
page don't load into you get to the bottom of the page. (I'm
actually not sure how auto-loading pages like that interact with
screen readers. I assume that when the virtual cursor reaches the
bottom of the page, more data loads?)

It's really more of a usability problem, but it does fall into
that space between usability and accessibility.

On Fri, 21 Jun 2013, David Hilbert Poehlman wrote:

> I'm not sure what you mean re twitter although it is problematic in some ways, I can use it just fine on my mac and on iOS.
> As for long pages, I'd think that permitting structure would be extremely helpful.
> On Jun 21, 2013, at 11:30 AM, deborah.kaplan@suberic.net wrote:
> Though as WCAG in the accessibility community confront the
> dynamic web, their variance on this but I think we should be
> making recommendations about. Both long pages and short pages
> with links can be made to work for people, but I wonder what our
> recommendation from an accessibility standpoint should be about
> those pages which endlessly scroll using JavaScript, without
> anchors to particular places in the page, or the ability to use
> the back button to get back to where you were.
> I'm thinking of sites like Twitter and tumblr, which use
> JavaScript to make an endlessly scrolling page. The real
> difficulty with pages like those is a usability one, but from
> an accessibility standpoint I wonder what other people feel about
> them. The inability to return to a static point in a page can
> cause a lot of difficulties.
> -Deborah
> Deborah Kaplan
> Accessibility Team Co-Lead
> Dreamwidth Studios
> Jim Tobias wrote:
>> I hope that we agree that trying to nail this issue down once and for all, for all users, sites, and reasons for the
>> user to be at the site, is a hopeless cause.
Received on Friday, 21 June 2013 15:41:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:49 UTC