Glossary page on WAI website + WAI website publication workflow

Hello ACT.

First, thanks everybody for the discussion last week. And especial 
thanks to Godwin who has been working on this.

The WAI team has been discussing the glossary page proposal. The 
conclusion is:

We support publishing the glossary provided that:

- the group ensures that, if there's any use of AI in the process, it:
   - is thoroughly reviewed by a human before committing, and
   - fits as much as possible with the existing logic,
- the proposal includes an explanation of what this page is about and 
sets clear expectations about its maturity status in the summary box 
(see below proposal),
- the group addresses the usability feedback WAI provided them, including:
   - having a parent (top-level) page at 
https://www.w3.org/WAI/standards-guidelines/act/rules/terms/ with just 
the list of existing terms, which would be the only one included in the 
main navigation of the ACT Rules standalone pages,
   - creating one page per term at 
https://www.w3.org/WAI/standards-guidelines/act/rules/terms/<term>/,

Text for the summary box

[[
This page contains a list of key terms used in [ACT 
Rules](https://www.w3.org/WAI/standards-guidelines/act/rules/), and 
their definitions. It is primarily intended for rule authors.

Note: Some definitions may only be used in [proposed 
rules](https://www.w3.org/WAI/standards-guidelines/act/rules/#about-rule-status). 
Depending on their approval date, approved rules may also use different 
definitions. To find the definition applicable to a specific rule, refer 
to that rule’s glossary section.
]]

WAI is happy to discuss editorial and other wording improvements you may 
suggest.

Next steps for this project are:

- the group works on addressing these pieces of feedback,
- the group asks Daniel and Rémi for another review cycle by explicitly 
emailing them or mentioning them on the issue/PR of choice to track 
progress about the project,
- WAI comes back with a reply that can be:
   - OK to publish as-is based on the review (ideal outcome),
   - other changes needed (not ideal, but can happen in case reviewers 
missed something).

In terms of new projects that may come up for publishing new features to 
the WAI website, WAI would like to remind people about the publication 
workflow [1]. A nice reminder that WAI Team cannot commit to monitoring 
every existing issue/PR on every repository, especially when it's 
outside of the w3c GitHub org. To optimize the time spent on developing 
the features, as well as to allow WAI Staff and the groups to coordinate 
effectively, WAI kindly asks that Staff Contact and WAI website 
technical lead  be assigned to the related issue and that the updates be 
agreed upon before starting any work on the feature.

Looking forward to finalizing this project as soon as these concerns are 
addressed.

Best.

[1]: https://wai-website-theme.netlify.app/workflow/#coop

-- 
Daniel Montalvo Charameli
Principal Accessibility Specialist
W3C WAI

Received on Thursday, 11 June 2026 18:35:16 UTC