Re: Question about "Implicit value for Role"

The question is very clear now, thank you.

Matt King
IBM Senior Technical Staff Member
I/T Chief Accessibility Strategist
IBM BT/CIO - Global Workforce and Web Process Enablement 
Phone: (503) 578-2329, Tie line: 731-7398
mattking@us.ibm.com



From:   Shane McCarron <shane@aptest.com>
To:     Birkir Gunnarsson <birkir.gunnarsson@deque.com>, 
Cc:     Matthew King/Fishkill/IBM@IBMUS, James Craig <jcraig@apple.com>, 
"W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Date:   03/24/2015 08:01 AM
Subject:        Re: Question about "Implicit value for Role"
Sent by:        ahby@aptest.com



I am sorry this is confusing.  I don't know how else to ask the question.  
In our specifications (e.g., ARIA 1.1) we say:

<h3>Implicit Value for Role</h3>
            <p>Many states and properties have default values. 
Occasionally, the default value when used on a given role should be 
different from the usual default. Roles that require a state or property 
to have a non-standard default value indicate this in the "Implicit Value 
for Role". This is expressed in the form "<code>state or property 
name</code> is <code>new default value</code>". Roles that define this 
have the new default value for the state or property if the author does 
not provide an explicit value.</p>

My question is, if a role (e.g., chapter in DPub) had any information in 
this field of its definition in the specification (e.g., 
aria-myNewState="true"), would that be inherited by any children of the 
role (e.g., subchapter in DPub)?

Right now the javascript that auto-generates portions of the ARIA 
specification(s) does not take this into account.  I am just trying to 
figure out if it needs to.

Is that clearer?

On Tue, Mar 24, 2015 at 8:31 AM, Birkir Gunnarsson <
birkir.gunnarsson@deque.com> wrote:
Shane, could you provide pseudo code to clarify?
I am still a bit confused by the question.
Are we talking about role or attribute?
Would this help?
http://www.w3.org/TR/aria-in-html/
(the "implicit semantics" column)?


On 3/24/15, Shane McCarron <shane@aptest.com> wrote:
> And specifically of the value of a field in a table in our 
specifications.
> It is a field in the template for a role, and I am not clear if children 
of
> a role should be inheriting whatever is in that field.
>
> On Tue, Mar 24, 2015 at 6:30 AM, Matthew King <mattking@us.ibm.com> 
wrote:
>
>> The original question:
>> > If there is data in the value for this field for a given role (e.g.,
>> "select") and another role references that role as a superclass, should
>> the
>> new "child" role inherit those implicit values automatically?
>> Example provided by James Craig:
>> > role=alert has an implicit value of "assertive" so the author just
>> > needs to write:
>> >     role="alert"
>> > Not:
>> >     role="alert" aria-live="assertive"
>>
>> I still do not understand the original question given the example. I
>> didn't even realize that there was a concept of value associated with
>> ARIA
>> roles., e.g., Alert has a value of assertive? Isn't it the live 
property
>> that has the value, not the assertive role?
>>
>> The original question is asking about the value of a field.
>>
>> Matt King
>> IBM Senior Technical Staff Member
>> I/T Chief Accessibility Strategist
>> IBM BT/CIO - Global Workforce and Web Process Enablement
>> Phone: (503) 578-2329, Tie line: 731-7398
>> mattking@us.ibm.com
>>
>>
>>
>> From:        James Craig <jcraig@apple.com>
>> To:        Shane McCarron <shane@aptest.com>, W3C WAI Protocols & 
Formats
>> <public-pfwg@w3.org>,
>> Date:        03/23/2015 10:26 PM
>> Subject:        Re: Question about "Implicit value for Role"
>> ------------------------------
>>
>>
>>
>> It's about authoring convenience. For example, role=alert has an 
implicit
>> value of "assertive" so the author just needs to write:
>>
>>     role="alert"
>>
>> Not:
>>
>>     role="alert" aria-live="assertive"
>>
>> We document the "implicit values for roles," otherwise the default 
value
>> would be the default for the attribute, which is "off" for aria-live.
>>
>>
>>
>> On Mar 23, 2015, at 4:40 PM, Shane McCarron <*shane@aptest.com*
>> <shane@aptest.com>> wrote:
>>
>> Actually, no.  I don't even know what "Implicit value for Role" means
>> really.  I can guess, but I would have assumed it was only relevant in 
a
>> host language context.
>>
>> On Mon, Mar 23, 2015 at 3:47 PM, Matthew King <*mattking@us.ibm.com*
>> <mattking@us.ibm.com>> wrote:
>> Can you provide an example?
>>
>> Matt King
>> IBM Senior Technical Staff Member
>> I/T Chief Accessibility Strategist
>> IBM BT/CIO - Global Workforce and Web Process Enablement
>> Phone: *(503) 578-2329* <%28503%29%20578-2329>, Tie line: 731-7398
>> *mattking@us.ibm.com* <mattking@us.ibm.com>
>>
>>
>>
>> From:        Shane McCarron <*shane@aptest.com* <shane@aptest.com>>
>> To:        "W3C WAI Protocols & Formats" <*public-pfwg@w3.org*
>> <public-pfwg@w3.org>>,
>> Date:        03/22/2015 05:24 PM
>> Subject:        Question about "Implicit value for Role"
>> Sent by:        *ahby@aptest.com* <ahby@aptest.com>
>> ------------------------------
>>
>>
>>
>>
>> If there is data in the value for this field for a given role (e.g.,
>> "select") and another role references that role as a superclass, should
>> the
>> new "child" role inherit those implicit values automatically?
>>
>> --
>> Shane McCarron
>> Managing Director, Applied Testing and Technology, Inc.
>>
>>
>>
>>
>> --
>> Shane McCarron
>> Managing Director, Applied Testing and Technology, Inc.
>>
>>
>
>
> --
> Shane McCarron
> Managing Director, Applied Testing and Technology, Inc.
>



-- 
Shane McCarron
Managing Director, Applied Testing and Technology, Inc.