search

w3c / wcag3

WCAG 3
https://w3c.github.io/wcag3/
Other
37 stars 8 forks source link

Guidelines update april 24 #62

Closed rachaelbradley closed 2 months ago

rachaelbradley commented 2 months ago

This is a pull request to publish the work on exploratory guidelines in autumn 2024-winter 2025 into the editor's draft.

The updated sections are:

Preview on Raw.git

Google Doc Version

netlify[bot] commented 2 months ago

Deploy Preview for wcag3 canceled.

Name Link
Latest commit 467f41c47d17fc6ccc2c0aec49f93cd47124bd68
Latest deploy log https://app.netlify.com/sites/wcag3/deploys/663502088f4f0a0008bba833
alastc commented 2 months ago

I can't find it in the source, but there is a plain language section at the top of the "Guidelines" section:

Plain language summary of "Guidelines" The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance.

I suggest:

The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance and some additional requirements.

rachaelbradley commented 2 months ago

I can't find it in the source, but there is a plain language section at the top of the "Guidelines" section:

Plain language summary of "Guidelines" The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance.

I suggest:

The following guidelines are being considered for WCAG 3. They are currently a list of topics which we expect to explore more thoroughly in future drafts. The list includes current WCAG 2 guidance and some additional requirements.

I've made this change.

julierawe commented 2 months ago

Thank you for alphabetizing the outcomes in each section—it helped me notice two subgroups had submitted similar-sounding outcomes in "Text and wording."

Can we change "Verbosity" to "Interface verbosity" so it's clearer that this outcome is different from "Unnecessary words or phrases," which is plain-language guidance that applies to all sentences?

bruce-usab commented 2 months ago

I love every little thing except "aggregate". Some minor editorial in the Google Doc.

alastc commented 2 months ago

Closing, replaced by #63