-
1. Re: Any way to outright exclude a control from the tab order? (besides xfa.host.setFocus)
Jono Moore Jun 18, 2012 2:21 PM (in response to past-tense)I don't know of any other way.
One thing to keep in mind, I believe buttons are part of the tab order to comply with accessibility guidelines (WCAG 2.0, etc.).
-
2. Re: Any way to outright exclude a control from the tab order? (besides xfa.host.setFocus)
HowardTreisman Jun 19, 2012 4:41 AM (in response to Jono Moore)Tab order is a huge pain, because it becomes a massive maintenance issue, and can become a huge area for testing and errors.
Our approach has become to NEVER explicitly specify tab order, but always let Reader just "get it right automatically" by creating the fields in the right order in the first place.
This may not work in some situations, but we find it does work in most. Wrap fields in subforms where necessary to control the behavior.
Good luck.
Howard
-
3. Re: Any way to outright exclude a control from the tab order? (besides xfa.host.setFocus)
Niall O'Donovan Jun 19, 2012 3:37 PM (in response to HowardTreisman)Hi,
In addition we have an example form here: http://assure.ly/gBUUXB, which highlight Howard's point about the automatic tabbing order being set by the relative x/y coordinates of objects (working from the top/left) and that once an object in a subform has focus, tabbing will work through the remaining objects in the subform before coming back out to the rest of the form.
Niall




