[wp-trac] [WordPress Trac] #30589: Comments navigation template tags
WordPress Trac
noreply at wordpress.org
Tue Jan 27 15:41:14 UTC 2015
#30589: Comments navigation template tags
-------------------------+-----------------------
Reporter: obenland | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 4.2
Component: Themes | Version: 4.1
Severity: normal | Resolution:
Keywords: has-patch | Focuses: template
-------------------------+-----------------------
Comment (by afercia):
We quickly discussed this in the Accessibility team meeting yesterday, our
concern is about 2 different issues:
1.
the total number of navigation landmarks in a typical page.
This should be raised in a separate ticket but just consider e.g. Twenty
Fifteen with one main menu, one social menu, a few widgets in the
sidebar... there would be 13-14 landmarks, with nested landmarks '''and 5
navigation landmarks'''. See screenshots:
https://cldup.com/n6o4tdWKr3.png
and
https://cldup.com/VzDECLO8uL.png
Just too many landmarks.
2.
The usage of a `nav` element for comments navigation. There's some debate
about this, we're open to discussion but please consider what the
specification says:
http://www.w3.org/TR/html5/sections.html#the-nav-element
Note: Not all groups of links on a page need to be in a nav element — the
element is primarily intended for sections that consist of major
navigation blocks.
What is "major" is matter of discussion of course. Specifically for
comments, they're a secondary content by definition. Whether you consider
them a "section" or an "aside", they're related to the main content but
they're not the main content. Thus, a ''secondary'' content having a
navigation with a semantic meaning of ''major'' doesn't look right to me.
As I said there are different opinions, we're open to discussion and we'd
really appreciate everyone's feedback, I'd just like to quote Mr. Bruce
Lawson:
You need to ask yourself why you’re marking something up as nav. I do it
to help users of assistive technology easily find important navigation, eg
site-wide stuff. If you mark up every link that goes somewhere in the site
as nav, it’s harder for such users to find the really important stuff.
-- http://html5doctor.com/avoiding-common-html5-mistakes/#comment-16949
--
Ticket URL: <https://core.trac.wordpress.org/ticket/30589#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list