feat: improvements on glossary a11y #34095
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,14 +6,20 @@ page-type: glossary-definition | |
|
|
||
| {{GlossarySidebar}} | ||
|
|
||
| **Accessibility** (often abbreviated to **A11y** — as in, "a", then 11 characters, and then "y") in web development means enabling as many people as possible to use websites, even when those people's abilities are limited in some way. Web accessibility is formally defined and discussed at the {{Glossary("W3C")}} through the {{Glossary("WAI", "Web Accessibility Initiative (WAI)")}}. | ||
|
|
||
| ## See also | ||
|
|
||
| - [Accessibility](/en-US/docs/Web/Accessibility) | ||
| - [Learn accessibility](/en-US/docs/Learn/Accessibility) | ||
| - [ARIA](/en-US/docs/Web/Accessibility/ARIA) | ||
| - [Web accessibility](https://en.wikipedia.org/wiki/Web_accessibility) on Wikipedia | ||
| - [The W3C Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/) | ||
PassionPenguin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| - [Accessible Rich Internet Applications (WAI-ARIA)](https://w3c.github.io/aria/) | ||
|
There was a problem hiding this comment. put WAI and WAI-ARIA together, given they are in the order of
PassionPenguin marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| - [Web Accessibility In Mind](https://webaim.org/) | ||
| - [Glossary](/en-US/docs/Glossary) | ||
|
There was a problem hiding this comment. I noticed a different style has been adopted here: #33423 (comment), and I understand you might have already implemented it on many pages, so I won't ask you to revert it. However, to keep the list (and the page length) contained, I would have formatted this as (no link on Glossary): For one term in in the list:
For multiple terms:
There was a problem hiding this comment. FWIW I would have personally gone with
Without any extra text, per see also guidelines, but I have no feelings towards any of them. There was a problem hiding this comment. FYI, i have been translated pages under glossary folder for some time (processed about 300-350 files and PRs), and find that in most cases they are arranged in that style, and with suggestion from @bsmth, using the style of the most common case but without a link, i.e. - Glossary
- a.
- b. |
||
|
|
||
| - {{Glossary("Accessibility tree")}} | ||
| - {{Glossary("Accessible description")}} | ||
| - {{Glossary("Accessible name")}} | ||
| - {{Glossary("ARIA")}} | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fly-by comment (meaning I choose not to arbitrate on this), but the format
(**A11Y**)is a very well understood way of indicating contraction/short form of a word. I find "(often abbreviated to A11y — as in, "a", then 11 characters, and then "y")" as verbose with no added value.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
many entries contains these abbreviations descriptions. this above was just copied from Web/Accessibility lol.
i totally agree with your point. l18n, l10n, ... this is a pretty common abbr way in computer science. maybe we can also remove Web/Accessibility's one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would argue that it might be a good thing to keep the verbose derivation of A11y in the Glossary for absolute beginners to web development. We can consider removing it from the Web/Accessibility page.