Re: [Custom] Custom elements and ARIA

Hi Domenic, -- Regards SteveF HTML 5.1 On 28 August 2014 15:57, Domenic Denicola wrote: > Hi Steve, thanks greatly for your help. It's clear now that I should have > reached out to you for your expertise directly before being very wrong on a >

Re: [Custom] Custom elements and ARIA

On Thu, 28 Aug 2014 16:57:00 +0200, Domenic Denicola wrote: Hi Steve, thanks greatly for your help. It's clear now that I should have reached out to you for your expertise directly before being very wrong on a public mailing list :) From: Steve Faulkner It appears (please correct me) y

Re: [Custom] Custom elements and ARIA

Why not put the `implicitAria` role on the element's prototype? That way each instance can override with the attribute in a naive and natural manner: `el.role = "link"`. This would necessitate some getter/setter logic for the aria properties to handle the something like the case with conditional

RE: [Custom] Custom elements and ARIA

Thanks to all for their responses. The fact that I misread a bunch of authoring requirements as UA requirements made things a lot more complicated than they are in reality. I updated my ARIA summary [1] and illustrative scenarios [2] to reflect the actual spec/browser behavior. And, given the m

RE: [Custom] Custom elements and ARIA

From: Nick Krempel > Have you considered allowing ARIA attributes to be set on a shadow root. > > The semantics would be that the browser uses the value of an ARIA attribute > on the (most recent) shadow root for an element, and only if it's not set > there will it fall back to the value of the

RE: [Custom] Custom elements and ARIA

Hi Steve, thanks greatly for your help. It's clear now that I should have reached out to you for your expertise directly before being very wrong on a public mailing list :) From: Steve Faulkner > It appears (please correct me) you have made the assumption that 'strong > native semantics' for

Re: [Custom] Custom elements and ARIA

Have you considered allowing ARIA attributes to be set on a shadow root. The semantics would be that the browser uses the value of an ARIA attribute on the (most recent) shadow root for an element, and only if it's not set there will it fall back to the value of the attribute on the shadow host.

Re: [Custom] Custom elements and ARIA

hi domenic, a few quick initial comments, (I have only skimmed the material you have provided): I don't think it is currently possible to define the browser accessibility API mappings in terms of ARIA as it defines and incomplete set of roles,states and properties used in acc APIs. It appears (

Re: [Custom] Custom elements and ARIA

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/28/2014 01:42 AM, Domenic Denicola wrote: > TL;DR: we (Google) are trying to explain the platform with custom > elements [citation needed] on "explain the platform". - -- Ms2ger -BEGIN PGP SIGNATURE- iQEcBAEBAgAGBQJT/tPwAAoJEOXgvIL+s