Live data from Hacker News

Use Google+ to Improve Your UI

pixify.com

21–30 of 46 posts

Re: Use Google+ to Improve Your UI

#22

One interesting difference: Google just uses for their buttons instead of tags or even . They also don't set cursor: pointer (the hand) for them. Any UI people want to comment on the best practice for cursor styles? I always figured pointer should be used for all buttons or links that have an action attached.

This is absolutely terrible for accessibility. Screen readers will not handle these buttons properly leading to a significantly more difficult experience. James Edwards actually talked about this at The Highland Fling conference a few weeks back.

Good point on accessibility. Anyone have links to making your UI accessible (including buttons)?

Re: Use Google+ to Improve Your UI

#23
post #11

It looks pretty nice but the use of background gradients is inconsistent. The buttons with a background image have no gradient but the other buttons do.

Nice catch. Know of an easy workaround to this?

Nope, I don't think there are any (the CSS3 workarounds can be tricky with custom padding/margin). Google consistently uses nested elements and I think for the next few years that's the only solution that's going to work well cross-browser.

Re: Use Google+ to Improve Your UI

#24

One interesting difference: Google just uses for their buttons instead of tags or even . They also don't set cursor: pointer (the hand) for them. Any UI people want to comment on the best practice for cursor styles? I always figured pointer should be used for all buttons or links that have an action attached.

Yes, use pointer. I don't know why G doesn't, but that is not good practice. There should be a visual indication that an object can be clicked, other than a highlighted border.

Re: Use Google+ to Improve Your UI

#25

No, no, no! Please don't let GMail and G+'s new look become a new fad. The white space around every element is very wasteful and obnoxious. Not everyone has huge resolutions and those that do don't appreciate having to scroll several times just to see past the first 4 or 5 entries in a list view.

Okay, thanks. I was just about to write the exact same thing (although I may have been more dramatic complaining about the huge amount of unnecessary white space that fills my small netbook screen).

The new buttons however are quite nice and simple. There should be a hint of 3D though, to make them feel more "press-able". Other than that, I am okay with them becoming wide spread on the web, just don't surround them with so much wasted space.

Re: Use Google+ to Improve Your UI

#27
post #25

No, no, no! Please don't let GMail and G+'s new look become a new fad. The white space around every element is very wasteful and obnoxious. Not everyone has huge resolutions and those that do don't appreciate having to scroll several times just to see past the first 4 or 5 entries in a list view.

Okay, thanks. I was just about to write the exact same thing (although I may have been more dramatic complaining about the huge amount of unnecessary white space that fills my small netbook screen). The new buttons however are quite nice and simple. There should be a hint of 3D though, to make them feel more "press-able". Other than that, I am okay with them becoming wide spread on the web, just don't surround them w…

I wrote a userscript that dials down the whitespace, if anyone's interested: http://userscripts.org/scripts/show/105891

Re: Use Google+ to Improve Your UI

#29

One interesting difference: Google just uses for their buttons instead of tags or even . They also don't set cursor: pointer (the hand) for them. Any UI people want to comment on the best practice for cursor styles? I always figured pointer should be used for all buttons or links that have an action attached.

This is absolutely terrible for accessibility. Screen readers will not handle these buttons properly leading to a significantly more difficult experience. James Edwards actually talked about this at The Highland Fling conference a few weeks back.

The Google buttons do use the ARIA role="button" attribute, which should let them work in screen readers.
Post reply on HN