All 14 Table of Contents sections
Extras
Show a floating button puts a small button in the corner that reopens the list from anywhere in the article, once the list in the post has scrolled away. The list in the post does not move — the button opens a copy, at the entry for the section being read. Choosing an entry in it takes you to that section and closes the panel.
Button shows is what the button says. With The section being read it is a pill naming the section the reader is in, "3 · Choosing a size", which changes as they scroll, and above the first heading it shows the list's title. The number is the one the list gives that entry, in whatever numbering the list uses: 3, 1.2, III, or none at all. A long heading is cut short with an ellipsis, and the pill is never wider than seven tenths of the screen, so on a phone it leaves the other corner to whatever button is there. It shows its words on a phone too, which is where the list scrolls away first. With The list's title it is the button as it always was: the title, and on a phone its icon alone. Either way it is at least 44 pixels each way, an easy target for a thumb.
A screen reader or voice control knows the button by the words on it: the list's title, and with a section showing, the title and the section, "Contents: 3 · Choosing a size". Nothing is read out as the reader scrolls; the name is simply up to date when the button is reached. For a reader whose device asks for less motion the pill changes width at once rather than sliding, and on a right-to-left site it sits in the mirrored corner. It follows the reader even with Highlight the current section off, and then marks nothing in the list.
New sites start with the section being read. A site that already had the plugin keeps the list's title until you choose otherwise, since the change is one your visitors would see: the Extras panel says so, and while the floating button is on, the Dashboard asks once, with Switch it on and No thanks.
Show a back-to-top button (under Navigation) appears once the reader has scrolled a screen's height, and until then cannot be tapped or tabbed to. Pressed from the keyboard, it takes the focus back up as well, to the post's title (or to the contents list when the post shows no title of its own), so the next Tab carries on from the top of the page.
Distance from the bottom (px) raises both buttons, the pill too, for a corner something else already holds: a chat bubble, or another plugin's button such as the Dark Mode switch. Both also move up by themselves above a bar pinned to the bottom of the screen by our other plugins, such as the Social Share phone bar, and above our Lucky Wheel launcher in the same corner, and on a right-to-left site they sit in the mirrored corners. However far the floating button has been lifted, the list it opens is made that much shorter, and shorter again for what is fixed across the top of the screen: the WordPress toolbar when you are signed in, and a shipping bar or cookie banner from our other plugins pinned there. So on a phone held sideways it opens below those, title first, and scrolls inside itself, as long as the screen has room above the button. If the button is lifted so far that it nearly reaches the top, lower Distance from the bottom (px).
Show a reading progress bar draws a thin bar across the top of the window and inside the list. At the top of the window it sits under our Free Shipping Bar when that is pinned to the top, and under our cookie banner while it is open there, rather than behind them.
Show the estimated reading time counts at about 200 words a minute, in any language — accented words count once, and a language written without spaces is counted by its characters. Show the number of sections puts the count beside the heading. Show a filter box adds a search box, but only once the list is long enough to be worth filtering — a filter above six links is more work than reading them. When typing pauses, a screen reader is told how many sections match, or that none do.
All four are off by default. They suit a long guide and clutter a short one, so the decision is yours rather than ours.
Still stuck? Ask the developers who wrote it. We aim to reply within one business day.