Skip to content

Added the glossary page#53

Open
G0dwin wants to merge 3 commits intomainfrom
feature/glossary
Open

Added the glossary page#53
G0dwin wants to merge 3 commits intomainfrom
feature/glossary

Conversation

@G0dwin
Copy link
Copy Markdown
Collaborator

@G0dwin G0dwin commented Mar 31, 2026

Adds the tools necessary to generate a glossary page and add it to the nav.

Dependent PR in act-rules to be published shortly.

Note: much of this was generated using Co-pilot, be on the lookout for code that doesn't meet standards.

Because we probably will not be able to preview this until after we merge the packages, I have a preview available on my personal site here.

Related PR: act-rules/act-rules.github.io#2395

Copy link
Copy Markdown
Contributor

@daniel-montalvo daniel-montalvo left a comment

Choose a reason for hiding this comment

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

Hi @G0dwin .

thanks for putting this together.

I think the act-tools repo should be the place to have this conversation, as this is were the logic lives.

I have a couple of thoughts based on previous work, especially act-rules/act-rules.github.io#2377 and w3c/wcag-act-rules#387

The URIs we settled on for these examples were: /act/rules/terms/accessible-name/examples/

This is because on the WAI website we have the pattern that every URI needs to be meaningful in itself.

If we include this work as-is, we would leave /act/rules/terms/ with no meaningful content, and we would be adding yet another pattern /act/rules/glossary/ which wouldn't meet user expectations.

I propose we rename /act-rules/glossary/ to /act/rules/terms/, just to avoid having two patterns repeated throughout.

In addition, I'd request review from @remibetin because these code updates are intended to push content to the WAI website, so he needs to be aware as the WAI website maintainer.

@G0dwin
Copy link
Copy Markdown
Collaborator Author

G0dwin commented Apr 6, 2026

Hi @G0dwin .

thanks for putting this together.

I think the act-tools repo should be the place to have this conversation, as this is were the logic lives.

I have a couple of thoughts based on previous work, especially act-rules/act-rules.github.io#2377 and w3c/wcag-act-rules#387

The URIs we settled on for these examples were: /act/rules/terms/accessible-name/examples/

This is because on the WAI website we have the pattern that every URI needs to be meaningful in itself.

If we include this work as-is, we would leave /act/rules/terms/ with no meaningful content, and we would be adding yet another pattern /act/rules/glossary/ which wouldn't meet user expectations.

I propose we rename /act-rules/glossary/ to /act/rules/terms/, just to avoid having two patterns repeated throughout.

In addition, I'd request review from @remibetin because these code updates are intended to push content to the WAI website, so he needs to be aware as the WAI website maintainer.

Thanks Daniel, I updated the URL and committed the change. You can preview it here.

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.

2 participants