Skip to content

Conversation

patrickhlauke
Copy link
Member

Closes #3635

Copy link

netlify bot commented Aug 19, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 7f1675c
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/68ae2845158344000871bc02
😎 Deploy Preview https://deploy-preview-4564--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@patrickhlauke
Copy link
Member Author

Ah, this PR currently fails the "Reflect status" check, but no idea what that is (and the error it shows in the log is not very helpful in that regard). is this the check that wants to avoid a mix of normative and non-normative files being changed in the same PR? and if so, should i bifurcate this PR into two separate ones? (and also, can the error messaging in the check https://github.com/w3c/wcag/actions/runs/17083042062/job/48441437816?pr=4564#step:9:7 be made a bit more human-understandable?)

@patrickhlauke patrickhlauke force-pushed the patrickhlauke-wcag21-references branch from 5d4244f to 47e948f Compare August 19, 2025 22:19
@patrickhlauke patrickhlauke self-assigned this Aug 22, 2025
@mbgower
Copy link
Contributor

mbgower commented Aug 26, 2025

@kfranqueiro is Patrick's analysis correct? Is this just flagging him on a mixed normative/non-normative PR?

@kfranqueiro
Copy link
Contributor

kfranqueiro commented Aug 26, 2025

If you scroll to the top of the check and expand the Annotations section (or click Summary and scroll down which shows the same annotations), you will see the human-readable version:

Check for isolation of changes to TR space or informative docs
Please submit changes to TR space separately from changes to informative docs.

This isn't reflected as clearly within the log in order to allow running all of the checks at once rather than short-circuiting as soon as one fails. IIRC I also tried separating each to its own job but that proved less readable for other reasons.

@patrickhlauke
Copy link
Member Author

do we want/need to separate this PR into two then?

@patrickhlauke
Copy link
Member Author

Assuming so, done #4586

@mbgower mbgower removed the Normative label Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WCAG 2.2 Errata: wrong reference to understanding URL (WCAG21 instead of WCAG22)
3 participants