In some different cases it would be really usefull to create a button which calls the navigation bar from the viewer app.

E.g.:

Button with url: app://navigation (to simulate a click on the article to get the navigation bar)

Button with url: app://overview (to simulate the home button)

Example scenario:

I have a animation in the background, which is done as a video. The user shouldn't be able to interact with that animation in any case. If the controls are hidden, the user can still click on the video to stop it. This can be solved if you put another interactive element on top, so the video can't be stoped. For example a button which links to the same article and same page number.

BUT in this case, you can click on the animation, and nothing happens, but it would be nice to get the navigation bar.

We have HTML5 app inside of the web overlay that handles the touch events for the entire page and disables tap to call the navigation bar. To exit from the folio we use another overlay on top of the 1st one as a button with the link to goto://ApplicationViewState/library as per: