Re: Extensible ARIA?

Matt, I like this idea.  Something that we should try to keep in mind.
 A11Y is for everyone - meat and machine.  The "semantic web" is A11Y too!


On Fri, Apr 4, 2014 at 5:43 PM, Matthew King <mattking@us.ibm.com> wrote:

> I think we need to consider standardized gestures and keyboard commands,
> or a standardized UI event for operational hints. I always have hints
> turned off, but there are still times that when I encounter the new
> FooWidget that I will need the hint. We could rely on AT for having a way
> of speaking it, but that limits the availability of the info to AT users.
>
> 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 Nurthen <james.nurthen@oracle.com>
> To:        public-pfwg@w3.org,
> Date:        04/04/2014 03:35 PM
> Subject:        Re: Extensible ARIA?
> ------------------------------
>
>
>
> For the "public" web I agree.
>
> For intranet applications knowing that something is a FooWidget could be
> beneficial even without that extra hint, as that information could have
> been covered in a training session for the application. Indeed - I would
> want to ensure any hint information could be turned off by the user so once
> they know how to operate the FooWidget they are not informed every time.
>
>
> Regards,
> James
>
> On 4/4/2014 2:57 PM, Matthew King wrote:
> In this discussion, we are fast approaching the need for standardized ways
> of ensuring operational hints can be spoken for any widget in a non-visual
> interface. I don't know any other way the combination of control patterns
> associated with a previously unencountered "FooWidget" could be made
> perceivable and understandable.
>
> So, to be perceivable and understandable, we might have to require
> developers to provide operational hint content whenever an operational
> widget has a custom role. If the control patterns themselves are
> standardized through something like Indie UI then declaring that
> "FooWidget" supports invoke, select, and droptarget could make it possible
> for the operational hint information to be generated dynamically.
>
> 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* <mattking@us.ibm.com>
>
>
>
> From:        Cynthia Shelly *<cyns@microsoft.com>* <cyns@microsoft.com>
> To:        *"lwatson@paciellogroup.com"* <lwatson@paciellogroup.com>
> *<lwatson@paciellogroup.com>* <lwatson@paciellogroup.com>, "'W3C WAI
> Protocols & Formats'" *<public-pfwg@w3.org>* <public-pfwg@w3.org>,
> Date:        04/04/2014 01:57 PM
> Subject:        RE: Extensible ARIA?
>  ------------------------------
>
>
>
> One thing we've talked about for ARIA 2.0 is the idea of adding something
> similar to the Control Patterns in UIA.  Control patterns describe
> behaviors, like invoke, select, droptarget, etc.  They include properties,
> methods and events.  They can be combined to describe the behavior of UI
> controls that don't fit neatly into a role.  These would then be given a
> name in the Localized Control Type field, as discussed in an earlier thread.
>
> In UIA, a role is called a control type, and every control type has
> required control patterns.  For example, buttons must support invoke.  Some
> control types also have optional control patterns.
>
> This model allows for a large number of combinations, and custom naming.
>  It's pretty powerful.
>
> There are also mechanisms for custom properties, events and patterns.
>  That might be more than we want to bite off in ARIA 2.0.
>
> You can read more about patterns here:
>
> *http://msdn.microsoft.com/en-us/library/windows/desktop/ee671194(v=vs.85).aspx*<http://msdn.microsoft.com/en-us/library/windows/desktop/ee671194%28v=vs.85%29.aspx>
>
> More about UIA in general here:
>
> *http://msdn.microsoft.com/en-us/library/windows/desktop/ee684076(v=vs.85).aspx*<http://msdn.microsoft.com/en-us/library/windows/desktop/ee684076%28v=vs.85%29.aspx>
>
> UIA has also part of ISO/IEC TR 13066-2:2012 available at:
>
> *http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=53996*<http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=53996>
>
> * From:* Léonie Watson [*mailto:lwatson@paciellogroup.com*<lwatson@paciellogroup.com>]
>
> * Sent:* Wednesday, April 2, 2014 1:16 AM
> * To:* 'W3C WAI Protocols & Formats'
> * Subject:* Extensible ARIA?
>
> Hello,
>
> Web components offer exciting possibilities, and accessibility is going to
> need to keep pace with this potential. This came up at EdgeConf recently,
> where ARIA was widely thought to be the solution amongst developers.
>
> I'm not sure that ARIA (as it stands) can keep pace with the near infinite
> range of components that developers could/will create? It seems improbable
> that the ARIA spec could ever encompass every/any element/role that a
> developer might conjure up.
>
> Jeremy Keith made this point at EdgeConf, and also suggested the
> possibility of ARIA becoming extensible [1].
>
> I thought it was worth raising here for discussion. Apologies if it's
> already being discussed here or elsewhere.
>
> Léonie.
> [1] *http://adactio.com/journal/6719/* <http://adactio.com/journal/6719/>
>
>
>
> --
> Senior Accessibility Engineer, TPG
> @LeonieWatson @PacielloGroup
>
>
> --
> Regards, James
>
> [image: Oracle] <http://www.oracle.com/>
> James Nurthen | Principal Engineer, Accessibility
> Phone: *+1 650 506 6781* <+1%20650%20506%206781> | Mobile: *+1 415 987
> 1918* <+1%20415%20987%201918>
> Oracle Corporate Architecture
> 500 Oracle Parkway | Redwood City, CA 94065
> [image: Green Oracle] <http://www.oracle.com/commitment>Oracle is
> committed to developing practices and products that help protect the
> environment
>
>