Since we have top:-999em; for hiding the drop-down when not hovered, do we really need display:none; too ? as this will make at least some screen readers skip over the submenus.

I am not an accessibility guru so I might be wrong or outdated.

Comments

jeremycaldwell’s picture

jeremycaldwell commented
Assigned: Unassigned » sociotech
sociotech’s picture

sociotech commented

TSI,

Most of the Superfish code is used as is, but I can look into it. Could you locate the source (file, line number) of the display: none and the elements it's targeting? Is it coming from Fusion's css/js or Superfish's?

I agree that it would be preferable to make it more accessible.

Thanks.

tsi’s picture

tsi commented

Don't know much about JS but the display:none comes from supposition.js - line 54

stephthegeek’s picture

stephthegeek commented
Title: Superfish & accessibility » Superfish & screen reader accessibility
Assigned: sociotech » Unassigned
Category: support » feature
Status: Active » Needs review

This unfortunately is an issue in Superfish itself. Keyboard navigation works fine but the display:none is an issue for screen readers.

Through some discussion threads about this, I found an updated version by another individual which apparently does the hiding differently.

If someone has a chance to try this out in the meantime, here is some info: http://jsbin.com/useku

stephthegeek’s picture

stephthegeek commented
Version: 6.x-1.0-rc1 » 7.x-1.x-dev
Status: Needs review » Closed (fixed)

In the D7 version, it's now possible to use whatever module/technique you'd like for dropdowns, since the main menu area is a region. We're currently recommending the Superfish module because it is still a standard and easy to port from people's previous themes. However, you can implement any alternative now, so we'll consider this fixed.