Merge pull request #224 from wpaccessibility/typos

rianrietveld · web-flow · commit ad5ca6ff4606 · 2025-11-24T10:43:23.000+01:00
typos
diff --git a/docs/topics/code/components/dialog.md b/docs/topics/code/components/dialog.md
@@ -7,7 +7,7 @@ nav_order: 5
 
 # The dialog modal
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed, modernized and restructured.  
 Related issue on [GitHub #152 Topic The dialog modal](https://github.com/wpaccessibility/wp-a11y-docs/issues/152).  
 
diff --git a/docs/topics/code/components/excerpt.md b/docs/topics/code/components/excerpt.md
@@ -7,7 +7,7 @@ nav_order: 3
 
 # Post Excerpts
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed, modernized and restructured.  
 Related issue on [GitHub #151 Topic Post Excerpts](https://github.com/wpaccessibility/wp-a11y-docs/issues/151).  
 
diff --git a/docs/topics/code/components/link-logo.md b/docs/topics/code/components/link-logo.md
@@ -7,6 +7,6 @@ nav_order: 4
 
 # Link on a logo in the header
 
-{: .alert }
+{: .callout .alert }
 This content will be written.  
 Related issue on [GitHub #150 Topic Link on a logo in the header](https://github.com/wpaccessibility/wp-a11y-docs/issues/150).  
diff --git a/docs/topics/code/components/pagination.md b/docs/topics/code/components/pagination.md
@@ -7,6 +7,6 @@ nav_order: 6
 
 # Pagination
 
-{: .alert }
+{: .callout .alert }
 This content will be written.
 Related issue on [GitHub #153 Topic Pagination](https://github.com/wpaccessibility/wp-a11y-docs/issues/153).  
diff --git a/docs/topics/code/components/skip-links.md b/docs/topics/code/components/skip-links.md
@@ -7,7 +7,7 @@ nav_order: 2
 
 # Skip links
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured.  
 Related issue on [GitHub #149 Topic Skip links](https://github.com/wpaccessibility/wp-a11y-docs/issues/149).  
 
diff --git a/docs/topics/code/dynamic-changes/index.md b/docs/topics/code/dynamic-changes/index.md
@@ -7,7 +7,7 @@ nav_order: 7
 
 # Feedback on dynamic changes
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured. And probably divided into separate topics for more use cases.
 Related issue on [GitHub #166 Topic Feedback on dynamic changes](https://github.com/wpaccessibility/wp-a11y-docs/issues/166).  
 
diff --git a/docs/topics/code/heading-structure/index.md b/docs/topics/code/heading-structure/index.md
@@ -7,7 +7,7 @@ nav_order: 3
 
 # Heading structure in theme development
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured.  
 Related issue on [GitHub #142 Topic Heading structure in theme development](https://github.com/wpaccessibility/wp-a11y-docs/issues/142).  
 
diff --git a/docs/topics/code/images-animations/images.md b/docs/topics/code/images-animations/images.md
@@ -7,7 +7,7 @@ nav_order: 2
 
 # Images in theme development
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured.  
 Related issue on [GitHub #147 Topic Images in theme development](https://github.com/wpaccessibility/wp-a11y-docs/issues/147).  
 
diff --git a/docs/topics/code/images-animations/reduced-motion.md b/docs/topics/code/images-animations/reduced-motion.md
@@ -7,7 +7,7 @@ nav_order: 3
 
 # Setting reduced motion for animations
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured.  
 Related issue on [GitHub #148 Topic Setting reduced motion for animations](https://github.com/wpaccessibility/wp-a11y-docs/issues/148).  
 
diff --git a/docs/topics/code/screen-reader-text/index.md b/docs/topics/code/screen-reader-text/index.md
@@ -7,7 +7,7 @@ nav_order: 6
 
 # The CSS class screen-reader-text
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured.  
 Related issue on [GitHub #145 Topic The CSS class screen-reader-text](https://github.com/wpaccessibility/wp-a11y-docs/issues/145).  
 
diff --git a/docs/topics/code/semantics/index.md b/docs/topics/code/semantics/index.md
@@ -7,7 +7,7 @@ nav_order: 2
 
 # Semantic HTML
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured.  
 Related issue on [GitHub #141 Topic Semantic HTML](https://github.com/wpaccessibility/wp-a11y-docs/issues/141).  
 
diff --git a/docs/topics/content/links/link-destinations.md b/docs/topics/content/links/link-destinations.md
@@ -8,7 +8,7 @@ nav_order: 4
 
 # Link destinations
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed, restructured and expanded.
 Related issue on [GitHub #118 Topic Link destinations](https://github.com/wpaccessibility/wp-a11y-docs/issues/118).  
 
diff --git a/docs/topics/content/links/link-image.md b/docs/topics/content/links/link-image.md
@@ -7,7 +7,7 @@ nav_order: 3
 
 # Images as links
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed, restructured and expanded.
 Related issue on [GitHub #117 Topic Images as links](https://github.com/wpaccessibility/wp-a11y-docs/issues/117).  
 
diff --git a/docs/topics/content/links/link-text.md b/docs/topics/content/links/link-text.md
@@ -7,7 +7,7 @@ nav_order: 2
 
 # Write a meaningful link text
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed, restructured and expanded.
 Related issue on [GitHub #110 Topic Write a meaningful link text](https://github.com/wpaccessibility/wp-a11y-docs/issues/110).  
 
diff --git a/docs/topics/design/avoid/infinite-scroll.md b/docs/topics/design/avoid/infinite-scroll.md
@@ -7,11 +7,10 @@ nav_order: 2
 
 # Patterns to avoid: Infinite scroll
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured.
 Related issue on [GitHub #132 Topic Patterns to avoid: Infinite scroll](https://github.com/wpaccessibility/wp-a11y-docs/issues/132).  
 
-
 We don’t recommend using infinite scroll because it has many significant accessibility issues:
 
 - You can’t go back to your previous place using browser “back” button.
diff --git a/docs/topics/design/color/color-contrast-forms.md b/docs/topics/design/color/color-contrast-forms.md
@@ -7,6 +7,6 @@ nav_order: 4
 
 # Color contrast in forms
 
-{: .alert }
+{: .callout .alert }
 This content will be written.
 Related issue on [GitHub #129 Topic Color contrast in forms](https://github.com/wpaccessibility/wp-a11y-docs/issues/129).  
diff --git a/docs/topics/design/color/color-contrast-icons.md b/docs/topics/design/color/color-contrast-icons.md
@@ -7,6 +7,6 @@ nav_order: 3
 
 # Color contrast of icons
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed, restructured and expanded.
 Related issue on [GitHub #128 Topic Color contrast of icons](https://github.com/wpaccessibility/wp-a11y-docs/issues/128).  
diff --git a/docs/topics/design/color/color-contrast-text.md b/docs/topics/design/color/color-contrast-text.md
@@ -7,7 +7,7 @@ nav_order: 2
 
 # Color contrast of text against its background
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed, restructured and expanded.
 Related issue on [GitHub #127 Topic Color contrast of text against its background](https://github.com/wpaccessibility/wp-a11y-docs/issues/127).  
 
diff --git a/docs/topics/design/color/use-of-color.md b/docs/topics/design/color/use-of-color.md
@@ -7,7 +7,7 @@ nav_order: 4
 
 # Using color
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured.
 Related issue on [GitHub #130 Topic Color Use of color](https://github.com/wpaccessibility/wp-a11y-docs/issues/130).  
 
diff --git a/docs/topics/design/focus-hover/index.md b/docs/topics/design/focus-hover/index.md
@@ -7,7 +7,7 @@ nav_order: 3
 
 # Styling hover and focus
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and rewritten for designers.
 Related issue on [GitHub #214 Topic Styling focus and hover](https://github.com/wpaccessibility/wp-a11y-docs/issues/214).  
 If you want to work on this, please let us know **before you start**.
diff --git a/docs/topics/design/fonts/index.md b/docs/topics/design/fonts/index.md
@@ -7,12 +7,10 @@ nav_order: 2
 
 # Fonts
 
-{: .alert }
+{: .callout .alert }
 This content will be reviewed and restructured and probably divided into separate topics.
 Related issue on [GitHub #124 Topic Fonts](https://github.com/wpaccessibility/wp-a11y-docs/issues/124).  
 
-This content will be reviewed and restructured and divided between separate topics.
-
 ## Font sizes and resize text
 
 The [WCAG 2.0 requirements](https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html) for resizing text are quite loose:
diff --git a/docs/topics/design/meaningful-sequence/index.md b/docs/topics/design/meaningful-sequence/index.md
@@ -7,6 +7,6 @@ nav_order: 5
 
 # Meaningful sequence of content
 
-{: .alert }
+{: .callout .alert }
 This content will be written.
 Related issue on [GitHub #134 Topic Meaningful sequence of content](https://github.com/wpaccessibility/wp-a11y-docs/issues/134).  
diff --git a/docs/topics/forms/descriptions/connect-description.md b/docs/topics/forms/descriptions/connect-description.md
@@ -29,7 +29,7 @@ The HTML basics:
         autocomplete="name" />
 ```
 
-{: .alert }
+{: .callout .alert }
 IDs used must be unique on each page; otherwise, the wrong description may be announced with a form field.
 
 It's possible to add multiple descriptions to one form field. You can combine the text of the description and an error message by separating the IDs with a space. The order of the IDs given in the `aria-describedby` attribute is the order in which they are announced.
diff --git a/docs/topics/forms/fieldsets/legend.md b/docs/topics/forms/fieldsets/legend.md
@@ -51,7 +51,7 @@ A legend can contain a heading. Make sure that the heading level fits correctly
 </fieldset>
 ```
 
-{: .alert }
+{: .callout .alert }
 The reverse is not true: a heading may not contain a `legend`, because the `legend` needs to be an immediate child of the `fieldset`.
 
 ```html
diff --git a/docs/topics/forms/input-label/accessible-name.md b/docs/topics/forms/input-label/accessible-name.md
@@ -105,7 +105,7 @@ If you have to, here are the basics:
 <button>Go</button>
 ```
 
-{: .alert }
+{: .callout .alert }
 Visual text or equivalent, like a search icon, should always be visible, so sighted users don't have to guess what they need to fill out.
 
 If you must hide a label or control from vision, use the CSS class [`.screen-reader-text`](https://make.wordpress.org/accessibility/handbook/best-practices/markup/the-css-class-screen-reader-text/) or equivalent.
diff --git a/docs/topics/forms/required/mark-optional-fields.md b/docs/topics/forms/required/mark-optional-fields.md
@@ -22,7 +22,7 @@ Assuming that you only request essential information in forms, most fields will
     </figcaption>
 </figure>
 
-{: .alert }
+{: .callout .alert }
 **Note for developers**: for screen reader users, the indication if a field is required must be added in the code with a form field. Learn how to [Indicate required fields for screen readers]({{site.baseurl}}/docs/topics/forms/required/required-screen-readers/).
 
 ## Indication of optional fields in WordPress form plugins
diff --git a/docs/topics/forms/required/mark-required-fields.md b/docs/topics/forms/required/mark-required-fields.md
@@ -26,7 +26,7 @@ A required field indicator can be:
     </figcaption>
 </figure>
 
-{: .alert }
+{: .callout .alert }
 **Note for developers**: screen readers have specific needs for discovering required fields. Read [Mark if a form field is required for screen readers]({{site.baseurl}}/docs/topics/forms/required/required-screen-readers/) about how to do this.
 
 ## Indication of required fields in WordPress form plugins
