Re: REVIEW REQUEST, AGENDA: aria-label-braille and aria-roledescription-braille

Mind adding those suggestions to the github pull requests? Thanks!
--joanie

On 4/3/19 3:36 PM, Gunderson, Jon R wrote:
> Maybe the attributes could be:
> 
> aria-braillelabel
> aria-brailleroledescription
> 
> These are also less like to get confused with using:
> aria-label
> aria-roledescription
> 
> Jon
> 
> 
> -----Original Message-----
> From: Joanmarie Diggs <jdiggs@igalia.com> 
> Sent: Wednesday, April 3, 2019 1:54 PM
> To: John Foliot <john.foliot@deque.com>
> Cc: ARIA Working Group <public-aria@w3.org>; Peter Krautzberger <peter@krautzource.com>
> Subject: Re: REVIEW REQUEST, AGENDA: aria-label-braille and aria-roledescription-braille
> 
> Hey John.
> 
> Thanks for the feedback. Point taken about the double-hyphens. Would you please add that to the github issue so that we have all the feedback in one place for tomorrow's meeting?
> 
> Thanks again!
> --joanie
> 
> On 4/3/19 2:23 PM, John Foliot wrote:
>> Hi Joanie, ARIA WG,
>>
>> As a lurker in this group, I have a small concern about introducing a 
>> new "pattern" into the aria lexicon - specifically "double-hyphenated"
>> attributes (i.e. aria-label-braille and aria-roledescription-braille). 
>> A quick check of the existing ARIA attributes 
>> <https://www.w3.org/TR/wai-aria-1.1/#state_prop_def>, and this will be 
>> the first time that this WG would be introducing that pattern, and so 
>> more than anything else - why?
>>
>> Previously, even "multi-name" attributes have all been concatenated 
>> into one string (ref: Position In Set = aria-posinset 
>> <https://www.w3.org/TR/wai-aria-1.1/#aria-posinset>), and I would 
>> strongly encourage the ARIA WG to maintain that pattern 
>> (aria-labelbraille, aria-roledescriptionbraille) if these new 
>> attributes are to move forward.
>>
>> There is a dotted-line connection here to similar work in the 
>> Personalization TF, where we are developing some new (proposed) 
>> attributes, and I have pushed back somewhat on a similar pattern there.
>> The back-story is that at the last TPAC, the Personalization TF met 
>> with WebPlat WG (as we'd *really* like to have fully-fledged "HTML5"
>> attributes, rather than "specialty" attributes - i.e. coga-*), and we 
>> were cautioned to avoid anything that looked like a micro-syntax 
>> (which these two new aria attributes sorta look like). The 
>> Personalization TF is currently working with data-* (again based upon 
>> the recommendation of Web Plat), and specifically I've pushed back on 
>> proposed attributes such as data-purpose-symbol with (I hope) some 
>> success. As such, I personally believe that we should maintain some 
>> consistency across the various WAI activities here.
>>
>> At any rate, not a hill to die on, but if the WG could consider thisas 
>> some constructive feedback I'd appreciate it.
>>
>> JF
>>
>> On Wed, Apr 3, 2019 at 11:48 AM Joanmarie Diggs <jdiggs@igalia.com 
>> <mailto:jdiggs@igalia.com>> wrote:
>>
>>     Hey all.
>>
>>     Peter has provided pull requests for two proposed features:
>>     aria-label-braille and aria-roledescription-braille. These items will be
>>     the two "meaty" topics for Thursday's call. Therefore, it would be super
>>     if everyone can give them a review prior to the call.
>>
>>     The pull requests can be found here:
>>     * https://github.com/w3c/aria/pull/923
>>     * https://github.com/w3c/aria/pull/924
>>
>>     Each pull request has a raw.githack.com <http://raw.githack.com>
>>     link in a comment. I added these
>>     because github's preview feature seems to be unreliable. Peter and I
>>     will try to keep these links updated (i.e. in case he makes any changes
>>     in response to your review comments).
>>
>>     Thanks in advance for your time and feedback!
>>     --joanie
>>
>>
>>
>> --
>> *​John Foliot* | Principal Accessibility Strategist | W3C AC 
>> Representative Deque Systems - Accessibility for Good deque.com 
>> <http://deque.com/>
>>
> 
>

Received on Wednesday, 3 April 2019 19:44:55 UTC