Page MenuHomePhabricator
Create Task
Maniphest T243887

Make TOC better accessible
Closed, DuplicatePublic
Actions

Description

On both desktop and mobile TOC should be equipped with:

role="navigation"

TOC will be brought to immediate attention of blind users. Screenreaders are supposed to offer in first place, after alerts, the navigation elements pointing to related other pages and the major navigation within the page.

See navigation@WAI-ARIA.

A similar concept is <nav> in Grouping content@HTML. The role="navigation" attribute is telling the screenreader that this <div> element is playing the same role.

<div id="toc" class="toc" role="navigation">

This is a follow-up of T26659 from 2010/2016.

Related Objects

Event Timeline

PerfektesChaos created this task.Jan 29 2020, 10:52 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 29 2020, 10:52 AM
TheDJ subscribed.Jan 29 2020, 12:15 PM
PerfektesChaos added a comment.Feb 4 2020, 11:36 AM

(+) Some Screenreaders do generate a TOC already from document headlines in the same way as MW does.

However, even those will benefit from labelling our TOC as navigation element rather than new and independent content. Furthermore it might be cut from text flow and section sequence.

TheDJ closed this task as a duplicate of T139221: Make generated table of contents a navigation region.Feb 4 2020, 12:04 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits