Minor cleanups from the Milestone 4 final review (non-blocking, bundled):
ARIA tab semantics — the authority kind selector (web/src/authorities/authorities-page.tsx) renders the person/organisation/place tabs as plain NavLinks styled as tabs, with no role="tablist" / role="tab" / aria-selected. They work, but screen-reader users don't get tab semantics. Either adopt proper tab roles or a shadcn Tabs primitive driven by the route.
Unused i18n keys — vocab.title and authorities.title are defined in both en.json and sv.json but never referenced (the nav uses the nav.* keys instead). Either use them as visible page/section headings on the respective screens, or remove them. (en/sv parity must be preserved either way.)
Both are cosmetic/a11y polish; no functional impact.
Minor cleanups from the Milestone 4 final review (non-blocking, bundled):
1. **ARIA tab semantics** — the authority kind selector (`web/src/authorities/authorities-page.tsx`) renders the person/organisation/place tabs as plain `NavLink`s styled as tabs, with no `role="tablist"` / `role="tab"` / `aria-selected`. They work, but screen-reader users don't get tab semantics. Either adopt proper tab roles or a shadcn Tabs primitive driven by the route.
2. **Unused i18n keys** — `vocab.title` and `authorities.title` are defined in both `en.json` and `sv.json` but never referenced (the nav uses the `nav.*` keys instead). Either use them as visible page/section headings on the respective screens, or remove them. (en/sv parity must be preserved either way.)
Both are cosmetic/a11y polish; no functional impact.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Minor cleanups from the Milestone 4 final review (non-blocking, bundled):
ARIA tab semantics — the authority kind selector (
web/src/authorities/authorities-page.tsx) renders the person/organisation/place tabs as plainNavLinks styled as tabs, with norole="tablist"/role="tab"/aria-selected. They work, but screen-reader users don't get tab semantics. Either adopt proper tab roles or a shadcn Tabs primitive driven by the route.Unused i18n keys —
vocab.titleandauthorities.titleare defined in bothen.jsonandsv.jsonbut never referenced (the nav uses thenav.*keys instead). Either use them as visible page/section headings on the respective screens, or remove them. (en/sv parity must be preserved either way.)Both are cosmetic/a11y polish; no functional impact.