RE: aria-level a required property for role="heading" or a supported property with an RFC SHOULD for authors

>>>> With respect to the Core-AAM, I suggest adding to the "Author Errors" 
section, which includes a table of default values for missing required 
states and properties [2].

+1

- Stefan

-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] 
Sent: Dienstag, 23. Juni 2015 15:53
To: Richard Schwerdtfeger; John Foliot
Cc: 'Bryan Garaventa'; 'Cynthia Shelly'; 'David Bolter'; 'Dominic Mazzoni'; 'James Craig'; 'WAI Protocols & Formats'; 'Alexander Surkov'
Subject: Re: aria-level a required property for role="heading" or a supported property with an RFC SHOULD for authors

Hi Rich,

On 2015-06-22 5:57 PM, Richard Schwerdtfeger wrote:
> The first bullet can be satisified by making aria-level a required 
> attribute of the "heading" role. The second bullet should be addressed 
> in the Core Accessibility API Mapping specification although we could 
> put a note in the ARIA 1.1 spec. 

Regarding the second bullet: the ARIA spec adds a row to the 
characteristics table with header "Implicit Value for Role", where 
implicit values for required states and properties are listed. Bryan 
noted that in another email in this thread.

For example, see the characteristics table for combobox: aria-expanded 
is listed as a required state, and lists an implicit value of "false" [1].

With respect to the Core-AAM, I suggest adding to the "Author Errors" 
section, which includes a table of default values for missing required 
states and properties [2].

[1] http://w3c.github.io/aria/aria/aria.html#combobox

[2] 
http://w3c.github.io/aria/core-aam/core-aam.html#document-handling_author-errors


-- 
;;;;joseph.

'Array(16).join("wat" - 1) + " Batman!"'
            - G. Bernhardt -

Received on Wednesday, 24 June 2015 09:21:50 UTC