Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editorial changes to structure/prose #306

Merged
merged 31 commits into from Apr 28, 2021
Merged

Conversation

patrickhlauke
Copy link
Member

@patrickhlauke patrickhlauke commented Apr 19, 2021

Related to #297

  • Small wording/grammatical tweaks
  • Rename the "Document conformance requirements for use of ARIA attributes with HTML attributes" to "Requirements for use of ARIA attributes in place of equivalent HTML attributes" and make it a proper sub-<section> (so it appears in the TOC and gets numbered)
  • Reword some of the abstract and conformance prose

Preview | Diff

Renamed from "Document conformance requirements for use of ARIA attributes with HTML attributes" to "Requirements for use of ARIA attributes in place of equivalent HTML attributes" ... as this actually makes it more understandable immediately why this table is different from the preceding one.
Making it an actual `<section>` makes it appear in the left-hand TOC and gives it a number (3.1)
this was the only place in the whole spec that used "n/a" ... looked ugly/straggly
to avoid the odd-looking clash of "HTML MUST", moved "documents" in this sentence
Only an editorial change that, hopefully, makes it a bit more understandable/readable
@stevefaulkner
Copy link
Collaborator

@patrickhlauke

Document conformance requirements for use of ARIA attributes with HTML attributes

The use of the term "Document conformance" is important in this context as it describes what the rules are tested against

Document-conformance checking is the current party-approved goodthink way of talking about looking for problems in HTML documents. And do note that we call it document conformance and not authoring conformance, and we talk about conformance requirements for documents, not conformance requirements for authors. That’s because you as an author are a human being; a technical specification can’t place requirements on you, it can only place requirements on documents you create. And related tools don’t evaluate you as a human being for conformance to particular technologies; instead they just evaluate the documents you create.
source: https://html5doctor.com/html5-check-it-before-you-wreck-it-with-miketm-smith/

@patrickhlauke
Copy link
Member Author

The use of the term "Document conformance" is important in this context as it describes what the rules are tested against

sure, but it's a subsection of "Document conformance requirements for use of ARIA attributes in HTML", so it's clear it's about document conformance, I'd say (otherwise the heading becomes a bit unwieldy)

Copy link
Member

@scottaohara scottaohara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for taking a look through this all. @stevefaulkner we can give this a merge once you're good to go.

@patrickhlauke
Copy link
Member Author

Made one last minute additional tweak to the abstract ... it always read a bit funny, this may be cleaner/clearer. @scottaohara

index.html Outdated Show resolved Hide resolved
@scottaohara
Copy link
Member

unsure what's going on here @patrickhlauke. Pulled this down and respec is throwing no errors or warnings, locally.

travis is returning this error:

Error: Command failed: java -jar /home/travis/build/w3c/html-aria/node_modules/vnu-jar/build/dist/vnu.jar --also-check-css /tmp/tmp.gdOiHUDM0J/output.html

cc @marcoscaceres

@patrickhlauke
Copy link
Member Author

Is it perhaps somehow checking the test cases where we do expect actual failures?

@scottaohara
Copy link
Member

it shouldn't be.

@patrickhlauke
Copy link
Member Author

patrickhlauke commented Apr 20, 2021

these are the specific errors Travis is reporting/blocking on

"file:/tmp/tmp.gdOiHUDM0J/output.html":332.138-332.205: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":334.138-334.202: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":337.152-337.262: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5613.7-5613.195: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5613.7-5613.195: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5623.13-5623.201: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5623.13-5623.201: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5639.13-5639.217: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5639.13-5639.217: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5649.13-5649.171: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5649.13-5649.171: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5661.13-5661.169: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5661.13-5661.169: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5671.13-5671.197: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5671.13-5671.197: error: Attribute “aria-modal” not allowed on element “aside” at this point.
Error: Command failed: java -jar /home/travis/build/w3c/html-aria/node_modules/vnu-jar/build/dist/vnu.jar --also-check-css /tmp/tmp.gdOiHUDM0J/output.html
"file:/tmp/tmp.gdOiHUDM0J/output.html":332.138-332.205: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":334.138-334.202: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":337.152-337.262: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5613.7-5613.195: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5613.7-5613.195: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5623.13-5623.201: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5623.13-5623.201: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5639.13-5639.217: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5639.13-5639.217: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5649.13-5649.171: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5649.13-5649.171: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5661.13-5661.169: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5661.13-5661.169: error: Attribute “aria-modal” not allowed on element “aside” at this point.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5671.13-5671.197: error: Bad value “dialog” for attribute “role” on element “aside”.
"file:/tmp/tmp.gdOiHUDM0J/output.html":5671.13-5671.197: error: Attribute “aria-modal” not allowed on element “aside” at this point.

https://travis-ci.com/github/w3c/html-aria/builds/223597886

As I don't think that's anywhere in the actual spec's index.html ... this smells to me like it is

@patrickhlauke
Copy link
Member Author

patrickhlauke commented Apr 20, 2021

ah, correction ... the errors here come from things that ReSpect injects into the page (though why only all of a sudden, now?)

e.g.

<dfn id="dfn-strong-native-semantics" tabindex="0" role="link" aria-haspopup="dialog" title="Show what links to this definition"><a data-cite="wai-aria-1.1#host_general_conflict" href="https://www.w3.org/TR/wai-aria-1.1/#host_general_conflict">strong native semantics</a></dfn>

