I have to say that I think a table would be perfectly acceptable, as well, of course. Semantics aren’t really a fixed feature: for complex data sets, there are commonly multiple appropriate solutions. I could go either way on this particular question!

It’s important not to worry too much about whether you’ve chosen the “right” answer in semantics. Basically, you can always choose to use the wrong element — - but choosing the right one is much more difficult.

If you can explain your reasoning for a specific element choice from a semantic perspective, you’re fine.

The immediate approach was to put this together as a table in which the headers were “Feature” & “Benefit”, but came to the conclusion that this is not tabular data and that, being a list of features & summarised benefit, it would be more semantically correct to present them as a list.

We have never used definition lists before and are not sure whether this would be the right place to use them.

So we would have, as an example, dt of ‘speed’ with a dl of ‘so you can get from a to b in time for dinner’. Would this be correct and, if so, what about what we would have used as table headers (i.e. feature & benefit) - do they also fall in this category?