• Resolved mrwweb

    (@mrwweb)


    While the new “Subscribe to Calendar” dropdown in v5.12.0 is technically keyboard accessible, it has a few very sub-optimal things that should be improved to make the experience more accessible.

    1. The div with class tribe-events-c-subscribe-dropdown__button and the ul with the class tribe-events-c-subscribe-dropdown__list has tabindex="0". This means when TABing through the page, the keyboard stops on those elements, but they don’t have any functions or content to interact with. Thus, they add “tab stops” that don’t do anything. Those two tabindexes should be removed.
    2. The button with the class tribe-events-c-subscribe-dropdown__button-text should have an aria-expanded attribute (false on page load, true when the dropdown is open) to communicate the state of the menu to assistive technologies.

    This is a “disclosure widget” pattern is has well established best practices for accessibility. Here’s one good article about it which demonstrates the aria-expanded attribute among other things.

    • This topic was modified 4 years, 5 months ago by mrwweb.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hey @mrwweb

    Thank you for reaching out and bringing this to our attention.

    A ticket was logged to make sure we get to the bottom of this during the upcoming maintenance release cycles.

    Stay tuned, we will report back here as soon as the fix is out.

    Cheers,
    Geoff

    Hi there!

    This thread has been inactive for a while so I’ll be marking it as Resolved.

    Please feel free to open a new thread if any other questions come up and we’d be happy to help.

    Best regards,

    Marho

    Thread Starter mrwweb

    (@mrwweb)

    At least on the demo site, these issues haven’t been addressed, so I’m marking this as unresolved.

    Hi again,

    Just noting the internal ticket number here: TEC-4185

    Not sure when this will be addressed, but we will follow up here as soon as we have any news to share.

    Best,
    Sky

    Plugin Support WilloftheD

    (@abzlevelup)

    Hi @mrwweb,

    Since we haven’t heard from you in a while on this topic we will assume that the problem was fixed or is no longer applicable and with that I will mark this as resolved.

    If that is not the case, please let me know, and I will gladly remove the “Resolved” tag and try to help you further. Or you can create a new topic with the problem if you prefer.

    Best Regards,
    Abz

    Thread Starter mrwweb

    (@mrwweb)

    @abzlevelup Please do not close this issue unless the upstream issue (TEC-4185) has actually been fixed! I can look at your demo site and quickly see that the problems I describe are still there.

    @skyshab If you can add on to that ticket, I’d also recommend making the drop-down menu position: absolute. Otherwise, it pushes the page down in a very unexpected way for that type of feature.

    For everyone from TEC on this ticket (cc: @geoffbel @marho), it’s really frustrating to have to reply to keep tickets open when there are associated internal issues that are still open.

    Plugin Support WilloftheD

    (@abzlevelup)

    Hi @mrwweb,

    Thank you for confirming. Apologies, we do understand your frustration here. We would keep this ticket open, and I would follow up the team about this bug ticket: TEC-4185.

    We would get back to you as soon as there are updates regarding this issue.

    Appreciate your time and patience.

    Best,
    Abz

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Accessibility Problems with New Export “dropdown”’ is closed to new replies.