[KevinH]

Hi Doitsu,
Thanks. That is a definite possibility.

But how would this be different from a clips bar that is dedicated to doing the same thing? No pulldown in needed then at all, and all are available to be clicked at any time so no "memory" is needed.

And does anyone use the aria-labelledby approach and place an id on the h1 tag it encloses?
And why hardcode a class name like "chapter" at all?

Making the [h*] button remember its last state is a good idea I will look into. But I do not like the idea of it changing its function for epub2 and epub3 given the tool bar itself works on all epub types now.

Perhaps a new top-level menu called "Add Accessibility" that could easily be made context sensitive and only be shown under epub3? Or perhaps make an epub3 menubar that removes all epub3 specific tools from the Tools menu and Accessibility becomes an entry under it.

The user can decide to show or not show an Accessibility clips bar, so maybe that is the way to go.

One issue with menus and toolbars being context sensitive is the multiple main window approach used in Sigil on macOS in which a user may be editing an epub2 and an epub3 simultaneously.

Lots to think about!

Thanks for sharing your recs and thoughts!