HTML-AAM: role=status is not a good match for output element

[cyns]

The output element isn't exactly a status bar. I think a more generic mapping (group?) and a live region is better. I've aleady updated the UIA mapping here, but I don't think this is a good mapping for the other APIs either.

[cyns]

@stevefaulkner @jasonkiss @asurkov @joanmarie @cookiecrook @klown
I'd like to update this sooner than later. What do you think about removing the mapping from the html output element to role=status? While they have some similarities (polite live region), I think calling an output a status bar is confusing.

[stevefaulkner]

@cyns looking at this related bug may be helpful https://www.w3.org/Bugs/Public/show_bug.cgi?id=26135 there has never been in rough concensus on the correctness of the current mapping

[cookiecrook]

The output element isn't exactly a status bar.

I consider "status" more general than "status bar" ("bar" implies a particular presentation and usage) so I don't have a strong aversion to using status as the default role for the output element.

I think calling an output a status bar is confusing.

Confusing to whom? Most web developers won't be aware of "element default roles" at all. Can you be more specific about why you want the change?

[cyns]

@cookiecrook the aria status role is mapped to Status Bar on IA2 and ATK. It was mapped to that for UIA as well, but I changed it to a group with a polite live region. It may not have originally been intended to be a status bar, but several platforms treat it as such.

I created tracker issues about the aria mappings

[cyns]

https://www.w3.org/WAI/ARIA/track/issues/1024

[asurkov]

I'm not sure whether role=status is a good match, which is defined as
"A type of live region whose content is advisory information for the user but is not important enough to justify an alert"
and HTML output as
"The HTML element represents the result of a calculation or user action."
which is not necessary same.

However it doesn't affect on mapping, since role='status' is mapped to role section plus polite live region in IA2/MSAA/ATK afaik.

[klown]

@asurkov

it doesn't affect on mapping, since role='status' is mapped to role section plus polite live region in IA2/MSAA/ATK afaik.

Current Core-AAM mappings are to ROLE_SYSTEM_STATUSBAR (MSAA/IA2) and ROLE_STATUSBAR (ATK/AT-SPI) plus polite and status live region info. The ARIA 1.0 test case passed using those mappings.

[asurkov]

oh, then it's a bug, HTML output is not a status bar, while ROLE_SYSTEM_STATUSBAR is:

"The object represents a status bar, which is an area at the bottom of a window and which displays information about the current operation, state of the application, or selected object. "

https://msdn.microsoft.com/en-us/library/windows/desktop/dd373608(v=vs.85).aspx

I'm getting a stronger feel to keep HTML mapping on its own, not delegating to ARIA core. Same way we did before.

[jasonkiss]

This issue was moved to w3c/html-aam#36