Brainstorm: On the loading of pages within a view container and focus policies #219
Description
When the OnboardingWizard is loaded, all pages within are all loaded. This has implications for tab functionality and accessibility features like screen readers.
If all pages are loaded, then by default; tabbing can go onto other pages that are not in view essentially making tabbing useless, and screenreader can go off the page, also making them useless.
It appears we have two options to address this:
Option A: Only load one page at a time
We can edit/choose containers that will only have one page loaded at a time. The action of continuing to the next page or going back to a previous page will be responsible for containing the logic that will allow for the correct animation to show.
The SwipeView documentation contains info on how to limit the amount of pages loaded, and
Option B: Make a hard boundary between pages
We can make hard boundaries between pages by playing around with focus policies (maybe): https://doc.qt.io/qt-6/qtquick-input-focus.html
I'm not so clear on how we would accomplish this one, but conceptually it's possible.
