Skip to content

Restore accessibility suite + fix signed-in dashboard scans - #192

Open
saqibmanan wants to merge 2 commits into
CIfrom
restore/a11y-suite
Open

saqibmanan wants to merge 2 commits into
CIfrom
restore/a11y-suite

Conversation

@saqibmanan

Copy link
Copy Markdown
Contributor

Refs #190

1. Restore (752b188)

The WCAG 2.1 AA suite was never committed and its source had disappeared from disk. I recovered it from untracked-files stash commit eeea1d0. Each file compiles to bytecode identical to the surviving .pyc files. Restored:

  • tests/accessibility/
  • utils/a11y.py and locators/accessibility_locators.py
  • a11y_report_generator.py
  • vendored axe-core 4.10.2
  • the accessibility/widget markers and the pytest_sessionfinish report hook

2. Fix (1b17a1e)

All 5 signed-in scans hit /dashboard/self/<slug>/dataset, because the JS sidebar click never navigated. So usecases, charts, profile and the dashboard hub had never been scanned. Each section is now reached by URL: the slug comes from the logged-in URL, and the landing path is asserted before scanning. The "dashboard" check scans the /dashboard hub.

Results on dev (2026-10-09)

  • 110 checks: 76 passed, 16 failed, 18 not implemented (the widget doesn't exist yet).
  • The failures are the known contrast, skip-link and target-size findings, plus DataSpaceFrontend#499 (Drafts/Published tabs, critical aria-valid-attr-value). The fixed navigation surfaced #499; it's already on prod.

CI impact

None. run-smoke.yml only collects tests/consumer, tests/api and tests/provider, so this suite runs only when invoked explicitly:
pytest tests/accessibility -m accessibility -n 0

Recovered byte-identical from the untracked-files stash commit eeea1d0
(verified against the surviving .pyc). Includes vendored axe-core 4.10.2,
the report generator, markers and the sessionfinish report hook.
The JS sidebar click never left the datasets view, so all five signed-in
scans hit /dashboard/self/<slug>/dataset. Navigate to each section's URL
(slug taken from the logged-in URL), assert the landing path, and scan the
/dashboard hub for the dashboard check.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant