If editor screen uses tabs in form display, checker only sees current tab

Yes; I agree that this is confusing in the UI at the moment.

It looks like it would be possible (though complicated) to modify the library to check inside closed tabs provided by the Field Group module → , as that module does render the field content in the DOM even when hidden. I would need to modify some of the parameters at runtime so that it does not ignore these hidden elements, would need to add a function to hide the tip toggles from results in any hidden tabs, and add a function to ask Drupal to switch tabs and then rerender my results with a different set of hidden tip toggles if someone hits "next" into an alert on the hidden tab.

It looks like it would not be possible to modify the library to check inside closed Paragraph → tabs, as Paragraphs does not render the DOM until a tab is opened.

I'm...honestly not sure what makes sense to do here. I'm trying to be consistent, so I do not like the idea of the module working notably different depending on the fields present on a content type. And Princeton does not put CK content inside Field Group tabs, so I am not sure they would want to sponsor the amount of work involved in something for only that use case.

Thanks for checking this out. To avoid confusion in the short term, the best option for us will be to disable showing the Editoria11y component when authors are editing a page. I'm having some trouble figuring out the best way to do that. Is the only way to do that by modifying this configuration parameter - Hide all alerts if none of these elements are present?

It seems that options to disable the scanner or not check content while it's being edited don't affect the display of the component.

Thanks.

Oh goodness; neither config is working right any more. I will try to get a release out tomorrow with bugfixes.

Config to turn off checker while editing should work correctly in 2.2.9 → .

Thanks very much for your fix itmaybejj! Our authors love Editoria11y!