Document accessibility features in Views

This seems like useful information to convey, but we need to figure out where to put it.

hook_help() standards say we have an "About" section (describing what the module does) and a "Uses" section (describing how to use the module).

This sounds like an About.

I suggest adding a section at the end of the About section, like:

---------------
The HTML output of the Views module has several features to promote accessibility:
- (information about tables)
- etc.
---------

Note: We do not want to talk about the evolution of Views. So do not say it has been "improved" or that it's better than previous versions, or mention Drupal 8 in particular. Do not use marketing language, or try to convince anyone that it's excellent. Just document what it currently does.

And we do not need to say what Views are used for in this paragraph/section. That is covered in other sections of the hook_help.

Hm. This sentence is garbled:

Views tables have include semantic headings/id references for improved accessibility.

Also, what are "headings/id references"? I do not know what this means, and "ID" should probably be all-caps? ("id" is a psychological term, while "ID" means identifier/identification).

And this sentence:
Views tables are used within the Drupal admin interface, but also for custom views.
why is this relevant?

The header "Expressing table accessibility"... "expressing"? This verb doesn't make sense to me. What are you trying to say?

I think an empty patch can be committed at any time, but git doesn't allow that :P

Sounds reasonable!

I still don't like the header here. It says "Documenting table accessibility", but that is not what someone using this feature is doing. They are providing information about a table, for purposes of accessibility, but they are not documenting that the table is accessible.

I also think this sentence needs a comma:

Using id and headers attributes data cells are automatically associated with header cells.

And we shouldn't be using & in place of "and":

Both the caption & summary ...

And... fundamentally, this documentation doesn't really tell me what I need to do in order to make a table accessible. What attributes do I need, and where, and how do I add them?

Hmmm... Our standard for Uses items says they should start with a verb. Perhaps "Improving table accessibility" would be a good header?

Using id and headers, attributes data cells are automatically associated with header cells.

Um... that is confusing. Maybe the comma doesn't belong there... and maybe it would be better to say "Data cells are automatically associated with header cells when their ..." um... really I have no idea what it means actually.

Maybe this would also be clearer if formatted as a UL list within the DD. For instance it could say:

Views tables include semantic markup to improve accessibility:
- (item 1)
- (item 2)
etc.

This patch I like. Reads very well, seems clear. I assume that it's accurate (sure looks reasonable). Thanks!

Committed and pushed to 8.x. Thanks!