Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Anysurfer reported that the NAV tag in language switcher block should be removed for accessibility purpose
<div id="<?php print $block_html_id; ?>" class="<?php print $classes; ?>"<?php print $attributes; ?>>
<?php print render($title_prefix); ?>
<?php if ($block->subject): ?>
<h2<?php print $title_attributes; ?>><?php print $block->subject ?></h2>
<?php endif; ?>
<?php print render($title_suffix); ?>
<nav<?php print $content_attributes; ?>>
<?php print $content ?>
</nav>
</div>
Comments
Comment #1
Pierre-Gilles Valcke CreditAttribution: Pierre-Gilles Valcke commentedComment #2
Pierre-Gilles Valcke CreditAttribution: Pierre-Gilles Valcke commentedComment #3
stefan.r CreditAttribution: stefan.r commentedRemoving it may break existing sites but according to their guidelines it is not necessary to remove it necessarily, what we can do instead is use
<nav role="navigation">
See: http://www.anysurfer.be/nl/blog/detail/html5-aria-landmark-roles-en-scre...
Comment #4
Pierre-Gilles Valcke CreditAttribution: Pierre-Gilles Valcke commentedI don't fully agree with https://www.drupal.org/node/2356187#comment-9250787
Het is een prima idee om beide te combineren:
<nav role="navigation">
.Merk op dat dit enkel gebruikt mag worden voor het hoofdmenu en eventueel het submenu.
Het is niet de bedoeling dat u elk groepje van 2 of 3 links in een nav-element plaatst.
Comment #5
bart.hanssens CreditAttribution: bart.hanssens commentedComment #6
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer and at Annertech commentedAccessibility is the preferred tag. Cleaning up the tags so the core topic maintainers don't have to monitor multiple tag queues.