Re: Pointers - to point to content issues in the ShadowDOM / iframes

Hi,

The shadow-piercing descendant combinator (>>>) from the CSS Scoping module doesn't seem to be going anywhere: https://drafts.csswg.org/css-scoping/#deep-combinator


Kasper Isager
Software Developer

Siteimprove
Sankt Annæ Plads 28 | DK-1250 København K
kki@siteimprove.com | +45 31 23 42 44

> On 11 Jan 2018, at 19.29, Shadi Abou-Zahra <shadi@w3.org> wrote:
> 
> I'll inquire why this was deprecated by the CSS Working Group.
> 
> Meanwhile, it would be good to hear from others on how well this pointer method would work for relevant types of test rules. Any downsides to it?
> 
> Best,
>  Shadi
> 
> 
> On 11/01/2018 18:13, Alistair Garrison wrote:
>> Hi,
>> There was /deep/ (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fcss-scoping-1%2F%23deep-combinator&data=02%7C01%7Ckki%40siteimprove.com%7C82b850a52a1d4561222908d559215a82%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C0%7C0%7C636512922173595149&sdata=wIp%2BYc8si03ADTiBB3yerBR%2BE7CguuEUFLFHQYGuK50%3D&reserved=0) in CSS – which was designed to do the job, although now deprecated.  However, as a mechanism for our usage it might be useful – although we’d have to say in our docs that this is not a proper CSS locator – it is a pseudo locator.
>> All the best
>> Alistair
>> On 11/01/2018, 16:48, "Shadi Abou-Zahra" <shadi@w3.org> wrote:
>>     Hi Alistair,
>>          There is currently no group working on EARL. The Evaluation and Repair
>>     Tools Working Group (ERT WG) was closed.
>>          Can you make a proposal for the "pseudo selector" and circulate it on
>>     this list? If there is agreement in this group, then we can just write
>>     it up somewhere and start using it. If it proves useful, then we could
>>     look into standardizing this more formally. This could be an existing
>>     W3C group, such as CSS, or another, depending on the how it gets used
>>     within and beyond the accessibility community.
>>          Best,
>>        Shadi
>>               On 11/01/2018 15:23, Alistair Garrison wrote:
>>     > Hi,
>>     >
>>     > We have the current format:
>>     >
>>     > {
>>     >
>>     > +      "test": "auto-wcag:SC1-1-1-css-image.html",
>>     >
>>     > +      "result": {
>>     >
>>     > +        "outcome": "Passed",
>>     >
>>     > +        "pointer": "html > body > h1:nth-child(2)"
>>     >
>>     > +      }
>>     >
>>     > However, neither CSS selectors; or xpath selectors enable us to point to
>>     > content found in:
>>     >
>>     >  1. A ShadowDOM; or recursive levels of ShadowDOMs;
>>     >  2. An iframe DOM; or recursive levels of iframe DOMs.
>>     >
>>     > Really, we need a “pseudo” selector – which we all agree on, which
>>     > allows us to point to content in both contexts.
>>     >
>>     > The question is – do we agree the “pseudo” selector format (maybe just
>>     > an extension to CSS or xpath) between us; do we kick it along to the
>>     > EARL group; or do we raise in to relevant groups in W3C?
>>     >
>>     > Thoughts / comments / suggestions for a “pseudo” format?
>>     >
>>     > Alistair
>>     >
>>     > Alistair Garrison
>>     >
>>     > Director of Accessibility Research
>>     >
>>     > Level Access
>>     >
>>          --
>>     Shadi Abou-Zahra - https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FPeople%2Fshadi%2F&data=02%7C01%7Ckki%40siteimprove.com%7C82b850a52a1d4561222908d559215a82%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C0%7C0%7C636512922173595149&sdata=iPcWN91TQERFl0cqoRFmY12LdYBbLJ0DyU8Y7qr25EI%3D&reserved=0

>>     Accessibility Strategy and Technology Specialist
>>     Web Accessibility Initiative (WAI)
>>     World Wide Web Consortium (W3C)
>>     
> 
> -- 
> Shadi Abou-Zahra - https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FPeople%2Fshadi%2F&data=02%7C01%7Ckki%40siteimprove.com%7C82b850a52a1d4561222908d559215a82%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C0%7C0%7C636512922173595149&sdata=iPcWN91TQERFl0cqoRFmY12LdYBbLJ0DyU8Y7qr25EI%3D&reserved=0

> Accessibility Strategy and Technology Specialist
> Web Accessibility Initiative (WAI)
> World Wide Web Consortium (W3C)
>

Received on Friday, 12 January 2018 07:37:48 UTC