Caius Durling wrote: > > On 24 Nov 2008, at 15:45, Chris Meller wrote: > >> I'd like everyone to re-vote after having read my arguments. Also, >> please take a minute or two to explain why. "It's ugly" and "It should >> never be done" aren't arguments that help to change my opinion, they >> just override it. > > +1 for native widgets. > > For you it might make sense to have unity across all browsers, but its > an accessibility nightmare for other people that aren't expecting > something to look different.
The graphic change has absolutely no impact on accessibility, because the underlying tag is a button. The concept you're thinking of is familiarity, which affects usability. To say the button look causes a "nightmare" is quite a bit of hyperbole. I've considered the usability of native buttons versus custom ones: In the column for native buttons: * Users recognize a button during scanning without difficulty In the column for custom buttons: * Can be color-hinted for improved feature recognition * A similar look to other already non-standard controls in the Habari UI will extend to them the concept of interactive control Other mentioned styling issues, such as subtlety of the hover state and matching to Habari UI, can be addressed only using a custom button. Many reasons why native buttons are usually preferable to custom ones are inapplicable to the Habari admin, because the admin UI is not designed to be scanned by passing visitors. Given that it's not too additionally difficult to recognize a custom button as a button during scanning, and the custom buttons can provide improved usability over their native counterparts, I'm not persuaded that the native buttons are the best solution for Habari usability. Owen --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
