#[kevinmarks]You can put the url around the avatar, and use alt for the name so that is the h-card
#[keithjgrant]Oh cool. So a 'p-name' on an <img> refers to the alt?
#[keithjgrant]On the grid issue, hopefully subgrid & the level 2 spec will mature soon and present a better way
KartikPrabhu joined the channel
#KartikPrabhu[keithjgrant]: sknebel: wrapping each comment with a <div class="comment"> and setting it to "display: contents" works. However I think only FF supports this for now
#KartikPrabhu[keithjgrant]++ for documenting these problems
#Loqikeithjgrant has 2 karma in this channel (16 overall)
#KartikPrabhu[keithjgrant]: yes p-name on img will pick up the alt. But that would have accesibility issues as the comment-author name will be announced twice on screen-readers (I think)
#ZegnatYes, it will be announced twice. You could theoretically block the author name text from being read with aria-hidden though. But I am not sure you really want to go to that trouble
#[keithjgrant]I think Chrome added display: contents also. That might be the way to go, with a reasonable column width hard-coded as fallback for other browsers
#KartikPrabhu[keithjgrant]: yes using @supports should be good here
#ZegnatI’d almost be more inclined to just add a <data class="u-photo"> within the h-card and not try to force extra semantics on the IMG element
#KartikPrabhuZegnat: yes. that sounds better. But also "hidden data" problem
#ZegnatUsing the alt tag for p-name is, in a way, also hidden data imho
#sknebelyeah, both alt= and data are hidden, but seems hard to avoid
#ZegnatEspecially since the name is right next to it.
#ZegnatSo either way you are duplicating data (either IMG URL or name text)
#ZegnatAnd I would rather not overload the IMG element
#ZegnatI am not actually sure what the recommended alt text for display pictures is these days. But I bet there is one. Better off sticking with that
#KartikPrabhuZegnat: for purely presentational images (which this would be ) it is alt=""
#ZegnatI wouldn’t say the photo’s of people’s faces are decorative
#KartikPrabhuI would if the name is right next to it
#KartikPrabhuif it were only an image I would put the name as alt
#ZegnatI once read an article by a screenreader user who said alt="" is very annoying for these things because people around them would refer to images. And even if they couldn’t see it, they wanted to know the image was there.
#ZegnatWhich is why I think how much a display picture of a person counts as purely decorative and not-for-the-user is debatable.
#ZegnatBut again, would need to find someone who wrote about the topic to know the current best practice. Don’t have it at my fingertips
#[keithjgrant]I wish there was a way to say the mf of element X is associated with the h-* defined by element Y. Kind of like a <label>’s for attribute can reference an arbitrary <input> on the page.
#KartikPrabhu[keithjgrant]: you are getting into Schema-type stuf now! :P
#ZegnatBTW, [keithjgrant], I know some people don’t like doing this but you don’t have to use an h-card on the h-entry and can instead just use u-author
#ZegnatSo then you only need to be able to nest that one URL somewhere in the h-entry. There is some discussion about the authorship algorithm that might then even allow matching an h-card *within the current document* if it has the same u-url.
#ZegnatSo you could have h-card outside of the h-entry, have u-author on h-entry match the u-url on the h-card, and some parsers will pick that up no problem
#ZegnatI believe X-Ray does it that way right now (possibly, maybe, discussion pending, ... ;) )
#aaronpkI thought that was all solidified in the authorship algorithm?
#sknebelsee the codepens above - markup examples where fitting h-card under the h-entry wasn't easily possible
#aaronpkon my own site i've solved that by using a hidden element to set the u-author property inside the h-entry
#aaronpkjust to link the two together for the authorship algorithm
#sknebelso it goes into "fetch their homepage" mode instead of getting the info locally
#sknebelI think that was what zegnat suggested: if there is an h-card in the current document that can provide details, use that instead of fetching an additional document
#aaronpkno, I also have an h-card on the page, but setting the u-author property tells the authorship algorithm to use the on-page h-card