diff --git a/docs/output-formats/html-accessibility.qmd b/docs/output-formats/html-accessibility.qmd
index ccf6d85fb..552f064fd 100644
--- a/docs/output-formats/html-accessibility.qmd
+++ b/docs/output-formats/html-accessibility.qmd
@@ -63,6 +63,43 @@ Quarto supports two additional output formats for the accessibility checks, avai
This option is equivalent to `axe: true`.
+### Checking against a WCAG conformance level
+
+::: callout-note
+The `standard` and `best-practice` options were introduced in Quarto 1.10.
+:::
+
+By default, `axe-core` runs its full default rule set, which combines rules for several WCAG versions and levels with axe's own "best practice" rules. If you are working toward a specific WCAG conformance level, use the `standard` option to check only the rules for that level:
+
+``` yaml
+format:
+ html:
+ axe:
+ output: document
+ standard: wcag21aa
+```
+
+The available values name a WCAG version followed by a level: `wcag2a`, `wcag2aa`, `wcag2aaa`, `wcag21a`, `wcag21aa`, `wcag21aaa`, `wcag22a`, `wcag22aa`, and `wcag22aaa`. Each standard is cumulative — it includes the rules for the lower levels and earlier versions it builds on. For example, `standard: wcag21aa` checks the rules for WCAG 2.0 A, 2.0 AA, 2.1 A, and 2.1 AA.
+
+For the full list of rules, grouped by these same WCAG versions and levels, see `axe-core`'s [rule descriptions](https://github.com/dequelabs/axe-core/blob/develop/doc/rule-descriptions.md); each rule links to a page describing what it checks, why it matters, and how to fix violations.
+
+Setting `standard` has two effects beyond filtering the checks to the chosen level:
+
+- Choosing a standard can surface violations the default checks don't report, because `axe-core` keeps a few rules off by default and Quarto enables them when your standard requires them. For example, `standard: wcag2aaa` checks text contrast against the stricter AAA ratio rather than the AA ratio, and `standard: wcag22aa` checks that interactive elements like buttons and links are large enough to tap — a requirement introduced in WCAG 2.2. Rules that `axe-core` has deprecated are never added, whichever standard you choose.
+
+- Axe's best-practice rules — recommendations that aren't required by any WCAG success criterion — are excluded. To check them alongside a standard, add `best-practice: true`:
+
+ ``` yaml
+ format:
+ html:
+ axe:
+ output: document
+ standard: wcag21aa
+ best-practice: true
+ ```
+
+You can also exclude the best-practice rules without choosing a standard by setting `best-practice: false` on its own; the WCAG rules from the default rule set still run.
+
## Example: insufficient contrast
As a minimal example of how this works in Quarto, consider this simple document:
@@ -103,15 +140,15 @@ This violates contrast rules: [insufficient contrast.]{style="color: #111"}.
This is the produced result visible on the page:
::: {.light-content}
-
+{fig-alt="A rendered webpage with an overlay in the bottom right corner reporting a color contrast violation found by axe-core, including the selector of the offending element."}
:::
::: {.dark-content}
-{.autodark}
+{.autodark fig-alt="A rendered webpage with an overlay in the bottom right corner reporting a color contrast violation found by axe-core, including the selector of the offending element."}
:::
## Planned work: automated checks before publishing
-Currently, this feature requires users to open the webpage in a [local preview](/docs/websites/index.html#website-preview), and it uses a CDN to load the `axe-core` library itself.
+Currently, this feature requires users to open the webpage in a [local preview](/docs/websites/index.html#website-preview). (Before Quarto 1.10, the `axe-core` library was loaded from a CDN; it is now bundled with Quarto, so checks also work offline.)
In the future, we envision a mode where every page of a website can be checked at the time of `quarto render` or `quarto publish` in order to reduce the amount of required manual intervention.
\ No newline at end of file