sideshowbarker

Hi @k7z45 — in order to accept this PR we need to make our tooling recognize that you’re already a participant in the Browser Testing and Tools Working Group. You...

Thanks @k7z45 — https://labs.w3.org/repo-manager/pr/id/w3c/webdriver/1536 shows this is now green for the IPR check

> `U+0000� ` My reading of the relevant best-practice guidance and relevant spec requirements lead me to believe a warning for that is appropriate, and so the `aria-label` attributes should...

Upon further reflection, I realize this could well be a copypasta spec bug in the AAM spec — so I raised https://github.com/w3c/html-aam/issues/335 over there to get clarification.

Update: @scottaohara [has updated](https://github.com/w3c/html-aam/commit/9f51b04ac7ec186d8164fe46feb8cb8c0d7dec93) the relevant language in the AAM spec to make it more clear. So I think it now unambiguously states the relevant implementation requirements. (Thanks Scott!) However,...

> There is of course the section on URL Writing which does look like a grammar in prose style. > > To be clear, what I tried to do, and...

> I cannot just write a separate section because in one way or another it'll compete with the algorithm for normativity, (ao). That's a big problem and I think it...

> 2. Second, I believe that you already basically have not one, but _two_ alternate semi-normative specifications anyway: the section on writing URLs, which specifies a sort of a grammar...

Note also that the URL spec has multiple conformance classes for which it states normative requirements; its algorithms state one set of requirements for parsers as a conformance class, and...

> a version of what I had should be enough just for a simple overview of URLs It seems like the simple RR diagram in https://github.com/whatwg/url/issues/337#issuecomment-421627310 hits the sweet spot...