EASI Archives

Equal Access to Software & Information: (distribution list)

EASI@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Alan Cantor <[log in to unmask]>
Reply To:
* EASI: Equal Access to Software & Information
Date:
Mon, 4 Nov 2002 13:40:35 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (16 lines)
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]

ATOM RSS1 RSS2