- From: <deborah.kaplan@suberic.net>
- Date: Fri, 21 Jun 2013 11:38:36 -0400 (EDT)
- To: Jim Tobias <tobias@inclusive.com>
- cc: w3c-wai-ig@w3.org
Ugh, usually I proofread my Dragon wackiness before I send emails. I'm not even sure what that first couple of sentences was trying to say. Sorry, folks. I think it was about how we should be paying more attention to the dynamic web. *fails at dictation today* On Fri, 21 Jun 2013, 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:39:03 UTC