W3C home > Mailing lists > Public > public-pfwg-comments@w3.org > July to September 2010

Re: ARIA "status" role definition should make clear that it is intended to be a status bar

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Thu, 26 Aug 2010 21:50:38 -0500
To: Maciej Stachowiak <mjs@apple.com>
Cc: public-pfwg-comments@w3.org, public-pfwg-comments-request@w3.org, Steve Faulkner <sfaulkner@paciellogroup.com>
Message-ID: <OFB33850A0.8836A547-ON8625778C.000F0E6C-8625778C.000F9F6A@us.ibm.com>

That is correct.  It is meant to be very general. A status can contain all
types of information. Status bars are meant to be monitored by an AT.

Where in the aria spec. definition do we state that status MUST be a
statusbar Steve?

Rich Schwerdtfeger
CTO Accessibility Software Group

From:	Maciej Stachowiak <mjs@apple.com>
To:	public-pfwg-comments@w3.org
Cc:	Steve Faulkner <sfaulkner@paciellogroup.com>
Date:	08/26/2010 04:53 AM
Subject:	ARIA "status" role definition should make clear that it is
            intended to  be a status bar
Sent by:	public-pfwg-comments-request@w3.org

The ARIA definition of the "status" role says:

A container whose content is advisory information for the user but is not
important enough to justify an alert. Also see alert.
Authors MUST provide status information content within a status object.
Authors SHOULD ensure this object does not receive focus.

Status is a form of live region. If another part of the page controls what
appears in the status, authors SHOULD make the relationshipexplicit with
the aria-controls attribute.

This seems very general, and like something that could apply to the HTML5
<output> element for instance. However, according to Steve Faulkner, this
is meant to be mapped to a status bar role in platform accessibility APIs,
which would likely make it inappropriate for <output>. Please correct the
definition in ARIA to make clear that it is not intended to be used only
for status bars or similar constructs.


(image/gif attachment: graycol.gif)

Received on Friday, 27 August 2010 02:51:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:02 UTC