- From: Gunderson, Jon R <jongund@illinois.edu>
- Date: Tue, 30 Apr 2013 14:05:40 +0000
- To: Ian Yang <ian@invigoreight.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Article will probably at some point will be a landmark in HTML5, so it would be better NOT to put them in a list, but inside a main landmark. Give each article a role="region" and a label to support landmark navigation. The role="region" will make them part of the landmark navigation in current assistive technologies. For example: <div role="main"> <article role="region" aria-labelledby="a1"> <h2 id="a1>Title of article 1 ...</h2> <p>Content of article 1Š </article> <article role="region" aria-labelledby="a2"> <h2 id="a2>Title article 2 Š.</h2> <p>Content of article 2Š. </article> Š. </div> On 4/30/13 8:47 AM, "Ian Yang" <ian@invigoreight.com> wrote: >Typically on the front page of a blog, there are several teasers, and >each teaser is an <article>. And usually blog comments are markuped >using <article>s, too. > >My concern is: Is it a good practice to put those <article>s inside ><li>s? I used to do that because those <article>s together look like >they are presented in a way of a certain amount/quantity. So when it >comes to listing a certain amount/quantity of elements, <ul> and <ol> >are the best choices. > >However, maybe I need to reconsider that because putting <article>s >inside <li>s seems to be a misuse of <li> element. Especially when a >blog comment is lengthy. And I also want to take accessibility into >account. I'm not sure if doing that causes confusions to assistive >technologies users or not. > > >Kind Regards, >Ian Yang >
Received on Tuesday, 30 April 2013 14:06:50 UTC