Figure out how to explain acronyms on the website

[owenatgov]

What

Review all acronyms on the website and decide on policies for explaining these acronyms based on our website's audience and their likely pre-existing knowledge of common technical and departmental acronyms.

Work related to this can be found in the accessible content audit worksheet (design system team access only).

Why

This is to address #4010, an issue raised in the 2024 DAC audit of the GOV.UK Design System website. This issue will enable us to either resolve or explicitly decide not to solve that issue raised by DAC.

This issue is also split off from #4193 in order to make the wider content audit work easier to manage.

Who needs to work on this

Website accessibiltiy squad (driven by content designer)

Who needs to review this

Website accessibiltiy squad

Done when

• We've collected all acronyms on the website
• We've decided which acronyms don't need to be explained, if any
• We've decided how we'll explain acronyms that need explaining
• We've published those updates to the website

[calvin-lau-sig7]

Work to pick up when possible:

Assess the indicative list of acronyms gather on our website, and decide if they're either:

• commonly known
• widely understood to the intended audience
  (see 'Report on acronyms' tab in Accessible content audit worksheet)

As a 2nd piece of work, we will eventually seek to ensure any other acronyms are explained in the first instance on each page of the website