ACTION-2119: Update Core-AAM for macOS

James, I went through the Core-AAM:

Verify/update the following role mappings: figure, feed, table

verify aria-roledescription mappings, including with empty string and whitespace text values

Make note of changed to Author Errors such as when to not expose aria-roledescription

Review aria-valuemax, and aria-valuemin default value settings to make sure MacOSX addresses the changes that were designed to align with HTML 5

Need mappings for:

aria-colindex, aria-colcount, aria-rowindex, aria-rowcount, aria-details, aria-erroremessage


Note: one issue we are discussing with NVDA and Freedom Scientific is the issue of dealing with aria-colindex and aria-rowindex, aria-rowspan, aria-colspan in the mappings when rows or columns are discontinuous.

Rich

also the term role

If CoreAAM says "MacOSX" anywhere, please update it to "macOS"; If you still reference "AXAPI" anywhere, please change it to "AX API"

aria-colindex, aria-colcount, aria-rowindex, aria-rowcount
https://bugs.webkit.org/show_bug.cgi?id=163644

feed
https://bugs.webkit.org/show_bug.cgi?id=151691

figure
https://bugs.webkit.org/show_bug.cgi?id=163646

table is still AXTable

empty roledescription
https://bugs.webkit.org/show_bug.cgi?id=163647

roledescription role limitations
https://www.w3.org/WAI/ARIA/track/issues/1048

Not sure what aria-valuemin/max changes you're referring to, but I found one issue.
https://www.w3.org/WAI/ARIA/track/issues/1049

Closing action. Thanks.

Sure. this is from slider, scrollbar, and spinbutton:

Authors MUST set the aria-valuemin, aria-valuemax, and aria-valuenow attributes. If missing, their implicit values follow the same rules as the HTML range input type:

If aria-valuemin is missing or not a number, it defaults to 0 (zero).
If aria-valuemax is missing or not a number, it defaults to 100.
If aria-valuenow is missing or not a number, it defaults to the value half way between aria-valuemin and aria-valuemax.
If aria-valuenow is present but less than aria-valuemin, it defaults to the value of aria-valuemin.
If aria-valuenow is present but greater than aria-valuemax, it defaults to the value of aria-valuemax.

Re-opening as it appears the discussion is not over.

Regarding Rich's comment 19 Oct 2016, the rules he cites are for slider, which matches the HTML range input type. They also apply to the scrollbar role.

It's different for spinbutton (HTML number input type):
- if aria-valuemax is missing, then the spinbutton has no upper bound (Accessibility API dependent).
- if aria-valuemin is missing, the spinbutton has no lower bound (Accessibility API dependent).
- a missing aria-valuenow defaults to zero.

Also, all of these mappings are based on the ARIA 1.1 spec text for slider, scrollbar, and spinbutton.

See the github issues file at https://github.com/w3c/aria/issues for issue 455 through 465