First and foremost, I am not attacking you personally, though I am most certainly responding to what I read in your posts on this subject. For example, on this latest post ... The fact that you can read something with JAWS or whatever screen reader proves precious little about the accessibility of the web page. Or, do you think accessibility is only for blind people using screen readers? I have news for you. There are other people with disabilities other than visual ones who are also comprehended in the WAI guidelines. So, please, let's not add self-centerdness to the lists of sins to untangle in this thread. As to the earlier issue, the matter of what tagging might or might not be appropriate, may I say that I do not regard it appropriate to recommend any old approach neither on this list nor anywhere else. This is not a contest to see who can think up more answers. I would ask you, as I ask myself and all others, to apply a little judgement to the advice offered here. All possible answers are not equal. Some are better than others. And there are legitimate reasons why some are better than others. So, in my mind I come back to the need for accessible markup on web pages. As blind (and otherwise disabled) users of the web, markup determines whether or not we participate. I cannot imagine a more fundamental principle of judgement than to insist that we practice what we preach about accessibility. By the way, the <pre> tag is not outdated. It has a purpose and should be used for that purpose and not suborned. Sina Bahram writes: > From: "Sina Bahram" <sbahram at nc.rr.com> > > Woh now. I never said anything about my advice being absolute or for > that matter even correct. In the nature of this list, a friendly forum > of knowledgable contribution, I attempted to offer a possible solution > among many. I never once stated mine was right, nor did I state that my > advice should be taken as anything but a suggestion. I also warned > against the bad practice of the pre elements; however, I offered one > possible solution to the problem. I will not get into an argument with > someone I have every other reason to respect over an outdated html tag > that I care little about; however, I would state that the accessibility > issues with using this command are not as grave as you may think as I > can prove with Jaws or IBM Home Page Reader each of which support and > read text in pre element tags just fine. I also thought that people were > encouraged to contribute advice so that we all may learn, apparently I > was wrong. The point of this list seems to be to offer advice so that it > may be rudely and negligently pushed aside with little regard for the > intentions behind that advice. I apologize if you do not agree with my > advice; however, I believe you could of phrased your email in a more > respectful manner. > > Also as to ignorance, I resent that accusation, simply because I always > stand to be corrected, as anyone should; however, the advice I gave has > worked with a number of different accessibility options. And as I > recommended it for a quick dirty fix, for example for a few days until > propper html may be written. I do not see the harm in the advice or the > necessity for your brrunt and uncalled for manner. > > Again I apologize if I have afended or said anything inappropriate, but > I don't believe I or Luke, along with Alex deserves such treatment. > > Take care, > Sina > > -----Original Message----- > From: speakup-admin at braille.uwo.ca [mailto:speakup-admin at braille.uwo.ca] > On Behalf Of Janina Sajka > Sent: Monday, August 25, 2003 7:38 PM > To: speakup at braille.uwo.ca > Subject: Re: text to html > > > Not very good advice, Sina. > > let's not go around inventing this stuff out of ignorance. There are > some pretty clear guidelines about what constitutes accessible HTML at > http://www.w3.org/wai. I suggest that meeting those guidelines needs to > be a priority. > > Let me make it real clear. We talk about accessibility here on this > list. We must give as we expect to receive. > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Janina Sajka, Director Technology Research and Development Governmental Relations Group American Foundation for the Blind (AFB) Email: janina at afb.net Phone: (202) 408-8175
