Verbs in aria-label tell users this element leads to action
Then wouldn't that logic also apply to the visual link? shouldn't we use go to example page instead of just example page? Yet the internet seems to have agreed that having a properly styled <a> is enough information for the user to understand "if I click this, it navigates to what the link text says", so why wouldn't it be the same for screen-readers?
If a screen reader reads "Saved items, link", how is that different from seeing a blue, underlined text saying "Saved items"?
I think you're right when you say that we understand the verb behind a link because of its normalized style, but I feel like this is processed in the background by our brains. There is no effort once the standard assimilated and if the design is good.
So there is a notion of comfort here, and if I would need to use a tool that describes the interface I would prefer the description to be nice to the ears, more like natural language.
At the expense of 99% of the users, who already know how the web works and prefer a streamlined experience? Not convinced. It's not on the web to explain itself to every clueless user.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Then wouldn't that logic also apply to the visual link? shouldn't we use go to example page instead of just example page? Yet the internet seems to have agreed that having a properly styled
<a>is enough information for the user to understand "if I click this, it navigates to what the link text says", so why wouldn't it be the same for screen-readers?If a screen reader reads "Saved items, link", how is that different from seeing a blue, underlined text saying "Saved items"?
I think you're right when you say that we understand the verb behind a link because of its normalized style, but I feel like this is processed in the background by our brains. There is no effort once the standard assimilated and if the design is good.
So there is a notion of comfort here, and if I would need to use a tool that describes the interface I would prefer the description to be nice to the ears, more like natural language.
My mom doesn't know what a link is because she doesn't use the web. But she wants to start. So we have to be more caring to new users.
At the expense of 99% of the users, who already know how the web works and prefer a streamlined experience? Not convinced. It's not on the web to explain itself to every clueless user.