Support tab stop behaviors for controls #886
Milestone
Comments
rozele
added a commit
to rozele/react-native-windows
that referenced
this issue
Sep 16, 2017
Allow, e.g., View buttons to be focusable. This is the first step, the next step is to add a JS native event listener that tracks the currently focused element to re-route keyboard input. Towards microsoft#886
rozele
added a commit
to rozele/react-native-windows
that referenced
this issue
Oct 5, 2017
ControlWindows is a UserControl with a single child Canvas. It has props to enable tab stop, tab index, keyboard navigation mode, and keyUp/Down events. Fixes microsoft#886
|
Option 3. in #1411 is to create a wrapper control component that can manage all the tab stop behavior and keep all other controls the same. This may be a "good-enough" balanced approach. |
rozele
added a commit
to rozele/react-native-windows
that referenced
this issue
Oct 5, 2017
ControlWindows is a UserControl with a single child Canvas. It has props to enable tab stop, tab index, keyboard navigation mode, and keyUp/Down events. Fixes microsoft#886
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For any accessible UI, we'll need to support tab stops. I think this could go one of two ways:
isTabStop.Option 1 will likely be a bit more expensive to implement, as we'll likely have to convert many react-native views to controls (or at least the important ones). Option 2 is likely not a good option at all as it will be very difficult to integrate with the native narrator behavior.
The text was updated successfully, but these errors were encountered: