Lint says the accessibility step is undefined, but the step library reference lists it

Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.

Copied the scenario straight out of Accessibility and performance budgets:

gherkin

@ui @regression @a11y
Scenario: The inventory page has no serious accessibility violations
  Given I am on the inventory page
  Then the page should have no accessibility violations of impact "serious" or higher

bash

sdods lint -p demo-shop

text

features/inventory/a11y.feature:6
Undefined step: Then the page should have no accessibility violations of impact "serious" or higher

The phrasing is identical to the table in the step library reference, down to the quotes. What am I missing — a plugin, a dependency, a config flag?

a11y lint ui

asked by Chandra Pillai

2 answers

Accepted answer
Nothing. The step does not exist. Neither does the page should meet the performance budget.
I would rather say that plainly than let you spend an afternoon on the configuration. The accessibility guide and that row in the step library reference describe a design, not a build. What is real as I write this is that @a11y and @perf are reserved in the tag taxonomy and that the project schema accepts accessibility and performance gates on a process. There is no axe hook in the runner yet, and no budget check.
The page that is honest about it is the workshop chapter: Screenshots, a11y and performance.
If you want the check anyway, the interim shape is yours to own:
1. Add the accessibility library to your own project's dependencies — nothing in SDODS pulls it in.
2. Write the step under projects/<slug>/steps/ with the phrasing you actually want, and assert on the result there.
3. Attach the JSON under sdods/a11y/<step>. That attachment name is already reserved in the contracts, so the run viewer and the ingest will file it in the right place even though nothing produces it yet.
bash
```
sdods steps list -p demo-shop
```
is the fastest way to check whether a phrasing you read somewhere is really in your catalogue.
answered by Reeta NandalSDODS team
Before you build step 2, agree what "serious or higher" is going to mean to your team.
The impact field on an accessibility finding is a heuristic supplied by the rule engine, not a severity your product has agreed to. A rule set is not a policy. Teams that skip that conversation ship a gate that fails on a decorative image and passes a keyboard trap, and then quite reasonably stop believing it.
answered by Helle Borg

Know the answer?

Wrap commands and output in triple backticks and they will render as a code block.

Checking whether you’re signed in…

Have a different question? Ask it.

Lint says the accessibility step is undefined, but the step library reference lists it

2 answers

Know the answer?

Related