Subject: | |
From: | |
Reply To: | * EASI: Equal Access to Software & Information |
Date: | Mon, 4 Nov 2002 16:30:56 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
just take me back to the page with helpful information to guide me
toward solving my problem if that is the case. otherly, go to a new
page. java script won't even be triggered by many browsers hense their
value is nill there anyway. inform means let me know so I can decide
whether or not I want to look.
----- Original Message -----
From: "Alan Cantor" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, November 04, 2002 1:40 PM
Subject: What is the problem with accessible pop-up windows?
I have a question about WCAG 1.0:
10.1: Until user agents allow users to turn off spawned windows, do not
cause pop-up or other windows to appear and do not change the current
window without informing the user.
What problems are there with operating-system produced pop-up windows?
Let's say a user enters data onto a form on a web-based application. The
use hits the submit button, the data is validated, and is found to
contain an error. If javascript pops an error message, there will be
accessibility problems. But if Windows draws a dialog box to report the
error (with an appropriate title bar, message text, and standard
pushbuttons) is this a problem? What techniques are more accessible than
an accessible pop-up window?
Alan
Alan Cantor
Project Manager
Strategic e-Government Implementation
e-Government, OCCS
416-212-1152
[log in to unmask]
|
|
|