Re: Agenda: HTML-A11Y Task Force ARIA MAPPING SUB GROUP call on 22nd June at 19:00 UTC (20:00 BST; 15:00 EDT; 14:00 CDT; 12:00 PDT)

<change>
Authors may use the WAI-ARIA role and aria-* attributes on HTML elements,
in accordance with the requirements described in the ARIA specifications,
except where these attributes conflict with the native host language
semantics described in the tables below. These exceptions are intended to
prevent authors from making assisting technology products report
nonsensical roles, states and properties that do not represent the actual
roles, states and properties of elements within the document. [ARIA].
</change>
<to>
Authors may use the WAI-ARIA role and aria-* attributes on HTML elements,
in accordance with the requirements described in the ARIA specifications,
except where these conflict with the semantics described by the tables in
this section. These exceptions are intended to prevent providing
conflicting, duplicate, or meanlingless roles, states, and properties to
assistive technologies when applied to HTML elements. [WAI-ARIA].
</to>
<change>
Authors can and do use a combination of scripting, event handlers and CSS
to create custom widgets, if there are implemented native language features
that provide the same semantic meaning and interaction behaviors as a
custom widget, authors are strongly encouraged to use the native language
features. If the author chooses to override the native semantics and
behaviors of a language feature through the use of scripting, event
handlers and CSS, their use may result in the document being
non-conforming. The addition of WAI-ARIA role and aria-* attributes to
enhance the accessibility of custom widgets, regardless of the conformance
state of the document without them, does not result in an increased state
of non-conformance as long as the usage rules detailed in this section are
adhered to.
</change>
<to>
Authors often use a combination of scripting, event handlers, and CSS to
create custom widgets. When there are native language features that provide
the same semantic meaning and interaction behaviors as a custom widget,
authors are strongly encouraged to use the native language features. In
these cases, accessible user agents should have done most of the work to
ensure these native language features support assistive technologies. If
the author chooses to create a custom widget, thus changing the
functionality of an existing HTML element, the author may need to add
WAI-ARIA role and aria-* attributes to make it accessible. In these
instances the must follow the conformance rules for applying WAI-ARIA to
HTML defined in this section as well as the rules for using aria defined in
the [WAI-ARIA] specification.
</to>

Rich Schwerdtfeger
CTO Accessibility Software Group



From:	Steven Faulkner <faulkner.steve@gmail.com>
To:	HTML Accessibility Task Force <public-html-a11y@w3.org>,
            Richard Schwerdtfeger/Austin/IBM@IBMUS, Cynthia Shelly
            <cyns@microsoft.com>, David Bolter <david.bolter@gmail.com>
Date:	06/22/2010 07:06 AM
Subject:	Re: Agenda: HTML-A11Y Task Force ARIA MAPPING SUB GROUP call on
            22nd 	June at 19:00 UTC (20:00 BST; 15:00 EDT; 14:00 CDT; 12:00
            PDT)



updated subject line date

On 22 June 2010 13:00, Steven Faulkner <faulkner.steve@gmail.com> wrote:

  hi all,


  I think this is complete, barring any feedback.
  significant changes since last week:
  now cover all HTML5 elements
  re-ordered and changed text in most parts.

  http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html



  Tuesday, 22nd June 2010

  Time: 19:00 UTC (20:00 BST; 15:00 EDT; 14:00 CDT; 12:00 PDT)
  Name: ARIA mapping call
  Code:  2742 ("ARIA") (irc.w3.org:6665)
  Zakim Bridge +1.617.761.6200


  irc channel= #aria


  Agenda:


  1. Identify Scribe
  2. Discuss -
  The following attempt at redrafting the html5 mapping aria tables and
  associated text:
  http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html
  3. any additional items





--
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html