I think this requirement is a little out dated, screen readers today
do a good job of telling people that a new window is open.

I think the main concern is window pollution, if links are opening a
lot of "new" windows it can be difficult for people with some types of
disabilities to be aware of and find windows they are interested in.

I believe a best practice is for your web pages to use the same TARGET
attribute value so links from your page basically are updating the
same "new" window and not creating a new window for every link
followed from your website.

Jon


On Thu, Mar 12, 2009 at 1:58 AM, Glen Wallis
<glen.wal...@velocitynet.com.au> wrote:
> Hello all
>
>
>
> I am interested to know whether the people on this list consider opening a
> new window without alerting the user to be a failure to conform to Success
> Criterion 3.2.2 of WCAG 2.0.
>
>
>
> The success criterion is as follows:
>
>
>
> 3.2.2 On Input: Changing the setting of any user interface component does
> not automatically cause a change of context unless the user has been advised
> of the behaviour before using the component. (Level A)
>
> The key phrases, I believe are “user interface component” and “change of
> context”. I looked up the definitions of both phrases. The glossary states
> quite clearly that a link is a user interface component and that a change of
> context includes opening a new window. However, the document “Understanding
> SC 3.2.2” says
>
> “Additional Techniques (Advisory) for 3.2.2
>
> Although not required for conformance, the following additional techniques
> should be considered in order to make content more accessible. Not all
> techniques can be used or would be effective in all situations.
>
> Giving users advanced warning when opening a new window. (future link)”
>
> This seems like a contradiction. The WCAG 2.0 Recommendation is the only
> normative document, so it should take precedence over the Understanding
> document. However, the Understanding document specifically states that
> warning the user is not required for conformance.
>
>
>
> *******************************************************************
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> *******************************************************************


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************

Reply via email to