ARIA application name

Hi Glen, Rob

I followed up with the working group on whether to have an ARIA application
name.  This was quite a long discussion.

Initial discussions centered around whether the URL of the web page would
be adequate enough however it was agreed that the content could be reused
on different URLs. Another issue is the growing use of mashups. This is
where mashup servers fuse content from different service providers to
rapidly create a rich user experience. Examples of web services might be a
google search facility, a Google map, or a yahoo mail application. IBM has
a new technology it is developing on alphaWorks called QEDWiki where the
person who accesses the Wiki can create their own custom UI from the
various services and deploy something quickly. Given this, a number of us
like Jon Gunderson and I though we need the application name provision on
any object with the following roles: application, document, or region.

We do not if this granularity or the following proposal would address your
needs for customization but we would like you to review it and send it back
modified to the xtech list or Al Gilman for discussion.

Proposal:

Add the following properties which could be added to the roles of:
application, document, region.

templatename - which takes a URL as a property. This name is intended to be
unique although no formal service is provided to ensure its uniqueness. If
the markup is generated from a web service it is suggested that a URL
combining the SOAP host and script location be used. Otherwise all or a
portion of the URL could be used such as when using an IFrame to show the
content.

majversion - integer major version number
minversion - integer minor version number

It is assumed that the assistive technology would use this knowledge to
trigger user interface customization, for the templatename, to increase the
usability for a person with a disability.

Please respond to xtech and/or Al Gilman. I will be traveling starting
Thursday.

Cheers,
Rich



Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review  Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer