- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Wed, 3 Sep 2014 16:10:51 +0000
- To: Joseph Scheuhammer <clown@alum.mit.edu>, "james.nurthen@oracle.com" <james.nurthen@oracle.com>, Steve Faulkner <faulkner.steve@gmail.com>
- CC: James Craig <jcraig@apple.com>, lisa.seeman <lisa.seeman@zoho.com>, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>, Michael Cooper <cooper@w3.org>, Janina Sajka <janina@rednote.net>, Richard Schwerdtfeger <schwer@us.ibm.com>
+1 for me, since it's clear and concise regarding the purpose.
-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu]
Sent: Wednesday, September 03, 2014 7:08 AM
To: james.nurthen@oracle.com; Steve Faulkner
Cc: James Craig; lisa.seeman; W3C WAI Protocols & Formats; Michael Cooper; Janina Sajka; Richard Schwerdtfeger
Subject: Re: Moving Name Computation to a separate specification document
On 2014-09-03 2:00 AM, james.nurthen@oracle.com wrote:
> Wouldn't we include the calculation for accessible description too? If
> so perhaps we should ensure that the name isn't too specific.
The algorithm is documented in the Core-AAM as the first subsection of
"5.6 Special Processing Requiring Additional Computation" [1], and has the heading "Name and Description". Similar to James Craig's suggestion, this is about the name and description properties as exposed in accessibility APIs. So, how about "Accessible Name and Description Computation"?
>
> On Sep 2, 2014, at 22:43, Steve Faulkner <faulkner.steve@gmail.com
> <mailto:faulkner.steve@gmail.com>> wrote:
>
>>
>> On 3 September 2014 06:40, James Craig <jcraig@apple.com
>> <mailto:jcraig@apple.com>> wrote:
>>
>> If it hasn't been suggested already, what about "Accessible Name
>> Computation"?
>>
>>
>> +1
>>
>> radically sensible suggestion
>>
>> --
>>
>> Regards
>>
>> SteveF
>> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Wednesday, 3 September 2014 16:11:33 UTC