4 ms·
Open up any webpage and count how many divs with no other purpose but to serve as CSS anchors there are. We traded in non-sematic tables for non-sematic divs.
by EdiX 11y ago
Open up any webpage and count how many divs with no other purpose but to serve as CSS anchors there are.
We traded in non-sematic tables for non-sematic divs.
- rimantas 11y agoExcept that div have no semantics by definition.
- nness 11y agoThe <div> element has no semantic meaning, screen-readers don't read them and they have no intrinsic behaviour unless associated with an aria tag.
- im3w1l 11y agoWhy couldn't we just have made non-semantic tables? In addition to the semantic tables, I mean.
- bonzini 11y agoDivs with display:table/table-row/table-cell _are_ non-semantic tables.
- e98cuenc 11y agoexcept divs lack colspan
- welly 11y agoThere's (almost) always a way round a problem. In the case of colspan, try this: http://jsfiddle.net/5cUW7/8/ http://jsfiddle.net/5cUW7/8/
- Springtime 11y agoI came across this issue recently and was surprised after all these years there still isn't colspan support. Ended up having to create additional containers when I should be able to style it using CSS.
- nness 11y agoWhich would actually be somewhat helpful, come to think of it...
- extra88 11y agoadding role="presentation" to a <table> element will tell screenreaders to treat the element and its required children as non-semantic. I still say using a table for layout (of non-tabular data) is should be a last resort but it's easy for me to say since making a layout is rarely my job.