[WSG] a WCAG 2.0 question

2009-03-12 Thread Glen Wallis
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

Re: [WSG] a WCAG 2.0 question

2009-03-12 Thread Patrick H. Lauke
Glen Wallis wrote: 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. *3.2.2 On Input:* Changing the setting of any user interface component does not automatically

Re: [WSG] a WCAG 2.0 question

2009-03-12 Thread Steven Faulkner
hi glenda, Changing the setting of any user interface component is changing some state in the control that will persist when the user is no longer interacting with it. So checking a checkbox or entering text into a text field changes its setting, but activating a link or a button does not.

Re: [WSG] a WCAG 2.0 question

2009-03-12 Thread Stuart Foulstone
No contradiction. WCAG 2.0 Recommendation is the normative document. Not all techniques can be used or would be effective in all situations. Therefore, any particular TECHNIQUE is not REQUIRED for conformance. That is to say, if you have some other technique that meets the WCAG

[WSG] Illinois Functional Web Accessibility Evaluator 1.0 Released!

2009-03-12 Thread Jon Gunderson
The Illinois Functional Web Accessibility Evaluator 1.0 (FAE) has been released with new and updated accessibility rules based on the iCITA Best Practices [1 to help web developers create HTML resources that are usable by people with disabilities. FAE is a free service provided by the University

RE: [WSG] a WCAG 2.0 question

2009-03-12 Thread Steve Green
It's not just screen readers that have problems with new windows. Every user group we have tested with has had problems. Screen reader users sometimes do not notice that the screen reader has announced the opening of a new window. Screen magnifier users frequently cannot tell that a new window

Re: [WSG] a WCAG 2.0 question

2009-03-12 Thread Jon Gunderson
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

RE: [WSG] a WCAG 2.0 question

2009-03-12 Thread Patrick Lauke
Jon Gunderson 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. But, as discussed, the requirement actually doesn't concern itself directly with links popping up new windows, but more things like the page all of a

RE: [WSG] a WCAG 2.0 question

2009-03-12 Thread michael.brockington
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 I would have to disagree with that. If the user actually

Re: [WSG] a WCAG 2.0 question

2009-03-12 Thread David Dorward
michael.brocking...@bt.com wrote: I would have to disagree with that. If the user actually _is_ aware that they are about to open a new window, then does the same again somewhere else on the page, or on another page, then they are going to be very confused to discover that only one window has

RE: [WSG] a WCAG 2.0 question

2009-03-12 Thread Chris F.A. Johnson
On Thu, 12 Mar 2009, michael.brocking...@bt.com wrote: 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. I