IN wcag 2, a draft of 17th May of 2007 you can see:
ยป http://www.w3.org/TR/2007/WD-WCAG20-20070517/#consistent-behavior
Guideline 3.2 Make Web pages appear and operate in predictable ways
3.2.1 On Focus: When any component receives focus, it does not
initiate a change of context. (Level A)
#changes of context
change of:
1.user agent;
2.viewport;
3.focus;
4.content that changes the meaning of the Web page.
Note: A change of content is not always a change of context. Small
changes in content, such as an expanding outline or dynamic menu, do
not change the context.
#viewport
object in which the user agent presents content
Note 1: The user agent presents content through one or more
viewports. Viewports include windows, frames, loudspeakers, and
virtual magnifying glasses. A viewport may contain another viewport
(e.g., nested frames). User agent user interface controls such as
prompts, menus, and alerts are not viewports.
Note 2: This definition is based on User Agent Accessibility
Guidelines 1.0 Glossary.
I believe that force user to open in new window is force to change the
context. I think is more wise give to the user the chanse to choose
open or not open in new window.
And what we could do is get a way of make that job easier, and not
choose for the user.
On 19/07/07, Philip Kiff <[EMAIL PROTECTED]> wrote:
Joyce Evans wrote:
> I always thought it was a good idea to open links to other websites
> in a separate window, so you don't lose the visitor. [...]
I think that the weight of public opinion has been steadily turning against
this view over the past 10 years or so. I would be interested in knowing if
there is any current research that supports the theory that opening links in
new windows will somehow keep visitors interested in your site longer. Sure
it may keep them *stuck* there longer, but does that keep them *interested*?
My impression is that in 2007 the reverse is true.
There is certainly a considerable amount of anecdotal evidence that suggests
that for a certain percentage of web users, nothing infuriates them more
than forcing causing a new window to pop-up unexpectedly when you click on a
link. I personally now use a JavaScript snippet to strip all
target="_blank" entries from the DOM before rendering pages are rendered in
my browser.
From a web standards perspective, the argument against opening links in new
windows dates back to the very first W3C Web Content Accessibility
Guidelines (1999), if not before:
Guideline 10.1
Until user agents allow users to turn off spawned windows, do not cause
pop-ups or other windows to appear and do not change the current window
without informing the user. [Priority 2]
http://www.w3.org/TR/WAI-WEBCONTENT/#gl-interim-accessibility
See also, the WCAG "Techniques" document notes for 10.5:
http://www.w3.org/TR/WCAG10-HTML-TECHS/#no-new-windows
Lastly, if one really must spawn new windows with certain links, then I
quite like the method suggested by Bill Posters (note that this is
apparently still a Work In Progress):
http://test.newplasticarts.co.uk/dom-js/flag-toggle-external-links/
Phil.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
--
Make it simple for the people
------------------------------------------
http://www.artideias.com
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
