Web design and digital-business ideas grounded in real tasks.

An abbreviation’s title attribute is not a dependable mobile glossary

A phone and tablet displaying a generic glossary rich article on a desk, no readable brands.
AI-generated photographic illustration; not documentary photography.

A desktop user hovers over an abbreviation and sees its expansion. A phone user taps the same text and gets nothing useful. The page contains an explanation, but not necessarily one every reader can reach.

MDN’s reference for the abbr element describes the element’s meaning and accessibility considerations. A title attribute can hold an expansion, but it should not be the only dependable route to understanding.

Put the first explanation in the sentence

An illustrative first use is “Our content management system (CMS) stores the articles.” Later uses of CMS can be shorter because the reader has already received the expansion in ordinary text.

If a page is often entered halfway down, consider whether a section needs its own explanation. A glossary link can help with a specialist term, but a reader should not need to leave the page for every common abbreviation.

Keep markup meaningful

You may still use <abbr> where it accurately describes the content. If you add a title, use the full expansion rather than unrelated instructions or promotional copy. Do not turn the attribute into a hidden paragraph.

For unfamiliar technical language, an expansion may itself need explanation. Spelling out a long phrase does not automatically make its meaning clear to a beginner.

Test the page on a touch device, with keyboard navigation and with appropriate assistive technology. Check whether the essential explanation remains available without hover. Also inspect print or copied text if those are common ways your audience uses the material.

A useful editorial review asks someone new to the topic to underline terms they cannot explain from the page. That reveals more than checking that every abbreviation has a title attribute. The goal is understandable content, with semantics supporting it rather than carrying the entire explanation invisibly.