Naming review for "Roadmap" documents

This table is prepared as a worksheet for considering the naming of the documents that we seek to make First Public Working Draft in the near futhre that fall within what we have called our "roadmap" area of work.

We have to negotiate the short names with the Director or particularly with the Webmaster who is his agent in this.  We also have to consider input from EO and the Domain who have an interest that we project a message that the public can relate to.  Here are the existing things we have said that are candidate thumbnail and shorter descriptions of the three documents, along with a few starter suggestions for short names for use on the TR page.

Document 1: Roadmap

Current Title: Dynamic Accessible Web Content Roadmap
Current Subtitle: (none)

Abstract (in document): The Dynamic Accessible Web Content Roadmap addresses the accessibility of dynamic web content for people with disabilities. The roadmap outlines the technoloiges to map controls and events to accessibility APIs, including custom controls. The roadmap also outlines new navigation techniques to mark common web structues as menus, primary content, secondard content, banner information and other types of web structures. These new technoloiges can be used to improve the accessibility and usability of web resources by people with disabilities, without extensive modification to existing libraries of web resources.

Trailer (in PF public home page): This roadmap that describes the problem, what W3C specifications will be used to correct the problem, and the timeline for the new specifications.

Filename Now: DHTMLRoadmapmmddyy.html

Short Name Options:
  1. DHTML = Dynamic HTML
  2. aaa-plan = accessible, adaptable applications - plan
  3. ARIA = Accessible Rich Internet Applications


Dated Name Consequences:
  1. WD-DHTML-yyyymmdd
  2. WD-aaa-plan-yyyymmdd
  3. WD-ARIA-yyyymmdd

Document 2: Roles

Current Title: Role Taxonomy for Accessible Adaptable Applications
Current Subtitle: An [RDF] Role Taxonomy with [Qname] Support for Accessible Adaptable [XML] Applications

Abstract (in document): This specification provides designers with extra semantic role information that make user interfaces more usable and accessible.

The goal is to make static and interactive content of Web pages more usable and accessible to their users and their assistive technologies. This goal is achieved by providing a cross-platform role model for dynamic Web content that allows for content adaptations based on role information. The result is to provide an interoperable way for associating behaviors with document-level markup.

The attributes defined in this specification provide XML languages with the ability to add extra information about the behavior of an element. States and Adaptable Properties are mapped to accessibility frameworks (such as a screen reader) that use this information to provide alternative access solutions. Similarly state and author properties can be used to dynamically change the rendering of content using different style sheet properties. The result is to provide an interoperable way for associating behaviors with document-level markup.

Trailer (in PF public home page): This specification defines an RDF taxonomy of roles which describe custom GUI widgets and document structure which may be used to support platform accessibility APIs. Roles encapsulate semantic information which may be use to help: user agents support assistive technologies; authoring tools enforce accessibility, and assistive technologies discover new custom objects and how to interoperate with them.

Filename Now: roleTaxonomy-yyyymmdd.html

Short Name Options: wairole

Dated Name Consequences: WD-wairole-yyyymmdd

Document 3: States & Adaptable Properties

Current Title: States and Adaptable Properties Module
Current Subtitle: A Syntax for adding accessible state information and author settable properties for XML

Abstract (in document): Web applications often rely on a hybrid of technologies (such as SVG, AJAX, DHTML and JavaScript) that do not promote the rich interaction semantics. Adaptive technologies, that need to provide alternative access to complex user interfaces, are often left guessing at the semantics behind specific portions of a document making them inaccessible. To fix the problem this specification provides extra semantics to support platform accessibility interfaces.

Trailer (in PF public home page): This specification defines attributes that provide XML languages with the ability to add extra information about the behavior of an element. States and Adaptable Properties are mapped to accessibility frameworks (such as a screen reader) that use this information to provide alternative access solutions. Similarly state and author properties can be used to dynamically change the rendering of content using different style sheet properties. The result is to provide an interoperable way for associating behaviors with document-level markup. Additionally, this specification includes markup to fix keyboard focus problems with today's XHTML 1.X markup.

Filename Now: StatesAndProperties-yyyymmdd.html

Short Name Options: waistate

Dated Name Consequences: WD-waistate-yyyymmdd