Tabindex removed from honeypot added by Antispam Bee

[Zodiac1978]

Describe the bug
Antispam Bee is adding a honeypot textarea to the comment form with a tabindex="-1", but the JS from WP Accessibility is removing it.

To Reproduce
Steps to reproduce the behavior:

1. Install Antispam Bee
2. Install WP Accessibility
3. Enable the feature to remove tabindex from focusable elements (if not enabled by default)
4. Visit a post with open comments
5. Tab through the page and see that now you can focus the hidden honeypot.

Expected behavior
The tabindex shouldn't be removed.

Maybe you could add a check if the element has aria-hidden="true"?

Additional context
pluginkollektiv/antispam-bee#696

[joedolson]

My preferred way to handle this is to add a mechanism for the end target to be able to ignore. While I could add an exclusion for aria-hidden="true", that wouldn't catch cases where the aria-hidden is dynamically toggled but the tabindex is still set (admittedly, that's probably an obscure case.)

If I have an ignore class where you can actively elect to have it ignored, then it's only by design cases.

But I could go either way; I'm not set on one or the other...

[Zodiac1978]

In general this is a good approach to have a class to ignore this, like minifying JS plugins where you can add a class, that this specific JS should not be minified.

But it would be best if there would be a common way to do this, that everyone (hopefully) is following. Otherwise we could end up adding classes to ignore more and more other plugins which does not scale in the long term.

If an element has tabindex="-1" and an area-hidden="true" or hidden="true", maybe we should respect that, as someone really wants to make it non-focusable.

So personally I would prefer to solve this here and not in Antispam Bee via CSS class.