Re: adding type attribute to Canvas HTML DOM interface

On 12/22/11 11:38 AM, Benjamin Hawkes-Lewis wrote:
> On Thu, Dec 22, 2011 at 7:19 PM, Charles Pritchard<chuck@jumis.com>  wrote:
>> I do think this is an idea to investigate in ARIA 1.1. One may, with ARIA,
>> use multiple roles, and the AT will fall back to known roles.
>> So you can do something like role="game application".
> What could user agents (including AT) do differently for "game"?

In my private conversations with some vendors, games have been mentioned 
repeatedly as a special case.

I really don't have a good answer for this, I only have some 
brainstorming ideas.

There may be screen heuristics such as anti-flashing filters [to help 
with light sensitivity], it may be a helpful hint in signaling that an 
element can run in full screen. It may be a hint, in itself, that some 
part of the content is not accessible, because it would defeat the 
purpose of the game.

I think it's something that could be investigated in ARIA 1.1, but I 
don't have sufficient information to bring to the table at this point.

It's my personal belief that games can be made accessible, but that 
there are concerns about "cheating" and/or alternate game play styles. 
There was a great showing of people at the Seattle Accessibility Camp 
this year (2011), and I really enjoyed sitting in on a conversation 
about gaming and accessibility.
http://accessibilitycampseattle.org/blog/

One could look at the Zynga model where a game may be difficult to make 
accessible, and where that accessibility may be a means for 
circumventing the game dynamics by making it easier for programmers to 
create automated scripts. That's conjecture, too... But I'm trying to 
provide some thought on this discussion and conjecture is all I have at 
this point. That and some off-list conversations.



-Charles

Received on Thursday, 22 December 2011 19:47:31 UTC