Usage of Headings
I've posted a couple times and got various feedback on projects, one of the things I always received feedback on is headings. Often times that I shouldn't use one. So for arguments sake here's a use case. Would someone please walk me through what parts are improper?
13 Replies
i dont see anything wrong in that
i would just avoid having any heading inside a link, but that is me
for example, the <h3> inside the <a> would cause it so whitespace is also a link, which can be confusing and frustrating
So would it be better to have a <p> tag instead?
NO
Or no tag?
just put the link inside the <h3>
and dont worry about the link being repeated
but, this depends on what you want
if you want a card to be clickable in it's entire area, what you have is good
but you have to make it super explicit (through the design) that everything is a link
I've noticed a lot of product cards are clickable through their entirety so the user doesn't have to be precise when clicking.
But I think it's also a bad screen reading experience to go through:
For each product and kind of wonder if
is easier. I haven't been able to find a good article on accessibility and HTML structure for e-commerce usage.
you can try it yourself
if you get irritated by it, imagine how bad it is for a blind person
if you can navigate it with your eyes closed, then you're doing it right
you can try multiple screenreaders in multiple browsers
i've been testing with microsoft narrator and i want to defenestrate my company laptop
I feel the sentiment. I've also been testing with a narrator and it's impossibly frustrating.
it is irritatingly annoying
but getting back on topic
your headings seem perfectly fine
as long as you have a proper architecture, and it all makes sense, you're very likely doing it correctly
The trick for this is to use
position: absolute
on a pseudo-element for the link, and have it cover the entire card.that's what i usually do for nested links
something like:
Gotcha, that's a lot cleaner of a solution. Thank you both