- From: Shawn Henry <shawn@w3.org>
- Date: Thu, 28 Aug 2014 08:54:44 -0500
- To: Lee Robinson <nw36np@outlook.com>
- CC: EOWG <w3c-wai-eo@w3.org>
Hi Lee, A bit of context will help here. :-) The discussion is a follow up from an EOWG teleconference. The general issue of back button and returning to previous page is not relevant in this case. Instead, we're talking about steps in a multi-page application. This discussion is specifically about placement of the Previous and Next buttons in <http://w3c.github.io/wcag-em-report-tool/dist/#/audit/scope> (There are some concerns with right-aligning the Next button [1] and some support for it based on common practice.) Best, ~Shawn [1] e.g., http://lists.w3.org/Archives/Public/w3c-wai-ig/2014JulSep/0069.html On 8/28/2014 8:21 AM, Lee Robinson wrote: > Dear Group, there seems to be discussion of 'next' and 'previous' > buttons in this thread. An piece of advice, which seems to go way > back is "Don't break the back button" [on the Browser]. There seem to > be, in existence, sites which adhere to this, and it is found that > they are superior in terms of accessibility . Made terse, an > 'previous' button may be superfluous, or if used, might simply invoke > a JavaScript handler to return to the previous page? Lee. > >> Date: Wed, 27 Aug 2014 09:07:18 -0500 From: shawn@w3.org To: >> w3c-wai-eo@w3.org CC: w.fiers@accessibility.nl Subject: Re: Button >> research discussion >> >> On 8/26/2014 5:00 PM, Anna Belle Leiserson wrote: >>> Following up on Sharron's email to a different EO list (linked >>> here: >>> http://lists.w3..org/Archives/Public/wai-eo-editors/2014Aug/att-0003/00-part), > >>> >> I've been wading through the same set of articles. It's all so >> murky.. >>> (BTW, this is in re. where to put next/previous buttons on the >>> WCAG EM Report Tool >>> http://w3c.github.io/wcag-em-report-tool/dist/#/). >>> >>> I agree with Sharron's logic. And then using my gut and thinking >>> about a few big, popular commercial sites, I take it one step >>> further.... I wonder if the clearest thing might be having *only* >>> a Next button -- and align it on the left? (In other words, axe >>> the Previous button.) >>> >>> If it's important to have easy access to previous step(s) on >>> longer pages, right beneath the solo Next button the top progress >>> bar could be replicated. >> >> .oO good idea. What about having only the progress bar (not a Next >> button)? It might not be very pretty, but it seems *very much to >> support usability*. :-) Maybe even tweak the design down there to >> make the next step look even more clickable? >> >> ~Shawn >>
Received on Thursday, 28 August 2014 13:55:01 UTC