SpiderBasic

Hi Fred,
I'm no pro at using the dev tools and the accessibility of them, at least in Microsoft Edge, is a bit weird, but it looked like at least one div there did have a hidden property on it. I think what you want is more specifically called aria-hidden though, that hides elements specifically for screen reader users
E.g.: <h1 aria-hidden="true">example</h1>
Thanks,
Quin

could you try

<h1 hidden="true">example</h1>

and

<h1 hidden>example</h1>

to see if it works as well ?

Hi Fred,
I tested both of these with a super simple static HTML page in Firefox and MS Edge, and both of them completely hid the heading element from my screen reader.

I think I know what happen: when the TabBarMobile() is really created, it put all the tabs in one list so it can do transitions from one page to another. I don't think I can workaround this unfortunately

Hi Fred,
That's sad news, as it makes making accessible mobile apps with SB much harder.
For whatever it's worth, once I switch tabs a couple times only the content of one tab shows. What does the page markup look like at this point, and would it be possible to send that to a screen reader on first load instead?
Or, perhaps, should we report this upstream to the library developers?
Thanks as always!

Hi Fred,
Since you seem unable to do anything about this yourself, how might I go about reporting it to the Oncen UI devs themselves? I really would like to get this resolved, as it is currently impossible for me to make even somewhat complicated mobile apps in SB, I have to use the Gadget lib Which works, but it makes me sad.