Add explicit mention of SPAs and dynamic changes of title to 2.4.2 understanding

[patrickhlauke]

• 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

[mraccess77]

Thanks! @patrickhlauke not sure if we need another word rather than "should" - sometimes I use "needs to" - but some people are more sensitive to this.

Also, not related to your commit -but I think we should pull the account number from being displayed in the page title. Perhaps we might say "saving account" or "account ending in xxxx" .
page titles seems like a way that PII could be leaked. Thoughts? ttps://support.google.com/analytics/answer/6366371?hl=en#zippy=%2Cin-this-article

[patrickhlauke]

@mraccess77 good point about security on that separate example. rolled a tweak into this PR for it as well

as for the use of "should", I think this is appropriate in this case because it clarifies that there may still be valid reasons for NOT changing the title, as this SC still does have that element of human judgement about it when deciding what is and isn't an appropriately descriptive title. don't think it would be confused with a normative uppercase SHOULD

[patrickhlauke]

Any news on this @alastc ?

[LaurenceRLewis]

I don't see the changes in relation to SPA in the Understanding document as described in the pull request 'Add explicit mention of SPAs and dynamic changes of title to 2.4.2 understanding #2107'

"In cases such as Single Page Applications (SPAs), where various distinct pages/views are all nominally served from the same URI and the content of the page is changed dynamically, the title of the page should also be changed dynamically to reflect the content/topic of the current view."

Was this every implemented?

[patrickhlauke]

I don't see the changes [...] Was this every implemented?

@LaurenceRLewis as this pull request is still open, and not merged, i think there's your answer

[hidde]

Just stumbled upon this PR and would very much support it to be merged in, very useful addition.

[marie450]

This PR would resolved a lot of discussion between our redaction and accessibility teams as all of our traditional HTML documents are replace by SPA.