Questions about this have come up a couple times recently on StackOverflow:

https://stackoverflow.com/questions/43015485/attribute-aria-expanded-not-allowed-on-element-li-at-this-point/43019557#43019557
https://stackoverflow.com/questions/44990967/about-use-aria-expanded-on-role-menuitem/44991285#44991285

…and I’ve answered them as best as I can—but note that among the reasons that web developer-authors want to know what the right thing to do here is that there are some W3C guides and tutorials that use aria-expanded with role=menuitem in violation of the ARIA spec:

WAI-ARIA Authoring Practices 1.1 https://www.w3.org/TR/2017/WD-wai-aria-practices-1.1-20170628/examples/menubar/menubar-1/menubar-1.html
https://www.w3.org/WAI/tutorials/menus/application-menus-code/
https://www.w3.org/WAI/tutorials/menus/examples/appmenu/

Because those are in violation of the ARIA spec, they cause the W3C HTML Checker (validator) to report error messages.

See w3c/aria-practices#410 for discussion of that.

ARIA 1.1: aria-expanded is not supported on menuitem roles #454

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions