In the Express map blocks, the key/legend uses an unordered list (<ul>) for the list of clickable locations, which works fine for visual and keyboard navigation. However, the list items (<li>) inside it are all assigned the button role (role="button"), which is not valid HTML—and it's a WCAG 2.1 violation that results in screen reader users not being told how many items are in the list. This becomes a huge problem with robust map blocks that have dozens—or more—of locations they would have to tab through.
There's a good explanation at dequeuniversity.com/rules/axe/4.12/list (I apologize—I can't post a link because my accoutn isn't old enough).
I'll defer to others more knowledgable than me, but ideally the legend would use a semantic element like <button> or <a> inside each <li>, rather than assigning a clickable role to the <li> itself.
Is this something that could be addressed? I ask because we're a government educational institution in the U.S., and we have a deadline of April 26, 2027 for WCAG 2.1 compliance (per federal ADA Title II regulations). We love the Express maps in the StoryMaps we use for teaching and research, but we will have to remove them by the deadline if there are violations.
