- From: david poehlman <david.poehlman@handsontechnologeyes.com>
- Date: Mon, 4 Apr 2005 08:01:31 -0400
- To: "wai-ig list" <w3c-wai-ig@w3.org>
Further complicating things is the fact that the line between user agent as rendering agent and screen reader as rendering agent in the case of windows with internet explorer, is blurring as the screen reader takes over more of the load of presentation. For embossing, you have often duxburry as an intermediary between the user agent and the embosser and duxburry has its own set of rules for translating/formatting based on rules set forth by the various braille authorities. e already have a template for duxburry to braille the web in dbt 10.5. I am not certain then what is gained by an emboss media type. -- Johnnie Apple Seed ----- Original Message ----- From: "Alastair Campbell" <ac@nomensa.com> To: "david poehlman" <david.poehlman@handsontechnologeyes.com> Cc: "Charles McCathieNevile" <charles@sidar.org>; "Emmanuelle Gutiérrez y Restrepo" <coordina@sidar.org>; <w3c-wai-ig@w3.org> Sent: Monday, April 04, 2005 4:20 AM Subject: Re: Braille style sheets david poehlman wrote: > if you > use a screen reader for windows that supports braille, the screen reader > decides what the braille display will render. There seems to be a fairly complex set of user agent responsibilities going on in this case. The braille hardware connects to the access software (e.g. a screen reader), which sits on top of the OS, using a (probably) mainstream browser. Which one should pick up the different media types? Presumably, if the browser/OS do not, then the access software would have a difficult time using them? Kind regards, -Alastair -- Alastair Campbell | Director of Research & Development Please refer to the following disclaimer for this message: http://www.nomensa.com/email-disclaimer.html
Received on Monday, 4 April 2005 12:01:37 UTC