On testing the accessible prototype, a bug has emerged which complicates the possibility of carrying out accessibility tests with keyboard users.
Basically while the users navigate (with screen reader as a VoiceOver from Mac or JAWS from windows) with tab (for interactive component as a buttons) or arrows (for simple text) keyboard buttons, the page doesnt work correctly cause by not scrolling with the focus order.
Navigation has brought focus out of the correct page flow making it impossible to read the information on the page. The result has been a uncorrect test.
Anyone have found same issue? There are any workaround to resolve temporarily?
I hope Figma development will be able to solve it as soon as possible. User test on a prototype are a big opportunity for UX Designer and development team
