2007/3/23, Drew McLellan <<a href="mailto:lists@allinthehead.com">lists@allinthehead.com</a>>:<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On 22 Mar 2007, at 17:14, Andy Mabbett wrote: > I suggest that this rule be adopted, for *all* microformats, unless > there are good reasons for specific exceptions: > >         Where an element contains only an image element, and the > parser >         is expecting text, the alt text of the image should be used. tbh I though that this was already a rule. It's a rule native to HTML, so we therefore inherit it for free. It certainly seems like common sense, and I believe hKit already behaves in this way. drew. _______________________________________________ microformats-dev mailing list <a href="mailto:microformats-dev@microformats.org"> microformats-dev@microformats.org</a> <a href="http://microformats.org/mailman/listinfo/microformats-dev">http://microformats.org/mailman/listinfo/microformats-dev</a> </blockquote></div> I disagree. By using the h1-tag you are already announcing that the enclosed data will be text data, just as the img-tag announces upcoming picture-data. So, even the use of the img-tag within any kind of heading is semantically incorrect html. In addition, the alt-attribute is meant as, in this case, non-text-equivalent to compensate reading-disabilities (More here: <a href="http://w3.org/TR/WCAG10-TECHS/#def-text-equivalent">w3.org/TR/WCAG10-TECHS/#def-text-equivalent</a>), not to add additional or even false information to a non-text element. The reason for wanting to place an img-tag within a heading is of course a pure matter of style, which can easily be achieved by one of the numerous Image-Replacement techniques (Actually they're Text-Replacement techniques. A list you can find here: <a href="http://mezzoblue.com/tests/revised-image-replacement">mezzoblue.com/tests/revised-image-replacement</a>) which add the desired image as a background defined in the stylesheet, rather than polluting the html file with misleading markup. So, the problem of your example is that I believe your approach is wrong and unnecessary. Sid.