- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Fri, 3 May 2002 08:07:49 +0100 (BST)
- To: w3c-wai-ig@w3.org
> It is not a done deal for screen readers today because applications use > non-standard controls without appropriately taking care of that. And of Not just in HTML, but before that, designers always want to be different (although curiously, they often all want to be different in the same way!). That means that many are always going to re-implement controls. The most obvious cases of this in HTML are that no designer ever seems happy with the standard presentation of links, or with standard text formats, but people also feel a desperate need to modify other controls. Also, the recent odd man out on frames was effectively pointing out that the screen reader/browser combinations he used didn't actually provide a deep enough view of the document, so he was frustrated because he could neither see the whole of a scrollable region of the document, nor scroll that region. Something in that browser/AT combination has to look at the underlying document model in order to provide the text - I'm sure the AT doesn't use OCR techniques to take it off the screen.
Received on Friday, 3 May 2002 15:10:02 UTC