a11y: ARIA landmarks audit and fix #80

New Issue

Closed

opened 2026-05-26 16:49:39 +00:00 by jmiller · 1 comment

jmiller commented

2026-05-26 16:49:39 +00:00

Owner

Ensure all template regions have proper role attributes and aria-labels: banner, navigation, main, complementary, contentinfo.

Audit all template PHP files for semantic HTML5 elements and add missing ARIA where needed.

WCAG 2.1 AA: 1.3.1 Info and Relationships

Ensure all template regions have proper role attributes and aria-labels: banner, navigation, main, complementary, contentinfo. Audit all template PHP files for semantic HTML5 elements and add missing ARIA where needed. WCAG 2.1 AA: 1.3.1 Info and Relationships

jmiller commented

2026-07-16 17:15:43 +00:00

Author

Owner

✅ Verified working on suite.dev (2026-07-16). Core landmarks are present and exposed to AT: banner (<header>), <main>, contentinfo (<footer>), and navigation regions — screen-reader landmark navigation works.

Note (minor): the page exposes 7 <nav> landmarks; consider giving each a distinct aria-label (e.g. Main, Footer, Language) so AT users can tell them apart. Core requirement met — ready to close.

✅ Verified working on suite.dev (2026-07-16). Core landmarks are present and exposed to AT: banner (`<header>`), `<main>`, contentinfo (`<footer>`), and navigation regions — screen-reader landmark navigation works. Note (minor): the page exposes 7 `<nav>` landmarks; consider giving each a distinct `aria-label` (e.g. Main, Footer, Language) so AT users can tell them apart. Core requirement met — ready to close.

jmiller closed this issue

2026-07-16 17:32:32 +00:00

Priority Medium

Type Task

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoOnyx#80