- From: <accessys@smart.net>
- Date: Wed, 29 Apr 2015 13:31:36 -0400 (EDT)
- To: Wayne Dick <waynedick@knowbility.org>
- cc: Christophe Strobbe <strobbe@hdm-stuttgart.de>, Steve Faulkner <faulkner.steve@gmail.com>, "Batusic, Mario" <mario.batusic@fabasoft.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
certainly right about WAI carring the load without the resources. and seperate is never equal but those on the inside looking out have a far different perspective than those on the outside looking in Bob On Wed, 29 Apr 2015, Wayne Dick wrote: > Date: Wed, 29 Apr 2015 10:20:48 -0700 > From: Wayne Dick <waynedick@knowbility.org> > To: Christophe Strobbe <strobbe@hdm-stuttgart.de> > Cc: Steve Faulkner <faulkner.steve@gmail.com>, > "Batusic, Mario" <mario.batusic@fabasoft.com>, > "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org> > Subject: Re: Screen readers do not obey language changes in HTML > Resent-Date: Wed, 29 Apr 2015 17:21:16 +0000 > Resent-From: w3c-wai-ig@w3.org > > This issue is exactly what I have feared for years. We have one system for > able bodied users and an alternative system for people with disabilities. > >> From the US Supreme Court 1954, "separate educational facilities are > inherently unequal." The same is true of separate software service flow > models. > > APIs are essential, and ARIA is critical but they carry to heavy of a load. > It is really too difficult for AT and web developers to keep up. The > central focus for accessibility support should come from the HTML, CSS and > Javascript languages. > > I know a lot is being done, but to me WAI is carrying the weight of the > technical load with a tiny fraction of the resources. > > Please correct me if I am wrong. > > Wayne > > Wayne >
Received on Wednesday, 29 April 2015 17:32:16 UTC