Seems like they could be essential to the content, but position is unrelated. . Personally, this is what I would use: It was a genuine attempt by bruce to provide what he thought would be a good alt text, so he should be commended not pilloried for his effort.

Using role=”img” on figure conveys to accessibility APIs there is an image and associating the figcaption content using aria-labelledby conveys the accessible name value for the img to accessibility APIs. And yes it’s a little bit extra work but it’s very minimal.

just hoping every browser starts supporting html5 and people move into them.

Copyright © 2020 HTML5 Doctor. The caption will be “Mayor of Casterbridge opens a new Lidl supermarket”.

So this is nothing to be confused with in HTML. If we were to adopt all of ARIA natively into html5 then ARIA would not have anything that HTML5 does not. In this example, we said it’s “a story simply about a dignitary opening a new branch of Lidl” , so I think that in this example there is too much description here. Show your working out. I am getting a headache. have a look at Investigating the proposed alt attribute recommendations in HTML 5 for further info about this. Currently with XHTML 4.x and CSS 2.x In order to have a caption be right justified with an image (like the way your ‘Submit Comment’ button lines up with the right side of the ‘Enter Comment’ box) , the following conditions need to be met: 1. Is he hiding in the leaves ? Before I resorted to using a div->image with a div->caption nested inside to express these kind of structures.

Just remember to make sure it’s the most appropriate element for the job. Why? You can also use , and remember to use < and > for brackets. Too much information, but would be a good runner up. To me, a new element like figcontrols would make sense, but I don’t think that will happen.

I don’t know if the p is unnecessary or not, but that’s not my main issue with this option anyway. In the end I’d like to vote for combining C and D. I don’t think that
should include a

since this is such a short caption. He would be much portlier if you corrected the aspect ratio.

@Steve Faulkner – Is it really true that img with no alt attribute is not presented to AT? I am sure that this will work, but would it be correct semantically? Thanks for the info. We covered
This article was written by Richard Clark.

…or at least that’s the impression I’ve got :). (From HTML5 Boilerplates), Also, while Bruce’s mum thanks you for complementing her photography, she apologies for the photo’s subject — sadly her son didn’t inherit her good looks ;). This should not be necessary when browsers implement

I don’t think it matters.

Regular readers will know that a new element was recently introduced, namely


But the remaining options are too short to provide value. The

element is optional and can appear before or after the content within the
. A p element is flow content but not phrasing content.
Offer Title
Or a better question may be: The longer the broader development community, such as the HTMLWG, ignores accessibility, or thinks that others like the PFWG / WAI will take care of it for them, the longer we will need technologies like ARIA to fill in the blanks.

Traditionally, the author adds the documents to the “resource gallery” (to use a CMS term) and then links to them in an unordered list (if you’re lucky). This bit of the spec is quite fiddly, but there is a nice Venn diagram under Kinds of content in the Overview document which shows how the content types relate to eachother.

You can also use , and remember to use < and > for brackets.

The alt attribute is almost always poorly written for screen readers providing bad UX. If

were to be associated with
, then it shouldn’t be contained by it.

HTML5 accessibility is not very well supported, it will be in the future, but ARIA works today. If you have multiple sized images that you want centered in a containing element but want the caption to be right (or left) justified with the varying image sizes will you STILL have to have a width declared? @Nathan — yep, the spec says “Content model: Flow content”, which is basically most elements, including



It does impose some extra difficulties with wysiwyg editors and such, as I would suggest using the figure element for every image that could have a caption (future-proof coding and such!). Bobby: Just let me add this: the way the spec.

Yes, the feature

in html5 is great, but it seems that few sites and blogs are using, here in Brazil (where I live), for example, few, if not none, blogs and websites use this feature and think it should use more, I always use this tag on my blogs and projects, trying to make the site more semantic as possible. It won’t hurt your site, it won’t hurt your users.