Live data from Hacker News

Show HN: Hint.css v2.0 – Pure CSS tooltip library

kushagragour.in

21–30 of 64 posts

Re: Show HN: Hint.css v2.0 – Pure CSS tooltip library

#21
post #8

How accessible is this approach to screen reader users and people who rely on keyboard interaction alone? Edit: A quick test reveals these tooltips are not accessible at all.

Keyboard accessibility should arrive soon: https://github.com/chinchang/hint.css/pull/111

Re: Show HN: Hint.css v2.0 – Pure CSS tooltip library

#22

On one of the very first tooltips at the very top of the landing page (the download button), my Chrome v48.0.2564.97 browser renders a very thin gap between the triangle of the tooltip and the content rectangle. Not a great first impression...Is anyone else seeing this? I suspect it has something to do with pixel percentages.

Ditto. I was also zoomed at 150%, zooming in to 100% makes it go away.

Still worth fixing if possible, since many users browse at non-100% zoom.

Re: Show HN: Hint.css v2.0 – Pure CSS tooltip library

#23
post #8

How accessible is this approach to screen reader users and people who rely on keyboard interaction alone? Edit: A quick test reveals these tooltips are not accessible at all.

Isn't there a tag for links similar to the description tag for images? If so, you could just enter the tooltip there as well.

No. Well, you could use aria-describedby but that has to refer to a separate element. There’s no generic aria-description.

Re: Show HN: Hint.css v2.0 – Pure CSS tooltip library

#24
post #22

On one of the very first tooltips at the very top of the landing page (the download button), my Chrome v48.0.2564.97 browser renders a very thin gap between the triangle of the tooltip and the content rectangle. Not a great first impression...Is anyone else seeing this? I suspect it has something to do with pixel percentages.

Ditto. I was also zoomed at 150%, zooming in to 100% makes it go away. Still worth fixing if possible, since many users browse at non-100% zoom.

> "many users browse at non-100% zoom"

This sounds dubious. Do you have a source for this?

Re: Show HN: Hint.css v2.0 – Pure CSS tooltip library

#25

Earlier quoted context omitted.

Isn't there a tag for links similar to the description tag for images? If so, you could just enter the tooltip there as well.

No. Well, you could use aria-describedby but that has to refer to a separate element. There’s no generic aria-description.

You could use aria-label potentially, but it has fairly scrict semantic connotations as a label for an input, I believe.

Re: Show HN: Hint.css v2.0 – Pure CSS tooltip library

#27
post #25

Earlier quoted context omitted.

No. Well, you could use aria-describedby but that has to refer to a separate element. There’s no generic aria-description.

You could use aria-label potentially, but it has fairly scrict semantic connotations as a label for an input, I believe.

aria-label is totally cool for not-input's: https://www.w3.org/WAI/GL/wiki/Using_aria-label_to_provide_l...

Re: Show HN: Hint.css v2.0 – Pure CSS tooltip library

#28

On one of the very first tooltips at the very top of the landing page (the download button), my Chrome v48.0.2564.97 browser renders a very thin gap between the triangle of the tooltip and the content rectangle. Not a great first impression...Is anyone else seeing this? I suspect it has something to do with pixel percentages.

It is a gap only if you zoom in, at 100% it appears as a grey line: http://i.imgur.com/6uCb0km.png

Chrome 48, Win 7

Re: Show HN: Hint.css v2.0 – Pure CSS tooltip library

#29
post #22

Earlier quoted context omitted.

Ditto. I was also zoomed at 150%, zooming in to 100% makes it go away. Still worth fixing if possible, since many users browse at non-100% zoom.

> "many users browse at non-100% zoom" This sounds dubious. Do you have a source for this?

Personally I rarely browse at 100% zoom. I magnify each page until I only have ~20px of margin and no whitespace.

Given there are tens of millions of people on the Internet, even if a small amount like 0,01% did it, it would already be "many people".

I would however appreciate some analytics data on it to have a better idea.

Post reply on HN