bug: repository row actions lack accessible names

[SHAURYAKSHARMA24]

Summary

The icon-only open and delete actions in each repository row have no accessible names. Screen-reader and voice-control users cannot distinguish the actions or identify which repository they affect.

Expected Behavior

Each repository-row action has a unique accessible name that includes the action and repository context, such as “Open kalyx” and “Delete kalyx”. Decorative icons are hidden from the accessibility tree.

Actual Behavior

The buttons contain only decorative SVG icons and expose no visible text, aria-label, or aria-labelledby. The violation repeats for every row.

Reproduction Steps

1. Sign in with an account that owns at least one analysed repository.
2. Open /repositories.
3. Run axe-core with the WCAG 2.2 AA tag set.
4. Inspect the icon-only open and delete actions in a repository row.
5. Observe the button-name violation.

Severity

P1 - High

Evidence

• axe-core 4.12.1 reports button-name with critical automated impact.
• WCAG 2.2: 4.1.2 Name, Role, Value (Level A).
• Manually reconfirmed through Safari accessibility inspection on 2026-08-02.

Environment

• Browser/tooling: Chromium 151 with axe-core 4.12.1; Safari accessibility smoke check.
• Application state: authenticated seeded repository list.
• OS, Node/Python versions, Docker state, and original branch/commit were not recorded in the initial audit.

Acceptance Criteria

• Open and delete actions have repository-specific accessible names.
• Decorative SVG icons are hidden from assistive technology.
• Existing navigation and deletion behavior is unchanged.
• Focused repository-list regression coverage is added.
• Frontend test, lint, and production build pass.

Roadmap Alignment

Advances the §28 trusted-output and usable-workflow criteria by making repository operations inspectable and operable without visual icon interpretation.

Related to #118.

[parthrohit22]

This issue tracks a manual accessibility check required for the WCAG 2.2 AA baseline (PR #241). It will be closed once manual evidence (screen‑reader, keyboard, contrast, etc.) is provided as part of the baseline validation.

[parthrohit22]

Issue Structure Review\n\nUpon reviewing this issue against the repository's bug report template (), I notice it follows a reasonable structure for tracking accessibility violations but doesn't fully conform to the standard bug report template.\n\nCurrent Structure:\n- Affected route and state\n- Reproduction\n- Expected behaviour\n- Actual behaviour\n- WCAG 2.2 criterion\n- Severity and user impact\n- Proposed scope\n- Related to #118\n\nMissing from Bug Report Template:\n- Evidence section (logs, screenshots, or response payloads confirming the issue)\n- Environment section (browser, OS, Node/Python versions, Docker availability, branch/commit)\n\nTitle Format:\n- Current: \n- Template expects: prefix (e.g., )\n\nRecommendations for Proper Restructuring:\n1. Update title to start with while preserving the descriptive text\n2. Reorganize body to match template fields:\n - Summary: What is broken? (Combine affected route/state with core issue)\n - Expected Behavior: What should have happened?\n - Actual Behavior: What happened instead?\n - Reproduction Steps: Numbered steps to reproduce\n - Severity: Select from P0-P3 dropdown\n - Evidence: Add logs/screenshots confirming issue\n - Environment: Add browser/OS/etc. where observed\n3. Preserve valuable extra information:\n - Keep WCAG 2.2 criterion details (add to Summary or Expected Behavior)\n - Keep Proposed scope (valuable for fixing)\n - Keep Related to #118 (valuable for traceability)\n\nThis issue appears to be correctly scoped as a follow-up to the WCAG 2.2 AA baseline work (PR #241, issue #118). The content is accurate and actionable.\n\nNote: As an AI agent, I cannot directly edit issues, but I can provide this analysis for your review. If you agree with these recommendations, you may wish to update the issue accordingly.

[parthrohit22]

Issue structure feedback: This issue follows a reasonable structure for accessibility violations but doesn't fully match the bug report template (.github/ISSUE_TEMPLATE/bug_report.yml). Current sections: Affected route/state, Reproduction, Expected/Actual behaviour, WCAG criterion, Severity/user impact, Proposed scope, Related to #118. Missing from template: Evidence and Environment sections. Title format: Should start with 'bug: ' per template. Content is accurate and actionable for fixing the accessibility issue.

[parthrohit22]

Please work on this immediately. We need a focused PR ready before tomorrow’s university tech-fest presentation. Keep the change limited to this issue’s acceptance criteria and include the frontend test, lint, and production-build results in the PR.

[adity982]

I’d like to work on this focused accessibility fix. I’ll keep the change limited to repository-specific accessible names for the existing open/delete actions, hide their decorative icons from assistive technology, add focused frontend regression coverage, and run the frontend test, lint, and production-build checks required by the issue and contribution guide.