Virtual Keyboard as permanent keyboard + accessibility?

A few questions about virtual keyboard use. I gather that the feature is mainly intended to help with input on mobile devices, but I’m wondering if it can be adapted to be accessible for all users.

1. None of the keyboard controls are keyboard-focusable. I would like to be able to:

• A) focus and trigger all the keyboard buttons as the main mode of input (since users may not be aware of the different commands available when typing directly into the mathfield). Apart from adding tabindexes and keyup listeners, the main problem I see here is tab order, since the virtual keyboard is injected at the end of the document and it’s not very practical to navigate quickly between mathfield and kb. Is it something you have ideas about or would consider?
• B) focus and trigger the keyboard toggle button by keyboard (might not be needed, see next point)

1. In my use case the mathfield will be part of a dedicated modal overlay. Would you consider:

• A) adding a virtualKeyboardMode: "on" mode to make the keyboard permanently displayed? (Currently I have used "onfocus" mode and overridden the visibility, opacity and transition properties using CSS to achieve something similar.)
• B) allowing to inject the virtual keyboard element into any specified container? (That may be asking too much, but it could be the logical next step if the permanent mode and accessible keys are feasible.)

[arnog]

The handling of the virtual keyboard in iframes has been improved in the main branch and virtualKeyboardContainer can now display the virtual keyboard within.

[arnog]

OK, thanks, that’s helpful. It seems like fixing this problem would be a better long term solution than adding an option to work around it. I’ll try to see if I can build a sample that reproduces the problem and I’ll investigate.