[games_access] Top 3 Top 3 and IGDA GASIG Awards Ceremony 2008

Barrie Ellis barrie.ellis at oneswitch.org.uk
Sun Dec 2 15:46:26 EST 2007


Hi Reid,

Thanks for your suggestions. I appreciate the point that some access
features are harder than they first seem to implement. But there definitely
are easy to add features for specific genres. Quickly:

a. Driving games - imagine OutRun - adding wider difficulty level adjustment
such as much more generous time limits to complete a stage is very easy.
b. Pinball games - allowing for adjustment in ball speed as a menu option
seems pretty straight forward to me.
c. Golf games - allowing an Easy Play option whereby hook and slice can be
turned off also sounds very easy to me.

Maybe the Extra Suggestions part is confusing the original message. These
are intended to show some ways devleopers can stretch out and go a bit
futher with that type of accessibility.

I wouldn't want us to scare off developers by saying there are no "easy"
accessibility features for developers to add. I really don't believe it. If
Atari could do it regularly for the Atari 2600 in the early 1980's...

2. If it's really that contentious, I'll change it - but "3 most requested"
isn't bullet proof either.

3. Why don't we make a Top 3 Most Requested Accessibility Features for each
disability area? Sounds like a good idea to me...

Barrie



----- Original Message -----
From: "Reid Kimball" <reid at rbkdesign.com>
To: "IGDA Games Accessibility SIG Mailing List" <games_access at igda.org>
Sent: Sunday, December 02, 2007 8:07 PM
Subject: Re: [games_access] Top 3 Top 3 and IGDA GASIG Awards Ceremony 2008



> Hi Barrie,

>

> I like what you have but do have a couple suggestions.

>

> 1) I agree with Richard, there are no "easy" accessibility features

> for developers to add. I have said that adding closed captioning to

> games is easier than a physics or rendering system and it is true, but

> creating the captioning system itself presents tricky design problems

> and depending on the sound engine, maybe even technical issues. In

> general, I don't think we have the right to designate whether an

> accessibility feature is easy or not for a developer to implement. How

> hard it is will depend on the developers technology foundation and

> programming/designing talent they have.

>

> 2) On the contention of Top 3, why not slightly change the wording so

> it's Top 3 Most Requested Accessibility Features.

>

> 3) Why don't we make a Top 3 Most Requested Accessibility Features for

> each disability area. Richard can submit a list of his top 3 for

> blind/visually impaired, I'll submit mine for hard of hearing/deaf and

> so on.

>

> -Reid

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seven.pairlist.net/pipermail/games_access/attachments/20071202/c8d611aa/attachment.htm>


More information about the games_access mailing list