-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Page title and notebook title do not match #10
Comments
I suspect that this might have to be in the style guide, since currently notebooks allow for two different kinds of titles, i.e. a recognized title corresponding to the filename (very frequently "Untitled") and a title expressed at the beginning of the document, ideally in a I think looking at a combination of the Pending further exploration, my initial suggestion here is to address this in the style guide. |
i am not sure if i agree with the need for the title and notebook to match. if they do they we are introducing repetitive information into the screen reader. i think they have different purposes. is there a wcag criterion for this? |
The closest I could find was this: https://www.w3.org/WAI/WCAG21/Understanding/page-titled.html I would generally say that it's not against WCAG to have mismatched title/h1. The most common version of this is that many websites have the name of the site (broadly) in the title, along with the name of the age, which I don't think is an accessibility issue. However, this is rarely done with a h1. I think this still might be a valid issue, in the sense that Jupyter notebooks seem to cause people not to title the file fairly often (what Isabela calls the infamous "Untitled (3)". People are less likely not to put any title-like info at the start of a notebook. I don't think we can realistically do a technical intervention here. It's too heavy-handed to take either the first h1 and make it the title or vice versa. I think the proper action here is to make sure the style guide says something like "Provide a descriptive title for the notebook." |
I'm following up on this as I clean up our content type test results. We asked a similar "Can you tell me what the title of this notebook is?" question in the test 2 script and found similarly inconsistent answers from participants. We still had answers ranging from the webpage title, to the file name, to the Based on the feedback above and more style guide discussions with a broader community, I think I'm inclined to agree that this might not be a wise thing to override. It also did not block people from working with notebooks; it was only a point of confusion because we use the word I won't close this yet to make sure we're on the same page, but I will circle back. Thanks for all the feedback. |
Problem and context
This issue comes from our user testing round 1: navigation. At the moment, the page title (the words listed in the browser tab) and the notebook/document title (the H1, a.k.a
#
first used in a markdown cell) are different. When asked "Can you tell me what the title of this notebook is?" multiple participants were not sure which piece of information was the title. Some only reported one of the options though there was not a trend of locating one of the potential titles over the other.Currently, the page title is the notebook/file name without the extension (ie.
my_notebook
or the infamousUntitled3
). The notebook/document title is determined by the author's use of headings in their notebook cells, in this case what line they label their H1. I have not had a chance to observe what happens if the author does not define an H1.Possible solutions
I don't think there is a experience-boosting reason for the page title and notebook title to be different (especially in light of #8's findings), though I would love to hear it if someone finds utility in having them separate. I would advise
Examining the first JWST images - Space Telescope Science Institute
or `How to write a tutorial in Jupyter notebooks - spacetelescope/notebooks.Acceptance criteria
This issue can be closed when we
Tasks to complete
The text was updated successfully, but these errors were encountered: