- From: Gregory J. Rosmaita <oedipus@hicom.net>
- Date: Wed, 26 Sep 2007 21:51:16 -0400
- To: Marghanita da Cruz <marghanita@ramin.com.au>
- Cc: Maciej Stachowiak <mjs@apple.com>, public-html@w3.org
aloha, marghanita! there are many excellent internal (W3C) resources to assist you in fleshing out the final phrase of your counter-proposal and in gaining a better understanding of how assistive technologies work with web technologies, amongst which are: 1. Accessibility Features of HTML4 * http://www.w3.org/WAI/References/HTML4-access also: * http://www.w3.org/TR/CSS-access.html/ 2. Components of Web Accessibility: * http://www.w3.org/WAI/intro/components.php 3. Alternative Web Browsing * http://www.w3.org/WAI/References/Browsing i have attempted to collect such material in the HTML wiki page located at: http://esw.w3.org/topic/HTML/AccessibilityDependencies gregory. ------------------------------------------------------ It is better to ask some of the questions than to know all the answers. -- James Thurber ------------------------------------------------------ Gregory J. Rosmaita, oedipus@hicom.net Camera Obscura: http://www.hicom.net/~oedipus Oedipus' Online Complex: http://my.opera.com/oedipus ------------------------------------------------------ ---------- Original Message ----------- From: Marghanita da Cruz <marghanita@ramin.com.au> To: "Gregory J. Rosmaita" <oedipus@hicom.net> Cc: Maciej Stachowiak <mjs@apple.com>, public-html@w3.org Sent: Thu, 27 Sep 2007 08:41:43 +1000 Subject: Re: HDP: Revised "Support Existing Content" Principle > Gregory J. Rosmaita wrote: > > aloha, maciej! > <snip> > > here is my proposed text again: > > > > "Browsers should retain support for residual/legacy markup designed for > > a specific purpose, such as accessibility. internationalization or device > > independence. Simply because new technologies and superior mechanisms > > have been identified, not all of them have been implemented. Moreover, > > disabled users are more likely to be users of "legacy technology" because > > it is the only technology that interacts correctly with third-party > > assistive technologies." > <snip> > > I am not familiar with Assistive Technologies and from this > paragraph am unsure whether there is markup aimed specifically > at Assistive Technologies or whether the way a browser > interprets markup enables assistive technologies. > > However, I think I get the intent of covering this under the > "Supporting Existing (pre-HTML5) Content Principle" but > wondered if rephrasing it along the following lines would be > more consistent with the principles document. > > "Some/Many Webpages include of markup which needs to be > interpreted in a specific way by Browsers (or directs browsers > to behave in a particular way), to enable the page to be > translated/interpreted correctly by Assistive Technologies such > as screen readers. Examples of such markup are...." > > Marghanita > -- > Marghanita da Cruz > http://www.ramin.com.au > Phone: (+61)0414 869202 ------- End of Original Message -------
Received on Thursday, 27 September 2007 01:51:35 UTC