Skip to content
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

Clarify in understanding SC 2.4.2 Page Title applicability to single page applications #2102

Closed
mraccess77 opened this issue Oct 22, 2021 · 4 comments · Fixed by #2107
Closed

Comments

@mraccess77
Copy link

The definition of web page as it's applied to a url that doesn't change in an single page application seems to imply that when the main content of an SPA changes the page title doesn't need to change, however, some people read it differently and would say that since the context changes the page title needs to be change because the title no longer describes the purpose of the url.

As we have discussed for 2.2 SPAs - some SPAs do have urls the change with hash tags. changes and then it's more clearly a requirement.

Some discussion was on WebAIM a few years ago on this topic.
https://webaim.org/discussion/mail_thread?thread=8564

So, I'm hoping that we can make it more clear if the context changes but the URL remains unchanged does a page title of a single page application need to change or not. I think we probably agree it's ideal - but is it required?

@patrickhlauke
Copy link
Member

I'm sure I said it before, but I believe the definition of Web Page and how it leans on the idea of "single URI" - which was probably relevant at the time of 2.0 - is now slowly showing its age / limits...

but back on topic, I'd agree that if the page's "topic or purpose" dynamically changes (while the URI remains the same), then title must also dynamically change to match reality. Would a note/mention along those lines in the understanding doc do the job?

@mraccess77
Copy link
Author

Hi @patrickhlauke that's how I interpret it - and if we agree then it makes sense to make that clear to others.

@patrickhlauke patrickhlauke self-assigned this Oct 22, 2021
@patrickhlauke
Copy link
Member

can't give a timeline (as i've got some imminent vacation), but will do a little PR soon (not that there's any rush...)

patrickhlauke added a commit that referenced this issue Oct 24, 2021
* this marries up nicely with the existing example already present talking about a web application for banking
* minor additional tweak: change `his` to `their` in the wording for the banking example

Closes #2102
@patrickhlauke
Copy link
Member

@mraccess77 #2107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants