W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2000

accessibility barrier.

From: Steven McCaffrey <smccaffr@MAIL.NYSED.GOV>
Date: Thu, 13 Jul 2000 12:02:47 -0400
Message-Id: <s96daff7.057@mail.nysed.gov>
To: <w3c-wai-ig@w3.org>

(I meant to post this to the list.
Sory melinda, I had mispelled your name)

Hi Malinda:

     I have been thinking about XML/XHTML issues lately, and given the wide disparity in support by browsers both for the language itself and the associated stylesheets, I am wondering about a possible "if all else fails" option.  I'd like to hear what others on this list have to say about my very tentative proposal.
    The advantage of both XHTML and XML is, of course, that the
developer can create her own tags which are semantic tags.  strikethrough is a kind of visual presentation. 
 If the source Xhtml file(file.xhtml) was made available, Lynx for example, would display the source.  So, if you had bills, with appropriate tags (I don't know what they are, so I'll use a simple generic example)
<billntype> Phone Bill </billtype>
<companyname> AT&T</companyname>
<Amountdue> $50.00 </amountdue>
Perhaps <amountdue> would have a stylesheet applied to it in such a way as to be displayed visually in strikethrough text.  Since the markup is there, and if I knew what the tag was named (e.g. <amountdue) and all my bills had <amountdue>, I could search for <amountdue> tags with the 
browser's search command.
Is this a viable "If all else fails" accessibility option?

Steve McCaffrey
Senior Programmer/Analyst
Information Technology Services
New York State Department of Education
New York State Workgroup on Accessibility to Information Technology 
Web Design Subcommittee 
Received on Thursday, 13 July 2000 12:05:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:35:57 UTC