From cf6ffdf043b7b1c558ab37c66b6f008c30b38f02 Mon Sep 17 00:00:00 2001 From: Dan Bjorge Date: Wed, 29 Jun 2022 15:47:31 -0400 Subject: [PATCH] docs(accessibility-testing): fix syntax issues in example 1 (#15204) --- docs/src/accessibility-testing-js.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/src/accessibility-testing-js.md b/docs/src/accessibility-testing-js.md index 39c7a71865..17d2d3f5ce 100644 --- a/docs/src/accessibility-testing-js.md +++ b/docs/src/accessibility-testing-js.md @@ -30,10 +30,10 @@ The following examples demonstrate a few basic accessibility testing scenarios. This example demonstrates how to test an entire page for automatically detectable accessibility violations. The test: 1. Imports the `@axe-core/playwright` package -2. Uses normal Playwright Test syntax to define a test case -3. Uses normal Playwright syntax to navigate to the page under test -4. Awaits `AxeBuilder.analyze()` to run the accessibility scan against the page -5. Uses normal Playwright Test [expect] syntax to verify that there are no violations in the returned scan results +1. Uses normal Playwright Test syntax to define a test case +1. Uses normal Playwright syntax to navigate to the page under test +1. Awaits `AxeBuilder.analyze()` to run the accessibility scan against the page +1. Uses normal Playwright Test [assertions](./test-assertions) to verify that there are no violations in the returned scan results ```js tab=js-ts import { test, expect } from '@playwright/test';