- From: Gregory J. Rosmaita <oedipus@hicom.net>
- Date: Wed, 9 Dec 2009 16:43:35 +0000
- To: Henri Sivonen <hsivonen@iki.fi>, public-xhtml2@w3.org, w3c-wai-pf@w3.org
henri wrote, quote:
> Since the PFWG is chartered to work on accessibility matters, it
> seems inappropriate to publish a spec about non-accessibility
> uses of role through the PFWG.
unquote
Role IS an "accessibility matter" -- whether role info is used by an
assistive technology or not... that Role has broader implications
than "simply" accessibility does not preclude PF from taking up the
Role Module, especially since an effort is being made to include
members of many W3C groups who have had input to the Role module as
editors, as well as members of the PFWG... i have simply proposed
that PFWG take a leadership role in the promulgation of Role as a
cross-dialect aspect of web content, because Role information is
so very necessary to true accessibility and because it can help
make some sense out of template-served content which is stuffed
into a generic SPAN or DIV
if not PFWG, then who, henri? WAI work is a sub- or super-set of
basic usability and human-computer-interaction, not an overlay
or add-on -- accessibility and usability are inseparable aspects of
any architecture, programmatic or otherwise...
gregory.
-----------------------------------------------------------------
Accessibility, Internationalization, and Interoperability are not
"features", "overlays" or "add-ons". Rather, they are core
components of any architecture -- programmatic or otherwise.
-----------------------------------------------------------------
Gregory J. Rosmaita, gregory@linux-foundation.org
Vice-Chair, WebMaster & Listmaster, Open Accessibility Workgroup
http://a11y.org/ http://a11y/specs
-----------------------------------------------------------------
Received on Wednesday, 9 December 2009 16:44:10 UTC