Joe Dolson

Do you mean that with the plugin enabled, orders aren’t created in the correct sequential order, or that some of the orders are being skipped in the display?

That sounds *extremely* strange; WP Accessibility really doesn’t do much in the admin, and I have no idea what might trigger that. I tested the second possibility, and couldn’t reproduce it in my own environment.

Your staging site returns a 404, so I can’t take a look.

At a guess, you’ve got a duplicate ID, but without seeing the site it’s hard to guess.

The transcript is already container-able, by adding a the data-transcript-div with a value that points to a div with that ID somewhere on your page.

The sign language container doesn’t have an equivalent, however; which it probably should.

Thanks for reporting! I can see how this is happening; there’s a string replacement if : is at the start of an event title (which happens on all day events if there’s no text assigned to represent all day events), but it’s replacing all occurrences of : , which is obviously a problem if that’s in the event title.

I’ll ship a fix for this!

That’s kind of strange. The definition of the ableplayer var is present on your site, in the place where I would expect it. But it hadtype="text/plain", and two data parameters added to it designating it as ‘marketing’ and ‘youtube’. That tells me that Complianz is messing with it in some way. After I accepted cookies, the data variable went away entirely.

So this seems like an issue with Complianz. I can play around with that and try and see what it’s doing and why.

Are you using my_calendar_upcoming with no arguments? I changed how some of the argument defaults are sourced, but I wouldn’t expect it to change anything explicitly assigned; if it changed a default, however, that could be on me.

If you can let me know what the arguments are you’re using for the shortcode, that would be useful.

Yeah, it looks like the problem is in the theme. WP Accessibility as adding a focus style, but there isn’t much of a practical way to make an inaccessible menu accessible. Every implementation is different, and the labor to do that is very high. I’d have to add individual handlers for nearly every theme.

If you have an option to swap out the theme’s menu for some other Elementor navigation menu, that might fix your issues.

But if I look at the events that the theme has attached to the menu, there are no events on focus, so there’s nothing to handle making the menus visible if the top level item gets focus.