Question about H1 on non-document, single-purpose pages #63
Description
Thanks for the wonderful accessibility workshop last week!
I've been playing with WAVE on JupyterHub pages, and trying to find some low hanging fruit, and there definitely are some.
I've hit a few I don't quite know what to do with, though.
The first is that several JupyterHub pages don't have an h1 because there is no heading. Most JupyterHub pages are single-purpose, where a text heading is redundant with the HTML title, url, etc., and in some cases would be most of the content of the page.
For instance, the login page looks like this:
Should I make that Sign In an H1?
Similarly, the 'home page' is really one button to get to your server (or two, if you want to stop it):
And a third case, the admin page is one big table:
Is it considered best practice to duplicate the HTML title into page content for every page of an application? That doesn't feel right, but I'm sure there are accessibility issues I'm not aware of. I don't feel like I have the information available to make "this guideline does not apply in this context" decisions.
In general, the WCAG text that comes up:
A first level heading (
<h1>) should be present on nearly all pages. It should contain the most important heading on the page (generally the document title).
seems to assume that web pages are documents and not applications.
When I check for another example of what I hope is a good page, the GitHub dashboard, which also doesn't have a logical heading in the default view, has a hidden <h1 class="sr-only">Dashboard</h1>. Is this a good pattern to follow to add hidden structural content for readers-only?
Sorry if this is the wrong place to ask questions like this, I'm just excited to be able to make progress!