- From: Emmanuelle Gutiérrez y Restrepo <emmanuelle@retemail.es>
- Date: Sat, 7 Oct 2000 12:45:31 +0200
- To: "Charles McCathieNevile" <charles@w3.org>, "Marti" <marti@agassa.com>
- Cc: "Web Content Accessibility Guidelines" <w3c-wai-gl@w3.org>
Hi, An example is TIFLOWIN, screen reader developed by ONCE (http://cidat.once.es/uttseccion.cfm?seccion2=10) for the Spanish blinds. Regards, Emmanuelle Gutiérrez y Restrepo mailto:coordina@sidar.org http://www.sidar.org/anima.htm -----Mensaje original----- De: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org]En nombre de Charles McCathieNevile Enviado el: viernes, 06 de octubre de 2000 14:57 Para: Marti CC: Web Content Accessibility Guidelines Asunto: 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 Saturday, 7 October 2000 06:47:16 UTC