WG and TF updates #1018
WG and TF updates #1018
Conversation
✅ Deploy Preview for wai-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
- abbreviations (expanding some) - simplify summary sentence (without removing or changing meaning) and format as a list for readability - add section with quick link to Admin home page - remove generic headings - add headings / structure content meaningfully under headings that match key words in the information - make headings sentence case - remove capital letters from nouns that are not proper nouns - Make link text slightly more descriptive, including signaling if moving away from WAI to a different sub-site. - Add / correct URLs - remove passive tense - use plain language - make sentences more concise - make list items consist of only one sentence per item (best practice) - fix typos
There was a problem hiding this comment.
Hi @tamsinewing555,
Thanks for this. I like your alternative approach that avoids lots of headings with a single link. Thanks for taking the time to come up with a solution to my concerns!
There are a few wee things that are slightly off. I have put comments into the PR - ping me if you are unable to find them.
pages/about/groups/agwg.md
Outdated
| The [Project Plan](https://www.w3.org/WAI/GL/wiki/Timelines) details intended timeline and milestones for this work. A [list of publications](https://www.w3.org/TR/tr-groups-all#tr_Web_Content_Accessibility_Guidelines_Working_Group) on the W3C Technical Reports page includes completed deliverables that are no longer worked on by the Working Group. | ||
| The work of the AG Working Group follows the [W3C Process](https://www.w3.org/2023/Process-20231103/). | ||
|
|
||
| This work is partly funded by the [WAI Core 2015 Project](https://www.w3.org/WAI/about/projects/wai-core-2015/). The work of the AG Working Group does not necessarily reflect the views or policies of the funders. |
There was a problem hiding this comment.
Again this seems to have crept in, although I think in this case it is needed. The trouble is where to put it. Not really in 'Current work'. Not sure it fits anywhere in new structure. Closest might be 'Contribute to the work'. Open to ideas.
There was a problem hiding this comment.
I did think the information about who funds the work sits best under 'current work, since it's related.
But if that doesn't make sense, then how about we place it under 'Charter and funding'?
There was a problem hiding this comment.
No, I think it needs to be separate from the Charter... not that I am being helpful with alternative ideas!
There was a problem hiding this comment.
We could place the information under a new h2 heading called 'About the work'. Under that heading will be two h3 headings:
- Current work
- Funding
I've mocked this up on the ARIA WG page that I committed this morning.
Or we could place the information under its own heading, 'Funding', after 'Publications and copyright'?
I don't think the funding information sits logically under 'Contribute to the work' because this is just information about the group (how it is funded) and not a call to action (i.e. to contribute funding), like the other items in this section.
There was a problem hiding this comment.
I don't think it should be close to the 'Current work'. Even having a 'funding' section doesn't make sense to me. If you take it out for the moment and then we can discuss in New Year - we could publish without it and then fix following discussion.
There was a problem hiding this comment.
Will do. This information was removed by a reviewer in the original mock up of the proposed design, so perhaps the information isn't needed on this page and is more appropriate on the 'Sponsor WAI page'?
No description provided.