W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 1998

Re: Guidelines

From: Al Gilman <asgilman@access.digex.net>
Date: Wed, 23 Sep 1998 16:14:16 -0400 (EDT)
Message-Id: <199809232014.QAA04703@access2.digex.net>
To: charlesn@sunrise.srl.rmit.edu.au (Charles McCathieNevile)
Cc: w3c-wai-gl@w3.org, jongund@staff.uiuc.edu (Jon Gunderson)
Both of these things raise questions about what we should expect
the page author to do as opposed to what the browser should do.

Jon Gunderson is going to raise this with the coordination group
based on things that came up in the UA telephone call.


to follow up on what Charles McCathieNevile said:

> There are two things that I am looking for
> Section C - good design practices ????
> prop: Ensure that pop-up windows or changes of window are notified to the 
> user before they occur.
> Non-visual users can be surprised, and thoroughly disoriented, to find 
> they are not where they expected to be. Visual users too are often 
> disoriented by the sudden appearance of pop-up windows, or having a page 
> opened in a new window and not being able to go back to where they have been.
> P2? P3?
> This had been discussed and I thought it was in there.
> Also, section a - ensuring all things degrade 
> Dynamic pages: 
> Guideline:
> Where important information is provided in a dynamic object (for example a
> javascript calculator) ensure that there is adequate notification that the
> object is dynamic. 
> technique: In the calculator example this may mean having a 
> text box which is changed, and whose default value is 'on calculation 
> your result will appear here'.
> Rationale: Assistive Technologies such as screen readers can read text
> which has changed, but the user needs to know where the dynamic object is
> before they can re-read it. Users will not necessarily know that a change
> has occurred. 
> Charles McCN
Received on Wednesday, 23 September 1998 16:13:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:27 UTC