This ambiguity / lack of clarity was raised by @robert-kinder in a related conversation.
Here's my summary of the situation, and of the decision that we need to make:
-
Web pages should have a main heading (using the <h1> element), as well as a page title (using the <title>) element. The main heading is visible on the page. The title is visible on the browser tab, and is announced by screen readers. This is what allows screen reader users to orientate between the tabs of their web browsers.
-
WCAG SC 1.4.2 has been written for web pages (back in early 2000s when native mobile apps didn't exist). And its only requirement is about the <title> of a web page.
-
1.4.2 says nothing about what the main headings of a web page should be. But it's convention and best practice for the <h1> and the <title> to mirror each other – with the exception that the <title> should also indicate the name of the website/service. @robert-kinder has documented an example of how the content of h1 and of title should compare.
-
It's not 100% clear whether and how 1.4.2 applies to native mobile apps. Some people say that the WCAG apply to native apps (with a bit of interpretation/adaptation). Some people say that the WCAG don't apply.
-
But the new UK public sector procurement law will apply the WCAG to native apps started June 2021. So my opinion is that, when a WCAG Success Criterion translates well to native mobile, we should apply it there too.
-
In the case of 1.4.2, there's an ambiguity: the Success Criteria's only requirement is for the title of a document (i.e. <title> for a HTML page, or equivalent for a PDF or Word document). It doesn't say anything about what the main heading of a page should be. So maybe, yes, we should make this 'web only'.
-
But at the same time, I'm imagining that for a native mobile app, the equivalent of <title> would be the title that appears in the navigation bar at the top of the screen. I'm imagining that, on native mobile app, the title that appears in the navigation bar at the top of the screen serves the same purpose as <title> and <h1> at the same time. So I'd like to investigate further.
@KaneCheshire @geftimov @amryousef-tab what are your thoughts?
This ambiguity / lack of clarity was raised by @robert-kinder in a related conversation.
Here's my summary of the situation, and of the decision that we need to make:
Web pages should have a main heading (using the
<h1>element), as well as a page title (using the<title>) element. The main heading is visible on the page. The title is visible on the browser tab, and is announced by screen readers. This is what allows screen reader users to orientate between the tabs of their web browsers.WCAG SC 1.4.2 has been written for web pages (back in early 2000s when native mobile apps didn't exist). And its only requirement is about the
<title>of a web page.1.4.2 says nothing about what the main headings of a web page should be. But it's convention and best practice for the
<h1>and the<title>to mirror each other – with the exception that the<title>should also indicate the name of the website/service. @robert-kinder has documented an example of how the content ofh1and oftitleshould compare.It's not 100% clear whether and how 1.4.2 applies to native mobile apps. Some people say that the WCAG apply to native apps (with a bit of interpretation/adaptation). Some people say that the WCAG don't apply.
But the new UK public sector procurement law will apply the WCAG to native apps started June 2021. So my opinion is that, when a WCAG Success Criterion translates well to native mobile, we should apply it there too.
In the case of 1.4.2, there's an ambiguity: the Success Criteria's only requirement is for the title of a document (i.e.
<title>for a HTML page, or equivalent for a PDF or Word document). It doesn't say anything about what the main heading of a page should be. So maybe, yes, we should make this 'web only'.But at the same time, I'm imagining that for a native mobile app, the equivalent of
<title>would be the title that appears in the navigation bar at the top of the screen. I'm imagining that, on native mobile app, the title that appears in the navigation bar at the top of the screen serves the same purpose as<title>and<h1>at the same time. So I'd like to investigate further.@KaneCheshire @geftimov @amryousef-tab what are your thoughts?