- From: Brian Blakely <anewpage.media@gmail.com>
- Date: Tue, 8 Jul 2014 09:39:46 -0400
- To: Nils Dagsson Moskopp <nils@dieweltistgarnichtso.net>
- Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>, Ashley Gullen <ashley@scirra.com>
Keep in mind my suggestion doesn't take away something that once solved your use case, or even adequately upheld the philosophy of an accessible Web. It simply doesn't try to solve it, which is a different thing. On Mon, Jul 7, 2014 at 7:53 PM, Nils Dagsson Moskopp <nils@dieweltistgarnichtso.net> wrote: > "Brian M. Blakely" <anewpage.media@gmail.com> writes: > >> The use cases involved are mostly intended for 60fps high-load >> graphics, so the kind of a11y conditions served by the DOM (screen >> readers) aren't as helpful in these apps. I don't think the DOM makes >> videogames more accessible. The Web Platform doesn't serve that case >> well; it isn't something this is trying to solve. > > I think no one should ever optimize for inaccessible web content. > > In case you think otherwise: Would you elaborate why your wish to > display “60fps high-load graphics” on the web outweighs the needs of > people with old or non widely used hardware or software, people with > disabilities, software that has no optical sensory input (e.g. web > spiders) and all those of us users who want to zoom or select text? > > Consider the following: If web content is not accessible by default, > only a privileged class of users will be able to see and use it. We had > that scenario already when “web” developers used Flash for everything. > > -- > Nils Dagsson Moskopp // erlehmann > <http://dieweltistgarnichtso.net>
Received on Tuesday, 8 July 2014 13:40:36 UTC