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.
Regards,
Maciej
