- From: Charles McCathieNevile <charles@w3.org>
- Date: Tue, 3 Dec 2002 20:12:55 -0500 (EST)
- To: Ines Robbers <robbers@comprehend.de>
- cc: <w3c-wai-gl@w3.org>
On Tue, 3 Dec 2002, Ines Robbers wrote: >Under Checkpoint 3.5 the following is suggested: > ><q>Example 1: a form to deactivate pop-up windows. >A checkbox is provided on a page of links to let the user select whether >they want the resultant pages to appear in new windows or not.</q> > >Does this also refer to target="blank" or just to the javascript pop-up >functions? >Has there been a solution developed yet? CMN This can be implmented by the website that takes the information and uses some tracking mechanism (paralell URIs, cookies, all manner of appraoches) to serve pages that don't cause pop-ups. I don't think it is a very valuable area of research and development - many browsers already provide the ability to suppress pop-up windows. But it should certainly apply to any technique that creates a new indow - scripting, target attributes, etc. IR >In the second example it is written: > ><q>Example 2: a warning given before a pop-up window. >At the end of a news story, several links are provided for more >information. At the beginning of each link is an icon of an arrow with >the text equivalent, "Link will open in new window."</q> > >I have tried this out and it can look a bit icon overloaded. In cases of >link lists would it not be sufficient to do something like this: > ><p><img src="img/extlink.gif" alt="Links will open in new window."/>All >links of the following collection will open in a new browser window.</p> CMN No, because many people still just browse the list of links and so would miss this. Ideally their browser will tell them and you don't need to, but otherwise adding (new window) to each link is the nly way to be sure. This is helpful not just for people who are blind, so please don't make it invisible. IR >One more comment with regards to Checkpoint 4.3 I would like to make: > ><q>acronyms and abbreviations are defined the first time they >appear.</q> > >Does this relate to the single document or the whole website? >In the latter case - is it not rather difficult on a website to >determine where there is a "first time" since we are confronted not with >linearity but hypertext? >It might be more understandable to some to clarify this point. CMN For the reasons you point out it should be in each document. (In my opinion it should be every time - it doesn't take much if you use an automatd tool, and if you don't this is already really ahrd to do).
Received on Tuesday, 3 December 2002 20:12:57 UTC