E-mail List Archives
Thread: How important are page titles in a single page application?
Number of posts in this thread: 4 (In chronological order)
From: Mark Magennis
Date: Tue, Jan 30 2018 4:57AM
Subject: How important are page titles in a single page application?
No previous message | Next message →
Hi all,
If a single page application (SPA) presents as a number of distinct 'pages' of functionality, is it necessary to change the page's <title> to reflect the current function/content of the page? Assuming that the change of context is made obvious in some way. Who will even notice the <title> change? My reading of WCAG 2.4.2 page title is that it doesn't require unique <title> elements for individual 'pages' within an SPA. But is this okay in practice?
Mark
From: Patrick H. Lauke
Date: Tue, Jan 30 2018 5:18AM
Subject: Re: How important are page titles in a single page application?
← Previous message | Next message →
On 30/01/2018 11:57, Mark Magennis wrote:
> Hi all,
>
> If a single page application (SPA) presents as a number of distinct 'pages' of functionality, is it necessary to change the page's <title> to reflect the current function/content of the page? Assuming that the change of context is made obvious in some way. Who will even notice the <title> change? My reading of WCAG 2.4.2 page title is that it doesn't require unique <title> elements for individual 'pages' within an SPA. But is this okay in practice?
Users may not hear the change itself, but they may switch between tabs
or windows, or leave their computer for a while and return at a later
point. Or at any point, for whatever reason, they may just hit the
shortcut in their screen reader (INSERT+T in JAWS for instance) to have
the window title read out. Then it would arguably be good if they knew
the new context that they're in. You could probably argue that this
isn't *strictly* a requirement / a site that doesn't do it doesn't
*strictly* fail...but I'd tend to argue towards the fact that it goes at
least against the spirit of the SC.
Even more so if the SPA also dynamically changes the URL, and
bookmarking it in different states loads that particular state ("page")
later on...then it makes sense even for the bookmarking scenario to
ensure the <title> is correct and reflective of what's being displayed.
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: Steve Faulkner
Date: Tue, Jan 30 2018 5:20AM
Subject: Re: How important are page titles in a single page application?
← Previous message | Next message →
Screen reader users can access the title element content at any time using
a keystroke, for example:
using JAWS using INSERT + T
https://freedomscientific.github.io/VFO-standards-support/html.html#toc-title
--
Regards
SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
On 30 January 2018 at 11:57, Mark Magennis < = EMAIL ADDRESS REMOVED = > wrote:
> Hi all,
>
> If a single page application (SPA) presents as a number of distinct
> 'pages' of functionality, is it necessary to change the page's <title> to
> reflect the current function/content of the page? Assuming that the change
> of context is made obvious in some way. Who will even notice the <title>
> change? My reading of WCAG 2.4.2 page title is that it doesn't require
> unique <title> elements for individual 'pages' within an SPA. But is this
> okay in practice?
>
> Mark
> > > > >
From: Wolfgang Berndorfer
Date: Tue, Jan 30 2018 7:33AM
Subject: Re: How important are page titles in a single pageapplication?
← Previous message | No next message
Another relevant JAWS keyboard stroke for the texting of a page title is
INSERT + F10 to open a list of my open application windows. I'm always glad,
when the first letters of the title remain on a website. So I can easealy
navigate between windows. Thus please begin the text of your titles with a
short name of your app and then specify with a concise texting of the
current context, as e.g. WebAIM does.
Wolfgang
-----Ursprüngliche Nachricht-----
Von: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] Im Auftrag
von Steve Faulkner
Gesendet: Dienstag, 30. Jänner 2018 13:20
An: WebAIM Discussion List
Betreff: Re: [WebAIM] How important are page titles in a single
pageapplication?
Screen reader users can access the title element content at any time using
a keystroke, for example:
using JAWS using INSERT + T
https://freedomscientific.github.io/VFO-standards-support/html.html#toc-titl
e
--
Regards
SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;
On 30 January 2018 at 11:57, Mark Magennis < = EMAIL ADDRESS REMOVED = > wrote:
> Hi all,
>
> If a single page application (SPA) presents as a number of distinct
> 'pages' of functionality, is it necessary to change the page's <title> to
> reflect the current function/content of the page? Assuming that the change
> of context is made obvious in some way. Who will even notice the <title>
> change? My reading of WCAG 2.4.2 page title is that it doesn't require
> unique <title> elements for individual 'pages' within an SPA. But is this
> okay in practice?
>
> Mark
> > > > >