Can anyone answer this question?
When I am using a browser, such as Firefox, or even, heaven forbid, IE, I often tab through text fields and buttons in a form. I am so used to this, as I work on a PC at work. From a usability point of view, this makes perfect sense. If one is tabbing through a form, a button is an element to tab through, and would be consistent from a usability perspective. However, at home, I use my beloved G5. When using either Safari or Firefox, I can certainly tab through text fields, but NOT through buttons. I have to take the extra step of using my mouse to click on the button instead of hitting 'tab' and then 'return', which is much faster.
Is there a reason for this? Or is it along the same lines as Apple's curious lack of commitment to release a two-button mouse? This isn't exactly rocket science, and would think it should be very easy to implement.
Just curious...
When I am using a browser, such as Firefox, or even, heaven forbid, IE, I often tab through text fields and buttons in a form. I am so used to this, as I work on a PC at work. From a usability point of view, this makes perfect sense. If one is tabbing through a form, a button is an element to tab through, and would be consistent from a usability perspective. However, at home, I use my beloved G5. When using either Safari or Firefox, I can certainly tab through text fields, but NOT through buttons. I have to take the extra step of using my mouse to click on the button instead of hitting 'tab' and then 'return', which is much faster.
Is there a reason for this? Or is it along the same lines as Apple's curious lack of commitment to release a two-button mouse? This isn't exactly rocket science, and would think it should be very easy to implement.
Just curious...