Contextual module can cause accessible menu to initialize itself using the wrong menu

Problem/Motivation

Accessible menu navigations target the first

element in the nav. Normally, that's fine- but if a user can see something like the contextual module menu, it will find that menu first, and initialize itself on that.

Proposed resolution

Explicitly ignore contextual

s or maybe just make the default selector a direct child on the nav.