OK, there are a lot of assertions here that I don't know much about so I am trying to summarise.
What is it about a button that makes it accessible and usable, or otherwise? I assume that the button tag is needed for non-visual purposes - If true then that is a non-issue as it is used. I assume that it is necessary for a button to look and act like a button, i.e. depth, caption, hover, press, are there any other attributes that make a button a button? Can any critical aspect of what makes a button a button not be delivered with a non-native solution? Is there sufficient similarity across the web (as viewed from each platform) to justify the assertion that familiarity outside a specific application is an issue? - The examples given would suggest not, and the fact that the new WP uses entirely non-native buttons would suggest that it isn't a problem. A lot of usability work has gone into the new WP so there may be lessons to be learned from it. Is there evidence that users have an expectation one way or another as to how a button will look? In the absence of evidence we just need to admit ignorance, or get some evidence. If these are all the relevant questions then I don't see a strong reason why it should not be done. My concern is to have a pleasant, and thus productive, experience. That obviously includes usability, but doesn't preclude graphical changes. I will say +1 for a really good non-native version +0 for native -1 for a bad non-native version. 2008/11/24 Owen Winkler <[EMAIL PROTECTED]>: > > Michael Bishop wrote: >> >> If we are going to argue for accessibility, then we should apply that >> across the board, not subjectively based on the personal tastes of a >> few who care to voice their preference. > > For what its worth, I think that the link color on the plugins page is > just an accident/oversight, and wouldn't mind seeing it styled > differently. If I had to choose to style the buttons or the links, I'd > certainly choose the links right now - they're unusable. > > 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 -~----------~----~----~----~------~----~------~--~---
