Re: @aria-describedat at-risk in ARIA 1.1 heartbeat draft

Do I understand that you correctly?

If our intent is a general feature for the whole world, than you say
"Put it in HTML?"

If our intent is a feature for accessibility, would you say "ARIA is
OK?"

Is this correct? Is this your view?

Just walking througha  clarification here ...

Janina

Alexander Surkov writes:
> It looks like I should comment too. I think that if aria-describedat is a
> nice feature for any element and all users can benefit of it then it should
> be part of HTML5 spec.
> Thanks.
> Alex.
> 
> On Mon, Dec 8, 2014 at 9:15 AM, Dominic Mazzoni <dmazzoni@google.com> wrote:
> 
> > On Mon, Dec 8, 2014 at 9:04 AM, John Foliot <john@foliot.ca> wrote:
> >
> >> I think as well that your characterization of "dissent" w.r.t. Gecko and
> >> Blink
> >> is, shall I say, somewhat exaggerated, but (again) I think we should ask
> >> these
> >> actors directly, and neither you nor I assume anything.
> >>
> >
> > Just to be clear, then, I officially object/dissent to the language "User
> > agents should provide a device-independent mechanism to allow a user to..."
> > used anywhere in the ARIA spec, because I feel the user agent directly
> > providing to all users a user-level feature based on an ARIA attribute is a
> > radical departure from the rest of the ARIA spec.
> >
> > Resolutions I would be happy with include:
> > * Change the language so that aria-describedat is mapped to native
> > accessibility APIs only, like the rest of ARIA
> > * Or, make it part of HTML5 and take ARIA out of the name
> >
> >
> >

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/

Received on Tuesday, 9 December 2014 20:00:06 UTC