Are w3c Standards Only for windows Sites-and-users?

Eric Oyen eric.oyen at
Tue Jun 17 06:05:21 UTC 2014

this is one of the reasons why accessibility for the blind on the net is so hit & miss. The W3C is attempting to standardize this in HTML 5 so that the code can be browser independent. Believe me, this would be far better for us blind users. THings like accessible controls on multimedia streaming, properly labeled buttons, text fields and other screen elements would make browsing almost a snap for us (regardless of the browser used).

The problem is that there are several multinationals (such as Microsoft) that are trying to get these items exluded. As far as I am concerned, this is unacceptable.

This is the problem with HTML 4. There is no standards for code and that is what hurts us the most.

anyway, that is my two cents worth on it.


On Jun 16, 2014, at 9:18 AM, John G. Heim wrote:

> But access for all  doesn't mean a web site has to support all browsers. You have a right to use whatever browser yu like but a web site doesn't have to work with your choice of browser.  By no means do I mean to criticize your decision to stick with speakup and lynx but that's a decision you've made. You can't expect web sites to accomodate your decision.
> Notethat what I say above is not the same (logically) as saying that it's okay for web designers to write for specific browsers. That's not what I am saying and logically, it's not the same thing. As a practical matter, your choice of browser and screen reader will always be limited by the technical issues involved with making sites accessible. Web designers have a right to code their sites for browsers that are kept up to date technically.
> On 06/13/2014 11:23 PM, Hart Larry wrote:
>> Wow, I suppose we in Linux may need our own version of a Civil Rights Bill. HEheHEheHEheHE
>> Ther is a large Grocery chain which was involved in a settlement-and-just upgraded, or supposedly made its site accessible to all shoppers.
>> Until March of 2010 I was able to shop this site in Linux, maybe not perfect, but if I were careful I filled out everything fine. Beginning in April 2010, no matter which Linux browser or JAWS I couldn't shop any more. In their separate access site, their help FAQ said they did not use any complicated scripting such as javascript or css, however, in the source-code, there they were.
>> Well, now April 30 has come-and-gone, I still cannot shop in either L Y N X or E L I N K S. When shopping by eile I notice items in a catagory, but none of them have any links to add to my cart.
>> So today intouch with a CSR, who found it, I can try chrome vox or fire vox. I tried looking for these with an "apt-get" in Debian, cannot find. Are these only for graphical browsers such as in an x11 display?
>> I was told that w3c requirements may give them choices of either html, javascript, or css?
>> So if they are permitted to write a site which would not work for many users, if they were picking 2 of those 3 choices, how is that access for all?
>> So many times especially during the last 2years, an onis is always on myself to possibly run windows  or maybe ask asistance of some1 running a graphical setup.
>>> From what I hear, L Y N X will maybe never have javascript support.
>> So what happens next? If indeede the standards give site owners leeway in leaving out a group of users, as well as a potential revenue loss. Or even worse, what happens if they drop delivery because of lack of shoppers?
>> Thanks alot for listening-and-I welcom all of your ideas-and-suggestions.
>> I did try Orca many years ago but it was `quite slow, but also even in Speakup in software speech, the volume was lo in I B M tts. I am running Speakup with a DecTalk U S B.
>> Hart
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list at
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at

More information about the Blinux-list mailing list