I'm wondering if people have feedback on the use of tab to move from field to field in a form, in a situation where some of the fields have likely defaults.
To expand a little bit: - the logical flow (how people think about) entering this kind of data is A-B-C-D-E-F-G. - in the context of the application I can reliably pre-fill values for fields C, D, and E. (here "reliably" means >90% of users tested will want the default values in >90% of the use cases) What I'd like to do is have <TAB> move the user from A-B but then from B-F, skipping the defaulted fields. I know this is going to inconvenience that 10% of users who want to change the default, but the alternative seems to be inconveniencing the 90% who have to hit <TAB> four times to get to the next field they care about. Obviously I can build and test both alternatives, and it's really a simple bit of code difference. What I'm wondering is whether anyone has data or experience with this kind of breaking the usual shortcut behaviors? TIA, --Alan ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