and

<aside class="dfn-panel" hidden="" role="dialog" aria-modal="true" id="dfn-panel-for-dfn-no-corresponding-role" aria-label="Links in this document to definition: No corresponding role">
  ...
</aside>

@marcoscaceres
Copy link
Member

We literally just shipped an update today 🥳 what did we break?

@marcoscaceres
Copy link
Member

Ah! Ok, I see. Will fix first thing tomorrow.

@marcoscaceres
Copy link
Member

Some of those strike me as odd... like "Bad value “dialog” for attribute “role” on element “aside”"?

Why is that not valid? Do the other strike anyone as odd? (Apart from the role=link on an anchor)

@patrickhlauke
Copy link
Member Author

We literally just shipped an update today 🥳 what did we break?

the web

@marcoscaceres
Copy link
Member

Best part of "HTML in ARIA" is that y'all get to tell me how to fix those 🤣😂🤣😂🤣

allowed the `checked` attribute in HTML.
</p>
<p>
Authors SHOULD NOT use the `aria-checked` attribute on any element where the <a data-cite="html/form-control-infrastructure.html#concept-fe-checked">checkedness</a> of the element can be in opposition to the current value of the <a data-cite="wai-aria-1.1#aria-checked">`aria-checked` attribute</a>.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should get the HTML folks to export something properly for "checkedness".

@marcoscaceres
Copy link
Member

Something weird going on with those "clarification of states versus properties".

I've not investigated yet. Will check tomorrow once I'm at computer again. At least the other errors are fixed.

@marcoscaceres
Copy link
Member

marcoscaceres commented Apr 26, 2021

FYI, "clarification of states versus properties", see w3c/aria#1468 ... @jnurthen is going to send a PR to this spec soon.

@jnurthen
Copy link
Member

FYI, "clarification of states versus properties", see w3c/aria#1468 ... @jnurthen is going to send a PR to this spec soon.

This should be resolved. Is it still an issue?

@marcoscaceres
Copy link
Member

Oh! just spotted the other PR @jnurthen. Thanks for sending that!... checking why CI is failing now.

@patrickhlauke
Copy link
Member Author

patrickhlauke commented Apr 26, 2021

@marcoscaceres are we ok to merge this in the knowledge that the travis fail is related to respec rather than the spec itself? or should we hold off merging?

@marcoscaceres
Copy link
Member

The ReSpec issues should be fixed now, but I can't seem to get Travis to retrigger the build. Can someone head over there and click the restart build button? Then it should all turn green and should be good to merge.

(as restarting build doesn't seem to work)
@patrickhlauke
Copy link
Member Author

patrickhlauke commented Apr 27, 2021

@marcoscaceres still erroring out on the following

"file:/tmp/tmp.q4jesHOjfW/output.html":332.138-332.205: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.q4jesHOjfW/output.html":334.138-334.202: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.q4jesHOjfW/output.html":337.152-337.262: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
Error: Command failed: java -jar /home/travis/build/w3c/html-aria/node_modules/respec-validator/node_modules/vnu-jar/build/dist/vnu.jar --also-check-css /tmp/tmp.q4jesHOjfW/output.html
"file:/tmp/tmp.q4jesHOjfW/output.html":332.138-332.205: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.q4jesHOjfW/output.html":334.138-334.202: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.
"file:/tmp/tmp.q4jesHOjfW/output.html":337.152-337.262: error: The element “a” must not appear as a descendant of an element with the attribute “role=link”.

also, for some reason Travis can't be retriggered manually ... "Oh no! An error occurred. The build could not be restarted."

@marcoscaceres
Copy link
Member

@marcoscaceres still erroring out on the following

Looking into those! Will report back soon.

also, for some reason Travis can't be retriggered manually ... "Oh no! An error occurred. The build could not be restarted."

Yeah, getting the same error. Not sure what's going on there :(

Going to transition us to use GitHub Actions, which makes things easier.

@marcoscaceres
Copy link
Member

I think once we rebase on #310 , it should hopefully be happy again.

patrickhlauke and others added 12 commits April 28, 2021 08:19
chore: fixup data-cite usage
Renamed from "Document conformance requirements for use of ARIA attributes with HTML attributes" to "Requirements for use of ARIA attributes in place of equivalent HTML attributes" ... as this actually makes it more understandable immediately why this table is different from the preceding one.
Making it an actual `<section>` makes it appear in the left-hand TOC and gives it a number (3.1)
this was the only place in the whole spec that used "n/a" ... looked ugly/straggly
to avoid the odd-looking clash of "HTML MUST", moved "documents" in this sentence
Only an editorial change that, hopefully, makes it a bit more understandable/readable
Co-authored-by: Marcos Cáceres <marcos@marcosc.com>
(as restarting build doesn't seem to work)
@patrickhlauke
Copy link
Member Author

I think once we rebase on #310 , it should hopefully be happy again.

yes, that seems to have done it

@patrickhlauke patrickhlauke merged commit b65efa2 into gh-pages Apr 28, 2021
@patrickhlauke patrickhlauke deleted the patrickhlauke-tweaks branch April 28, 2021 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants