component-driven / component-driven/cypress-axe
Empty table does not trigger violation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 641
- Forks
- 90
- Avg merge
- 6h 8m
- Merged PRs (30d)
- 1
Description
A table with headers but no body should trigger a violation, but it does not.
Testing the same page with chrome plugin shows a violation
<table class="govuk-table">
<caption class="govuk-table__caption govuk-table__caption--m">Your files</caption>
<thead class="govuk-table__head">
<tr class="govuk-table__row">
<th scope="col" class="govuk-table__header">File name</th>
<th scope="col" class="govuk-table__header">Date uploaded</th>
<th scope="col" class="govuk-table__header">Action</th>
</tr>
</thead>
<tbody class="govuk-table__body">
</tbody>
</table>
I can confirm that cypress-axe is being run, as if I remove the h1 from the page, a violation is triggered
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the empty govuk-table case through cypress-axe and compare its result with the Chrome plugin, using the HTML example in the issue as the fixture. Trace the Cypress test entry point that invokes cypress-axe and identify where the empty table is evaluated; done means the case reports the expected accessibility violation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- accessibility, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100