[games_access] WCAG and Games

[Sandra Uhling]

Hi,

I could write a document with examples why the WCAG does not
suit the needs of GA. But I do not want to waste on something this stupid.

E.g. (of course this is only an example, there is more behind it!)
WCAG: reduce everything to text (alternatively)
GA: easy description: sound <-> graphic

WCAG: possible to stop animation
GA: control over time (in different ways)

WCAG: make it accessible
GA: consider that there is still challenging

WCAG: make it barrier free (maybe this is only a German "term" problem?)
GA: make it accessible as possible 

WCAG: Web stuff (no web games)
GA: special GA stuff

WCAG: only mouse and only keyboard should be possible
GA: ... and reconfigurable control, added with changeable gamespeed,
difficulty
   .... AND we need to consider how the interface for AT has to look like!!!

When we would recommend the WCAG for Games, we would get
* angry and confused game designer
* angry and confused game developers
* boring games

The big problem is: yes we can use the WCAG, but ONLY when you know
about the special needs about GAMES! Games are not software!

The target group are game designers and game developers.
They usually do not know about the special GA needs!
They need and they have the RIGHT to get their own GA guideline!


One comment: the WCAG can become a rule!!!!!!!!!!!!!!!
(Do not forget the UN Convention CRPD!)


AT = Assistive Technology