It’s possible that the accessibility mode in Fable is still in its early stages and not fully functional with screen readers such as VoiceOver. The best way to check if you’re doing it correctly would be to consult the Fable documentation or reach out to their support team to see if they have any tips or recommendations on using the accessibility mode with screen readers. Additionally, you could also try testing with other screen readers to see if you have similar results, and gather feedback from blind users to understand their experiences.

Thanks for your reply, Yeh I’m probably going to reach out to the support team, I was just keen to talk to other people who might have experienced something similar.

Hi @Romain_Chen i’m has some user test with blind users. They used JAWS (on windows) as a Screen Reader. For text navigation (as headings or simple text) they used arrows keyboard bottons, while for interaction components the tab keyboard botton. Anyway the prototype has crashed or blocket and they need to refresh the prototype from the browser page.

At the moment i think that the accessible prototyping doesnt work correctly, hope to ad upgrade from Figma teams