Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I am creating a list of links which have the following in them:

  • link title and url
  • a comment about the link
  • a date that the link was posted

I wish to do this using accessible best practice, but also would like to avoid using tables because I'd like to keep the site responsive (mobile/tablet/desktop) - and although you can create accessible tables and responsive tables I'm not sure that you can have a responsive and accessible table.

There is an answer here, but it doesn't fully help me. It states helpfully that "Basic question you should ask yourself: do you need rows and columns? Do you need some kind of cross-referencing and/or sortable on different properties of the individual items? In that case, use a table. Otherwise, use an unordered (or ordered) list."

For my example I'm not giving the user an opportunity to sort the data, and as for cross referencing I'm not sure if this applies - but am happy to take advice on that.

share|improve this question
    
Regarding Accessibility on screen readers: unless you actually do test (& fix) the screen reader accessibility, your table may just be unreadable for a screen reader, see stackoverflow.com/questions/21586478/tables-and-screen-readers –  Adrien Be May 15 at 11:36

3 Answers 3

I think you are answering yourself: if you don't need rows and columns, then you don't need a table.

The table could be responsive and accessible, but in this case it would be unnecessary. Maybe the best list you could use is a definition list that allows you to tag a title and a definition (the comment).

This would be the result (without any style): view on jsfiddle.

share|improve this answer
    
While I love the semantics and concept of definition lists, note that--at least historically--they haven't been well supported by accessibility software such as JAWS (but that's not necessarily a reason not to use them, of course...) –  DA01 Feb 10 at 19:09
    
I knew that the problem was solved in JAWS 6, but the problem seems to be the correct use of DL tag. For example, Lynx has problem when you write two descriptions for only one title (and according to the WCAG you have to write one description for one title because dt+dd is considered a unit). –  panna Feb 11 at 9:53

Actually I think it depends on how much items there is and how different they are. If there is between 1-10 links and their titles, urls and coments are going to have somewhat the same length then you could display them as a list.

But I don't think so, so you probably should use a table to increase readability. The fact is that your users are going to browse/scan your list and search for interesting things and a table make the eyes' work easier.

Below is an example of the kind of list you are talking about. Let's say the user is searching for an url.

enter image description here

Please note that this is mockup, there is lots of ways to design a nice table.

share|improve this answer
    
For what reason would a table increase readability? Just because it is neater doesn't mean it is more readable. Personally I find the list example you give far more readable. –  Alnitak Feb 11 at 12:32
    
@Alnitak I edited my answer to make it clearer. Actually, tables makes the eye's work easier. –  Zhouzi Feb 11 at 15:17
    
Your diagrams make your point much clearer. However, a question about readbility still stands. Your "eyeline" diagram on the table illustrates that the URLs are more easily viewed as a block. Similarly, the eye can easily see other columnar data as a block. But would easy visibility of columns would better help the reader, or the rows? For me personally, I would prefer to see information relating to a particular link grouped together, i.e. I'm looking for row information, and I find that much easier not in the table. –  Alnitak Feb 11 at 15:26
2  
Readability isn't necessarily the same as 'scannability'. It all comes down to what the priority is here. –  DA01 Feb 11 at 16:15

When you said accessibility, do you mean just making easy to read or are you planning to cater to people with disability?

On making it look pretty and easy to read, list can be made to look like tables and vice versa - except of course if you plan to have columns with varying widths on every row then tables wouldn't be too good.

If you are however talking about accessibility in terms of disability, can I suggest you an article. It's a little old, I should say but nonetheless useful: http://snook.ca/archives/html_and_css/definition-lists-v-tables

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.