Re: Acronyms in Capabilities: How religious are we?

My two cents:
Yes, expand every single one.
Justification: We will have readers who are less familiar.

To support the abstract being an exec summary: Do not expand in the Abstract. Consider any occurrence after the abstract to be “the first occurrence”.

From: Janina Sajka <janina@a11y.nyc>
Date: Thursday, October 16, 2025 at 11:54
To: Accessibility at the Edge <public-a11yedge@w3.org>
Cc: Jason Taylor <jason@usablenet.com>, Mike Paciello <michael.paciello@audioeye.com>, Lionel Wolberger <lionel@userway.org>
Subject: Acronyms in Capabilities: How religious are we?

Colleagues:

The rule says that the first use of an acronym should be expanded. The
usual approach is the <abbr>.

But, how thorough should we be in this?

The first three in our document are WCAG, HTML, and CSS, and they occur in the Abstract.

The next three are W3C, URL, and URI occuring in our diagram text.

Should we really spell out hyper-text markup language and cascading
style sheets?

And similarly World Wide Web Consortium?

Guidance, please!

--

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/