Re: Proposal: remove aria-describedat from the ARIA 1.1 specification

Any possibility of having specific roles for description and instructions?

“description” and “instruction" could be descendants of section abstract role and save all the creation of role=group aria-label=description | instructions.

Jon


From: Steven Faulkner <faulkner.steve@gmail.com<mailto:faulkner.steve@gmail.com>>
Date: Thursday, November 12, 2015 at 9:16 AM
To: Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>>
Cc: Shane McCarron <shane@aptest.com<mailto:shane@aptest.com>>, Chaals McCathie Nevile <chaals@yandex-team.ru<mailto:chaals@yandex-team.ru>>, "public-pfwg@w3.org<mailto:public-pfwg@w3.org>" <public-pfwg@w3.org<mailto:public-pfwg@w3.org>>, "public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>" <public-digipub-ig@w3.org<mailto:public-digipub-ig@w3.org>>
Subject: Re: FW: Proposal: remove aria-describedat from the ARIA 1.1 specification
Resent-From: "public-pfwg@w3.org<mailto:public-pfwg@w3.org>" <public-pfwg@w3.org<mailto:public-pfwg@w3.org>>
Resent-Date: Thursday, November 12, 2015 at 9:17 AM

I have created a demo making use of aria-flowto: and aria-label=Description with group=role to give an idea of how it may work if an identifying role is added. It primarily demonstrates the utility of aria-flowto in providing a bi-directional relationship between 2 objects in the DOM.

http://s.codepen.io/stevef/debug/PPXZWY<https://urldefense.proofpoint.com/v2/url?u=http-3A__s.codepen.io_stevef_debug_PPXZWY&d=BQMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=TOEZzu82yGUOKImf7ocBg90_IdBhmyFeCmlJOA1tsek&s=RMnn8Ky2MYTrJVLhIXof72lyBGJz3df4Qx6co2tnlMA&e=>

code view: http://codepen.io/stevef/pen/PPXZWY<https://urldefense.proofpoint.com/v2/url?u=http-3A__codepen.io_stevef_pen_PPXZWY&d=BQMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=TOEZzu82yGUOKImf7ocBg90_IdBhmyFeCmlJOA1tsek&s=_VV9VdbhSqUZWwnYRiT0sTP7l4zijIs--JPf8FCIox8&e=>

--

Regards

SteveF
Current Standards Work @W3C<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paciellogroup.com_blog_2015_03_current-2Dstandards-2Dwork-2Dat-2Dw3c_&d=BQMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=TOEZzu82yGUOKImf7ocBg90_IdBhmyFeCmlJOA1tsek&s=2OJkv7IE-VZSe6-2myCnLieD0eIiNmDNXmsXNfjckaE&e=>

On 12 November 2015 at 15:05, Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>> wrote:
Preponderance of opinion on the Dpub-ARIA call is for a main role, as it
should be generally available, not just in epubs.

Expect a conversation about this on today's ARIA call starting at 12:30
Boston (17:30 UTC).

Janina

Shane McCarron writes:
> Sure.  A "main" role or a "doc-" role?  Since this is (actually) a
> mainstream problem, a "main" role seems more sensible to me.  That and a
> technique for guidance and call it a day?
>
> On Thu, Nov 12, 2015 at 5:50 AM, Steve Faulkner <faulkner.steve@gmail.com<mailto:faulkner.steve@gmail.com>>
> wrote:
>
> >
> > On 12 November 2015 at 11:48, Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>> wrote:
> >
> >> It was proposed (during PF this week) that a simple ARIA role could
> >> trigger notification for AT users, and could trigger CSS to show the non
> >> AT user that a description is available.
> >>
> >
> > sounds reasonable
> >
> > --
> >
> > Regards
> >
> > SteveF
> > Current Standards Work @W3C
> > <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paciellogroup.com_blog_2015_03_current-2Dstandards-2Dwork-2Dat-2Dw3c_&d=BQMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=TOEZzu82yGUOKImf7ocBg90_IdBhmyFeCmlJOA1tsek&s=2OJkv7IE-VZSe6-2myCnLieD0eIiNmDNXmsXNfjckaE&e=>>
> >
>
>
>
> --
> Shane McCarron
> Managing Director, Applied Testing and Technology, Inc.

--

Janina Sajka,   Phone:  +1.443.300.2200<tel:%2B1.443.300.2200>
                        sip:janina@asterisk.rednote.net<mailto:sip%3Ajanina@asterisk.rednote.net>
                Email:  janina@rednote.net<mailto:janina@rednote.net>

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:       http://a11y.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__a11y.org&d=BQMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=TOEZzu82yGUOKImf7ocBg90_IdBhmyFeCmlJOA1tsek&s=xnTs_IG2RmyaMhhRPJZC4lNq_bzLzq7GACXgU6KvJJ0&e=>

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,  Protocols & Formats     http://www.w3.org/wai/pf<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_wai_pf&d=BQMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=TOEZzu82yGUOKImf7ocBg90_IdBhmyFeCmlJOA1tsek&s=wM5_XA2Atq90T3rYAUDmLIw5s0N34J_3c6SQodowStQ&e=>