WCAG 2.1.1, 4.1.2, 1.4.13 · Navigation

A WordPress Accessible Menu Plugin for Dropdowns That Actually Open on Tab

A hover-triggered dropdown menu never opens for someone navigating by keyboard, because there’s no hover with a Tab key. Accessible Menus rebuilds your navigation on the ARIA disclosure pattern: every submenu opens on Enter or Space, announces its expanded state, and closes on Escape.

Most WordPress Mega Menus Are Built for a Mouse. Half Your Visitors Aren’t Using One.

Department directories, service menus, and multi-level navigation on government and education sites are frequently built as hover-only dropdowns. A keyboard user tabs to the parent link, presses Enter, lands on the parent page, and never sees the submenu items at all, because nothing ever triggered the hover state.

This plugin pairs well with WPPersona's built-in accessibility compliance if your agency runs on the WPPersona CMS, and installs standalone on any WordPress 6.0+ site.

4.1.2

WCAG success criterion requiring name, role, and state for all custom UI components

Accessibility Features

What Accessible Menus Actually Checks

Every feature below maps to a specific WCAG 2.1 success criterion, not a vague accessibility claim. Here's exactly what changes on your site.

WCAG 2.1.1 (Level A)

Keyboard-triggered submenus

Submenus open on Enter or Space, not hover alone, so every navigation path available to a mouse user is equally available on a keyboard.

WCAG 4.1.2 (Level A)

ARIA expanded state announcement

Parent menu items get aria-expanded and aria-haspopup attributes that update correctly, so a screen reader announces "collapsed" or "expanded" accurately at every interaction.

WCAG 2.1.2 (Level A)

Escape-to-close behavior

Pressing Escape closes an open submenu and returns focus to the parent trigger, matching the standard ARIA Authoring Practices Guide disclosure pattern.

WCAG 2.1.1, 2.4.3

Mega menu keyboard grouping

Multi-column mega menus maintain a logical, predictable tab order through columns and sections instead of jumping unpredictably based on visual layout.

WCAG 1.4.13 (Level AA)

No hover-only content

Any content that appears on hover, like a submenu preview or tooltip, is also dismissible, hoverable, and persistent per WCAG 1.4.13, rather than vanishing the instant a mouse moves.

How It Works

From Install to Fixed, in Four Steps

01

Point the plugin at your menu

Select your existing WordPress navigation menu, mega menu plugin output, or theme header, and the plugin analyzes its current markup and interaction pattern.

02

Apply the disclosure pattern

The plugin rebuilds the interaction layer, keyboard triggers, ARIA states, and Escape handling, without requiring you to rebuild the menu’s visual design.

03

Test every level with a keyboard

Use the built-in keyboard walkthrough to confirm every submenu, at every depth, opens, closes, and announces state correctly.

04

Verify with a screen reader

A guided screen reader checklist walks through NVDA and VoiceOver testing so you can confirm state announcements before publishing.

Our department directory had six levels of dropdown and every single one was hover-only. A keyboard user could only ever reach the top-level pages.

Webmaster, Special District Government

Common Questions About Accessible Menus

Will this change how my menu looks?

No. The plugin changes the interaction and markup layer, keyboard triggers, ARIA attributes, and focus handling, while leaving your existing CSS and visual design in place.

What is the ARIA disclosure pattern?

It’s a documented interaction model from the ARIA Authoring Practices Guide for showing and hiding content, like a submenu, with the correct roles, states (aria-expanded), and keyboard behavior (Enter, Space, Escape) built in from the start.

Does this work with mega menu plugins I already use?

Yes, for most popular mega menu plugins and page builder navigation modules. The plugin analyzes the rendered markup rather than requiring a specific menu plugin, and flags any menu structure it can’t safely rebuild automatically.

Get Started

Get Accessible Menus on Your Site

There's no self-serve checkout yet. Submit the form and our team confirms your license tier, sends pricing, and gets you installation instructions within 1 business day.

  • WordPress 6.0+, PHP 7.4+, compatible with most mega menu and page builder plugins
  • License covers updates and support for 12 months

Need more than one? See the full Accessibility Suite bundle.

Request to Purchase

Tell us which plugins you need. We'll send licensing and setup details.

Plugins You're Interested In

License Size

We respond within 1 business day · No spam, ever

Free Tool

See Your Agency's PDF Risk in 2 Minutes

Enter your government website URL. We crawl every page, scan every PDF, and deliver a full ADA compliance risk report. No account. No credit card.

Run Free Audit

Talk to Someone Who Speaks Government

Our team understands government procurement, ADA compliance timelines, and what it takes to migrate a government website. Free 20-minute demo. No hard sell.

  • Full platform walkthrough for your agency type
  • Answers to procurement and security questions
  • Honest timeline and migration assessment
Schedule a Free Demo