If controls are dynamically moved on the screen, for example, by having its X or Y value change according to a timer or other control, the navigation order will change dynamically too. The order is based on the X and Y property values of the controls. When TabIndex of all controls are set to either -1 or 0, navigation order goes from left-to-right, then top-to-bottom, in a "Z" pattern.
We recommend that you do not set TabIndex to other values. Label, Image, Icon, and other typically non-interactive controls.Ī logical keyboard navigation sequence can be achieved with just these values, along with the use of the Container control. The TabIndex property has two recommended values: TabIndex valueĬontrol participates in keyboard navigation.īutton, Text input, Combo box, and other typically interactive controls.Ĭontrol does not participate in keyboard navigation. Follow either an intuitive across and then down "Z" order or a down and then across "reverse-N" order.Only have a tab stop at controls that are interactive.For many, the keyboard is more efficient than using touch or a mouse. Keyboard navigation is an important aspect of any app. Heading3 and Heading4 can be used for finer hierarchies of headings.ĭetermines if the control participates in keyboard navigation. There should be exactly one Heading1 in each screen that serves as the main heading. This lets screen reader users know whether a Label is a heading and allows them to navigate quickly to different parts of the app.
#Table accessibility screen reader how to#
Learn how to announce dynamic changes with live regions.