- From: Marti <marti@agassa.com>
- Date: Fri, 6 Oct 2000 10:12:30 -0400
- To: "Charles McCathieNevile" <charles@w3.org>
- Cc: "Web Content Accessibility Guidelines" <w3c-wai-gl@w3.org>
I have not checked this out with a full set of screen readers but it appears that JFW versions prior to 3.31 are a problem - I suppose it could be considered 'flicker', but somehow I always think of that as a graphics related condition. In this case it is a 'digital clock' that is updated with JavaScript. Marti ----- Original Message ----- From: "Charles McCathieNevile" <charles@w3.org> To: "Marti" <marti@agassa.com> Cc: "Web Content Accessibility Guidelines" <w3c-wai-gl@w3.org> Sent: Friday, October 06, 2000 8:57 AM Subject: Re: Clocks > This actually is the reason for 7.1 "Until user agents allow users to control > flickering, avoid causing the screen to flicker". > > Some information about what screenreaders (or other software) have problems > with this would be good... > > Charles McCN > > On Fri, 6 Oct 2000, Marti wrote: > > This probably falls under the current > "7.4 Until user agents provide the ability to stop the refresh, do not > create periodically auto-refreshing pages. " > But perhaps should be covered more specifically somewhere - > I recently encountered a web page that uses JavaScript to display a clock > that updates continuously. For slightly older screen readers this draws the > attention of the screen reader making it immpossible to get to the page > content. > Marti > > > > -- > Charles McCathieNevile mailto:charles@w3.org phone: +61 (0) 409 134 136 > W3C Web Accessibility Initiative http://www.w3.org/WAI > Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia > September - November 2000: > W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France > >
Received on Friday, 6 October 2000 09:58:12 UTC