Skip to content

Commit

Permalink
Guidelines for bolding in conceptual content (#52079)
Browse files Browse the repository at this point in the history
Co-authored-by: Ethan Palm <[email protected]>
  • Loading branch information
rachaelrenk and ethanpalm authored Aug 27, 2024
1 parent 7923f8b commit 13eb020
Showing 1 changed file with 7 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -277,10 +277,14 @@ Workflow runs are delayed when too many workflows run at once. Since many users

## Emphasis

Use italics to emphasize words or parts of a sentence. Use emphasis sparingly for terminology or context that someone must be aware of to successfully complete the task that they're working on. Do not use italics to emphasize words that have other formatting applied such as all caps for placeholder text or bold for UI elements.
Use bold to emphasize words or parts of a sentence. Use emphasis sparingly (no more than five contiguous words), and remember that it is a visual aid for scannability for sighted users.

* **Use:** _{% data variables.product.pat_v2 %}s_ have several security advantages over {% data variables.product.pat_v1_plural %}.
* **Use:** _For types of packages other than containers_, to the right of the package version click **Delete**.
* Do not bold words that have other formatting applied, such as all caps for placeholder text.
* For accessibility, do not use bolding as the only way to convey meaning or emphasis.

For example:

* **Use:** Managed user accounts **cannot create public content** or collaborate outside your enterprise.
* **Avoid:** Next to _**Title**_, add a descriptive label for your new key.

## Error messages
Expand Down

0 comments on commit 13eb020

Please sign in to comment.