Problem/Motivation
It would be great if Views used HTML5 tags like <section>
wherever appropriate.
Proposed resolution
1. Determine which parts of the views UI need to support HTML5 tags (this attached flowchart could help) and update this issue summary accordingly:
- Field style settings
- Rewrite output in fields
- Custom field
- Custom header/footer
- ... think of more examples..
2. When we're done with specifying, implement new markup.
3. Check resulting styling in all core themes.
Remaining tasks
Task | Novice task? | Contributor instructions | Complete? |
---|---|---|---|
Update the issue summary | Instructions |
User interface changes
No immediately visible changes; the use of tags like <nav>
(unlikely?) would mean that assisted technology (screenreaders etc.) might experience some progressive enhancement which shouldn't affect existing functionality.
API changes
This could affect styling in third-party themes, so could constitute a much bigger change to the wider community, than it looks when seen within just Drupal core on its own.
Comment | File | Size | Author |
---|---|---|---|
#3 | sectioning-flowchart.pdf | 107.82 KB | martin107 |
Comments
Comment #1
dawehnerI think its a good task for a site builder to contribute
Comment #2
davidhernandezComment #3
martin107 CreditAttribution: martin107 commentedJust for reference
When deciding to use a tag, which is semantically more appropriate than div
Should it be article aside or section ?
This flow chart is a good starting point when trying to reach consensus.
Comment #4
dawehnerInteresting.
Comment #5
jp.stacey CreditAttribution: jp.stacey at Magnetic Phield commentedI don't think this is clearly defined enough at the moment—the list of possible changes is still open-ended—so I'm not convinced that it's ready for a novice, except maybe to rewrite and improve on the issue summary.
I've therefore tagged it as needing summary update. I've added a bit to the summary myself, but it would be good if we could get a clear idea of "what done looks like", and also how this might affect third-party themes that we can't test (and therefore whether or not it's a breaking change.)
Comment #6
emma.mariaRemoving the 'Novice' tag because of issues raised in #5. This would be a good issue that a Novice could work alongside a more experienced person however.