---
title: "Is the capitalized word an abbreviation that should be described?"
date: "2025-03-31T10:47:08+00:00"
summary: "Learn how to make abbreviations accessible on web pages. Improve comprehension for all users, including those with disabilities or using assistive tech."
image:
type: "page"
url: "/web-governance/capitalized-word-abbreviation-should-be-described"
id: "8d4d4749-8590-4cdb-9026-23b90ad0643a"
---

Table of contents will be added

3.1.4 Abbreviations

Introduction
------------

This document provides information about the following Acquia Web Governance accessibility check:

*   Is the capitalized word an abbreviation that should be described?

What
----

Abbreviations on a web page must be clearly described to ensure that all users can understand their meaning. 

Why
---

This is important because some users may not recognize abbreviations.

Who
---

### Affected users

*   Users with cognitive disabilities: Who may struggle with shortened words.
*   Screen reader users: Who use assistive technology, which may not be able to automatically expand or pronounce abbreviations correctly.
*   New visitors to your website: Who may not be familiar with internal terminology or industry-specific acronyms.
*   No impairments: Who might not understand that WCAG refers to _Web Content Accessibility Guidelines_ unless it is expanded or described.

Examples
--------

This section provides some pass and fail examples of this check.

### Pass examples

*   **Expanded abbreviation on first use**
    
    Implementation:
    
        <p>The Web Content Accessibility Guidelines (WCAG) define accessibility standards for digital content.</p>
        <p>According to WCAG 2.1, websites must be perceivable, operable, understandable, and robust.</p>
    
    *   Why this works:
        *   The full term is provided before the abbreviation is used later in the text.
*   **Use of the** `**<abbr>**` **element**
    
    Implementation:
    
        <p>The <abbr title="World Health Organization">WHO</abbr> is a global health organization.</p>
    
    *   Why this works:
        *   When users hover over the _WHO,_ a tooltip shows the expanded text.
        *   Screen readers can announce the full term when they read the abbreviation.
*   **Provide a glossary of abbreviations**
    
    Implementation:
    
        <h2>Glossary</h2>
        <ul>
          <li><strong>SEO</strong>: Search Engine Optimization</li>
          <li><strong>UX</strong>: User Experience</li>
        </ul>
    
    *   Why this works:
        *   Users can refer to the glossary for clarification.

### Fail examples

*   **An abbreviation without explanation**
    
        <p>The WCAG requires websites to be accessible.</p>
    
    *   Issue:
        *   The abbreviation _WCAG_ is used with no definition.
        *   Users who are unfamiliar with the term may not understand its significance.
    *   Fix:
        
        *   Expand the abbreviation the first time it appears:
            
                <p>The Web Content Accessibility Guidelines (WCAG) require websites to be accessible.</p>
            
*   **Abbreviations in an accessibility-related context without support for screen readers**
    
        <p>The WHO published new health guidelines.</p>
    
    *   Issue:
        *   Screen readers may mispronounce _WHO_ instead of reading it as _World Health Organization_.
    *   Fix:
        
        *   Use the `<abbr>` tag:
            
                <p>The <abbr title="World Health Organization">WHO</abbr> published new health guidelines.</p>
            

How
---

This section provides information on how to review and fix the issue.

### How to review it

1.  Identify capitalized words that may be abbreviations.
2.  Check if they are defined or expanded when they are used for the first time.
3.  Ensure that the proper markup is used, such as:
    *   The `<abbr>` element for tooltip descriptions.
    *   A glossary section is provided for commonly-used terms.
4.  Test with assistive technologies to confirm that screen readers can correctly interpret the abbreviations.

### How to fix it

*   **Expand abbreviations when they are used for the first time.**
    
    *   Example: 
        
        _Search Engine Optimization (SEO)_.
        
*   **Use the** `**<abbr>**` **element.**
    
    *   Example: 
        
            <abbr title="User Experience">UX</abbr>
        
*   **Provide a glossary.**
    
    *   Example: 
        
        A list of abbreviations with explanations at the end of the page.
        

Additional resources
--------------------

### WCAG criteria

[3.1.4 Abbreviations](https://www.w3.org/WAI/WCAG21/Understanding/abbreviations.html)