MobileRead Forums - View Single Post

KevinH · 10-14-2025, 08:02 AM

Why on earth would you want to do that? In an epub3 the nav document must be there and be machine readable. It is there so that accessibility and navigation by screen readers is possible. So do not empty it out. Accessibility is important as is fast navigation around inside any epub by all readers. In fact most governments and institutions require full accessibility information in all its publications, especially those in europe.

You can always edit the OPF in CodeView and in its spine tag remove the nav manifest id from the spine and then immediately save the epub. That way you can leave the full/accurate toc info in the nav but prevent from being part of the epub's reading order. If you do that, readers will not see the nav as part of their normal reading.

10-14-2025, 08:02 AM	#17
KevinH Sigil Developer Posts: 9,066 Karma: 6361556 Join Date: Nov 2009 Device: many	Why on earth would you want to do that? In an epub3 the nav document must be there and be machine readable. It is there so that accessibility and navigation by screen readers is possible. So do not empty it out. Accessibility is important as is fast navigation around inside any epub by all readers. In fact most governments and institutions require full accessibility information in all its publications, especially those in europe. You can always edit the OPF in CodeView and in its spine tag remove the nav manifest id from the spine and then immediately save the epub. That way you can leave the full/accurate toc info in the nav but prevent from being part of the epub's reading order. If you do that, readers will not see the nav as part of their normal reading. Last edited by KevinH; 10-14-2025 at 08:10 AM.