TopOfContentObject preventing text select from (and tab-to) non-interactive components

[cahirodoherty-learningpool]

Subject of the issue/enhancement/features

I believe the work that went in to https://github.com/adaptlearning/adapt-contrib-core/releases/tag/v6.63.0 prevents users being able to tab to non-interactive components such as a Text component on chromium browsers.
Additionally, users cannot highlight text (to copy/paste somewhere else for example)

Your environment

• Chromium browsers

[cahirodoherty-learningpool]

@oliverfoster I'm not sure what the best path forward is for this. Manually removing the new div element allows text selection but still an issue with tabbing to the content. Is this best WCAG practice in your opinion? I'm a little confused on that

[oliverfoster]

When you say tabbing, do you mean

• That you're pressing the tab key and that you have a focusable element, such as an a tag, in the text component body?
• Are you talking about the screen reader cursor?

Normally a text component wouldn't be tabable as it would have no focusable elements in it.

Conceptually I'm struggling to imagine why the injected element would prevent either behaviour with any of the unspecified assumptions applied.

I need a fuller description to try to replicate.
Browser, operating system, screen reader deets also if applicable please.

[cahirodoherty-learningpool]

Yeah I think I agree with you there, I was just doubting myself based on a clients query. Thanks

As for the selectable text issue, it is occurring in:
Google Chrome Version 144.0.7559.110 (Official Build) (arm64)
Safari Version 26.2 (19623.1.14.18.4)
Microsoft Edge Version 144.0.3719.92 (Official build) (arm64)
Mozilla Firefox 147.0.2 (aarch64)
macOS Sonoma 14.6.1 / Windows 11 VM (UTM+qemu)