Groups can't have Hidden states; grouped items which start Hidden are visible to Accessibility tools

As long as a Group object has any event attached to it, it will be accessible using the Tab key. It doesn't matter whether the trigger is enabled or disabled, which is rather odd. In fact, the Group shouldn't have any trigger attached to it at all to prevent Tab key access to the group.

If I want to hide the Group, I use an Execute JavaScript trigger to add the hidden class to it, and then remove the class when I want to show it again. This is the same approach Storyline uses for any object that is set to the Hidden state.

// Hide the group
const group1 = document.querySelector('[data-model-id="6hJ8RTBQg2v"]');
group1.classList.add('hidden');

// Show the group
const group1 = document.querySelector('[data-model-id="6hJ8RTBQg2v"]');
group1.classList.remove('hidden');

However, it's very odd that even after the Group is hidden, it is still accessible using the Tab key. I don't think this is the most logical behavior, because an individual object that is in the Hidden state is no longer accessible via the Tab key, even if it has events or triggers attached to it.

My suggestion would be to avoid using Group objects as interactive event targets if the grouped content is intended to be dynamically hidden or shown during runtime.