Redmine

Or even more: we can omit the whole description block if there are no description and no attachements.

I don't think that readers actually read the css classes so 2. would be useless for that purpose.

I would also favor having the label. Currently, everything in Redmine is labeled (which I consider a good thing). I don't think we should remove that trait.

Also, this view is often extended by plugins to add additional sections. I consider it good practice to label these sections to properly distinguish them and define their meaning. In my eyes, clarity beats saving a few vertical pixel every day.

Holger Just wrote:

I would also favor having the label. Currently, everything in Redmine is labeled (which I consider a good thing). I don't think we should remove that trait.

That's not correct. The other descriptions are not labelled (eg. project, versions...).

Eric Davis wrote:

Actually, I'm going to argue against that. To non-visible users it's impossible to tell where the description is (e.g. blind or screen readers). Since r4264 it appears as a 'wiki' div with no other hint as to it's content:

Look at any other web page: product info, articles, blog posts pages, etc. They do not have any label for the content part. Just heading (h1..h6 followed by content).

Also, if we are talking about the semantics then instead of <table class="attributes"> here should be definition list (<dl>, <dt>, <dd>).

Dmitry Babenko wrote:

Look at any other web page: product info, articles, blog posts pages, etc. They do not have any label for the content part. Just heading (h1..h6 followed by content).

And the headings are exactly what he are talking about here. The tag-type might have been wrong (should indeed be a h2 or h3), but the label serves the purpose of a header.

Jean-Philippe Lang wrote:

The other descriptions are not labelled (eg. project, versions...).

Projects have the Overview header directly above the description. In the roadmap, it is indeed missing. But there is not much that can distract from the description there.

Eric Davis wrote:

I've talked to an associate of mine, Brian P. Hogan, who deals with a lot of web accessibility and screen readers. His recommendation was to use a header tag since that is what is actually presenting (like what Dmitry Babenko suggested too).

And then we would hide it via css ? The first request was about that, not about accessibility or semantics... I don't understand arguments about accessibility where everyone focuses on blind users only, without thinking of lambda users (not specific to redmine though).

Jean-Baptiste Barth wrote:

And then we would hide it via css ? The first request was about that, not about accessibility or semantics... I don't understand arguments about accessibility where everyone focuses on blind users only, without thinking of lambda users (not specific to redmine though).

I think removing it was wrong in the first place and having a header or label here was right thing to do (and a <p><strong>Description was only half right).

github's diff for those who still would like to remove it totally.