Eric @martijnvdven There shouldn't be a problem with the screen readers - they will read the page as follows: PlaceNameA: n*[date:status], PlaceNameB: n*[date:status], PlaceNameC: n*[date:status] - If you look at the source all the tables are very semantic. This is a mobile first approach really, the tricksy bit is how it displays on desktop.

Martijn Except modern screen readers interpret CSS and will not read elements that have their display set to none, this has led to such fuzzy CSS as seen in Bootstrap: github.com/twbs/bo...

Eric Excellent link, now updated.

Martijn While we are on an accessibility roll, maybe update the boundary map and expose some good alternative content to screen readers? sitepoint.com/tips...