Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the links just need to be longer vs a couple of words.

We are used to small areas, but the problem is that you end up with 'click here', like in the example. But if you linked the whole text, it's basically the same thing as adding aria.

IMO, most cases that I see using aria seem like a fix after the fact vs doing it the right way.

There are use cases for it, but in the case of the example, making the whole sentence a link would be good.

Regarding screen readers, you can have it read all links, which is why the 'click here' is an issue. So you want a balance. Change "for x, <a href=...>click here</a>" "<a href=...>for x, click here</a>"... ta-da?

You need to optimize for people using accessibility tools, but also for the people looking at the site...



> Regarding screen readers, you can have it read all links, which is why the 'click here' is an issue. So you want a balance. Change "for x, <a href=...>click here</a>" "<a href=...>for x, click here</a>"... ta-da?

No, you want the verb to be whatever "x" does or is for, not the action taken to get there. The action taken to get there is the same for all links regardless of what they're for. So this is a bad example simply because we don't know what "x" is so we don't know what a better verb would be.


It depends on x, right? For example, it could end up being, 'for learning more about Hacker news click here'.

I think that signals to visitor using screen readers and without, what that is and how to interact with it.

If someone with a screen reader is jumping through links, they'll get context for the link. A visitor not using it will see get the context since it's all highlighted together. Someone using a keyboard, the outline will highlight all of it.

I am just a keyboard user. I have no idea if this is the best way. But I think it gives the same info to everyone.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: