Update guidance title to Mobile Applications

JJdeGroot · JJdeGroot · commit a3a5035f4af6 · 2025-03-12T08:06:55.000+01:00
diff --git a/index.ejs b/index.ejs
@@ -4,7 +4,7 @@
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1">
   <meta name="color-scheme" content="light dark">
-  <title>Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)</title>
+  <title>Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)</title>
   <script src="wcag2mobile.js" class="remove"></script>
   <script src="respec-config.js" class="remove"></script>
   <script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
diff --git a/index.html b/index.html
@@ -4,22 +4,22 @@
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1">
   <meta name="color-scheme" content="light dark">
-  <title>Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)</title>
+  <title>Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)</title>
   <script src="wcag2mobile.js" class="remove"></script>
   <script src="respec-config.js" class="remove"></script>
   <script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove"></script>
   <link rel="stylesheet" href="matf.css">
 </head>
 <body>
   <section id="abstract">
-    <p>This document, “Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)”, describes how the Web Content Accessibility Guidelines (WCAG) version 2.2 [<a href="https://www.w3.org/TR/WCAG22/">WCAG22</a>] principles, guidelines, and success criteria can be applied to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps. It provides informative guidance (guidance that is not normative and does not set requirements).</p>
+    <p>This document, “Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)”, describes how the Web Content Accessibility Guidelines (WCAG) version 2.2 [<a href="https://www.w3.org/TR/WCAG22/">WCAG22</a>] principles, guidelines, and success criteria can be applied to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps. It provides informative guidance (guidance that is not normative and does not set requirements).</p>
 <p>This document is part of a series of technical and educational documents published by the <a href="https://www.w3.org/WAI/">W3C Web Accessibility Initiative (WAI)</a> and available from the <a href="https://www.w3.org/WAI/standards-guidelines/mobile/">Mobile Accessibility Overview</a>.</p>
 
   </section>
 
   <section id="sotd">
     <p>This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.</p>
-<p>This is a W3C Group Note on “Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)”. The purpose of this work is to build upon <a href="https://www.w3.org/TR/mobile-accessibility-mapping/">&quot;Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile&quot;</a>, but with a stronger focus on Mobile Applications and including changes made in WCAG 2.1 and 2.2.</p>
+<p>This is a W3C Group Note on “Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)”. The purpose of this work is to build upon <a href="https://www.w3.org/TR/mobile-accessibility-mapping/">&quot;Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile&quot;</a>, but with a stronger focus on Mobile Applications and including changes made in WCAG 2.1 and 2.2.</p>
 <p>To comment, <a href="https://github.com/w3c/matf/issues/new">file an issue in the W3C <code>matf</code> GitHub repository</a>. The Task Force requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to <a href="mailto:public-agwg-comments@w3.org?subject=WCAG2Mobile%20public%20comment">public-agwg-comments@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). In-progress updates to the guidelines can be viewed in the <a href="https://w3c.github.io/matf/">public editors’ draft</a>.</p>
 <p>This document was published by the <a href="https://www.w3.org/groups/wg/ag">Accessibility Guidelines Working Group</a> as an <a href="https://www.w3.org/standards/types/#x2-3-editor-s-draft">Editor's Draft</a>.</p>
 <p>Publication as an Editor's Draft does not imply endorsement by W3C and its Members.</p>
@@ -45,16 +45,16 @@ <h3>Background</h3>
 <li>3.3.7 Redundant Entry (A), to reduce the amount of repetitive typing.</li>
 </ul>
 <p>In January 2024, the MATF regrouped and welcomed new participants to work on updated guidance for applying WCAG 2.2 to Mobile Applications.</p>
-<p>This current document, “Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)” is specific to how WCAG applies to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps.</p>
+<p>This current document, “Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)” is specific to how WCAG applies to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps.</p>
 <p>WCAG2Mobile maps directly to the W3C supporting document, “<a href="https://www.w3.org/TR/wcag2ict-22/">Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)</a>”, which was published as a Group Note in October 2024, describing how WCAG 2.2 could be applied to non-web documents and software. The intention of the MATF is to publish WCAG2Mobile as a Group Note, just like WCAG2ICT.</p>
 <p>WCAG2ICT is organized to mirror the Principle, Guideline and Success Criterion structure of WCAG; this model is also used in WCAG2Mobile. WCAG2ICT clarifies when and how WCAG Level A and Level AA success criteria could be applied to non-web documents and software; WCAG2Mobile narrows the scope of this work to Mobile Applications.</p>
 
     <h3>Guidance in this Document</h3>
 <p>This document provides informative guidance (guidance that is not <a href="https://www.w3.org/TR/WCAG22/#dfn-normative">normative</a> and that does not set requirements) with regard to the interpretation and application of Web Content Accessibility Guidelines (WCAG) to Mobile Applications. This document is a <a href="https://www.w3.org/standards/types/#x2-5-2-group-note">Group Note</a> (in contrast to WCAG 2.2, which is a <a href="https://www.w3.org/standards/types/#REC">W3C Recommendation</a>). Specifically, this document provides informative guidance on applying WCAG 2.2 Level A and AA success criteria to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps.</p>
 <h4>Interpretation of Web Terminology in a Mobile Context</h4>
 <p>When certain Web-specific terms or phrases like “web page(s)” were used in success criteria, those were replaced with mobile terms or phrases like “screen(s)” or “view(s)”. Additional notes were also provided to explain the terminology replacements.</p>
-<p>A small number of success criteria are written to apply to “a set of web pages” or “multiple web pages” and depend upon all pages in the set to share some characteristic or behavior. Since the unit of conformance in WCAG 2 is a single web page, the task force agreed that the equivalent unit of conformance for mobile applications is a single screen within the application. It follows that an equivalent unit of evaluation for a “set of web pages” would be a “set of screens”, not, as previously interpreted in WCAG2ICT, as a “set of software”. These terms are defined in the Key Terms section of this document. See “set of screens” to determine when a group of screens in a mobile application are considered a set.</p>
-<p>The glossary terms were also reviewed and most of them applied to mobile applications, as written. Some applied with additional notes or edits (largely related to phrases like “Web page(s)”), and a small number of terms were only used in Level AAA success criteria which are not addressed by the WCAG2Mobile Note at this time.</p>
+<p>A small number of success criteria are written to apply to “a set of web pages” or “multiple web pages” and depend upon all pages in the set to share some characteristic or behavior. Since the unit of conformance in WCAG 2 is a single web page, the task force agreed that the equivalent unit of conformance for Mobile Applications is a single screen within the application. It follows that an equivalent unit of evaluation for a “set of web pages” would be a “set of screens”, not, as previously interpreted in WCAG2ICT, as a “set of software”. These terms are defined in the Key Terms section of this document. See “set of screens” to determine when a group of screens in a Mobile Application are considered a set.</p>
+<p>The glossary terms were also reviewed and most of them applied to Mobile Applications, as written. Some applied with additional notes or edits (largely related to phrases like “Web page(s)”), and a small number of terms were only used in Level AAA success criteria which are not addressed by the WCAG2Mobile Note at this time.</p>
 
     <h3>Excluded from Scope</h3>
 <p>The following are out of scope for this document:</p>
@@ -126,7 +126,7 @@ <h3>Comparison with the 2015 Mobile Accessibility Working Draft Note</h3>
 <li>Success Criterion 3.3.2 Labels or Instructions (Level A)</li>
 <li>Success Criterion 3.3.5 Help (Level AAA)</li>
 </ul>
-<p>Supporting documentation in the Mobile Mapping Appendix included <a href="https://www.w3.org/WAI/GL/mobile-a11y-tf/MobileTechniques/">WCAG 2.0 Techniques that Apply to Mobile</a> to address mobile web use cases for the rest of the WCAG 2.0 success criterion at the Level A, AA, and AAA levels as they were available in 2015 when the webpage was published. However, most listed techniques have limited application to native mobile applications and cross-platform frameworks like Flutter and React Native.</p>
+<p>Supporting documentation in the Mobile Mapping Appendix included <a href="https://www.w3.org/WAI/GL/mobile-a11y-tf/MobileTechniques/">WCAG 2.0 Techniques that Apply to Mobile</a> to address mobile web use cases for the rest of the WCAG 2.0 success criterion at the Level A, AA, and AAA levels as they were available in 2015 when the webpage was published. However, most listed techniques have limited application to native Mobile Applications and cross-platform frameworks like Flutter and React Native.</p>
 <p>This document includes all WCAG 2.1 Level A and AA success criteria and guidelines:</p>
 <ul>
 <li>Success Criterion 1.3.4 Orientation</li>
diff --git a/plugins/wcag.js b/plugins/wcag.js
@@ -21,7 +21,7 @@ export class WcagPlugin extends Plugin {
    * @returns {Promise<{function}>} - An initialized `WcagPlugin` function.
    */
   static async init(tag, url) {
-    const html = await WcagPlugin.fetchHtml(url);
+    const html = await WcagPlugin.fetchHTML(url);
     return new WcagPlugin(tag, url, html).plugin();
   }
 
@@ -30,7 +30,7 @@ export class WcagPlugin extends Plugin {
    * @param {string} url - The URL to fetch.
    * @returns {Promise<string>} - The rendered HTML content.
    */
-  static async fetchHtml(url) {
+  static async fetchHTML(url) {
     console.log(`Fetching rendered HTML for: ${url}`);
     const browser = await puppeteer.launch({ 
       headless: true,
@@ -46,7 +46,7 @@ export class WcagPlugin extends Plugin {
     } catch (error) {
       console.error(`Error fetching ${url}:`, error);
       await browser.close();
-      return `<p>Error loading content from ${url}</p><p>${error}</p>`;
+      throw new Error(`rror loading content from ${url}: ${error}`);
     }
   }
 
diff --git a/sections/abstract.md b/sections/abstract.md
@@ -1,3 +1,3 @@
-This document, “Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)”, describes how the Web Content Accessibility Guidelines (WCAG) version 2.2 [[WCAG22](https://www.w3.org/TR/WCAG22/)] principles, guidelines, and success criteria can be applied to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps. It provides informative guidance (guidance that is not normative and does not set requirements).
+This document, “Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)”, describes how the Web Content Accessibility Guidelines (WCAG) version 2.2 [[WCAG22](https://www.w3.org/TR/WCAG22/)] principles, guidelines, and success criteria can be applied to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps. It provides informative guidance (guidance that is not normative and does not set requirements).
 
 This document is part of a series of technical and educational documents published by the [W3C Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/) and available from the [Mobile Accessibility Overview](https://www.w3.org/WAI/standards-guidelines/mobile/).
diff --git a/sections/background.md b/sections/background.md
@@ -16,7 +16,7 @@ In the next years, the MATF ensured that mobile considerations were included in
 
 In January 2024, the MATF regrouped and welcomed new participants to work on updated guidance for applying WCAG 2.2 to Mobile Applications.
 
-This current document, “Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)” is specific to how WCAG applies to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps.
+This current document, “Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)” is specific to how WCAG applies to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps.
 
 WCAG2Mobile maps directly to the W3C supporting document, “[Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)](https://www.w3.org/TR/wcag2ict-22/)”, which was published as a Group Note in October 2024, describing how WCAG 2.2 could be applied to non-web documents and software. The intention of the MATF is to publish WCAG2Mobile as a Group Note, just like WCAG2ICT.
 
diff --git a/sections/comparison.md b/sections/comparison.md
@@ -30,7 +30,7 @@ The prior 2015 Mobile Working Draft Note included specific guidance on the follo
 - Success Criterion 3.3.2 Labels or Instructions (Level A)
 - Success Criterion 3.3.5 Help (Level AAA)
 
-Supporting documentation in the Mobile Mapping Appendix included [WCAG 2.0 Techniques that Apply to Mobile](https://www.w3.org/WAI/GL/mobile-a11y-tf/MobileTechniques/) to address mobile web use cases for the rest of the WCAG 2.0 success criterion at the Level A, AA, and AAA levels as they were available in 2015 when the webpage was published. However, most listed techniques have limited application to native mobile applications and cross-platform frameworks like Flutter and React Native.
+Supporting documentation in the Mobile Mapping Appendix included [WCAG 2.0 Techniques that Apply to Mobile](https://www.w3.org/WAI/GL/mobile-a11y-tf/MobileTechniques/) to address mobile web use cases for the rest of the WCAG 2.0 success criterion at the Level A, AA, and AAA levels as they were available in 2015 when the webpage was published. However, most listed techniques have limited application to native Mobile Applications and cross-platform frameworks like Flutter and React Native.
 
 This document includes all WCAG 2.1 Level A and AA success criteria and guidelines:
 
diff --git a/sections/guidance.md b/sections/guidance.md
@@ -6,6 +6,6 @@ This document provides informative guidance (guidance that is not [normative](ht
 
 When certain Web-specific terms or phrases like “web page(s)” were used in success criteria, those were replaced with mobile terms or phrases like “screen(s)” or “view(s)”. Additional notes were also provided to explain the terminology replacements.
 
-A small number of success criteria are written to apply to “a set of web pages” or “multiple web pages” and depend upon all pages in the set to share some characteristic or behavior. Since the unit of conformance in WCAG 2 is a single web page, the task force agreed that the equivalent unit of conformance for mobile applications is a single screen within the application. It follows that an equivalent unit of evaluation for a “set of web pages” would be a “set of screens”, not, as previously interpreted in WCAG2ICT, as a “set of software”. These terms are defined in the Key Terms section of this document. See “set of screens” to determine when a group of screens in a mobile application are considered a set.
+A small number of success criteria are written to apply to “a set of web pages” or “multiple web pages” and depend upon all pages in the set to share some characteristic or behavior. Since the unit of conformance in WCAG 2 is a single web page, the task force agreed that the equivalent unit of conformance for Mobile Applications is a single screen within the application. It follows that an equivalent unit of evaluation for a “set of web pages” would be a “set of screens”, not, as previously interpreted in WCAG2ICT, as a “set of software”. These terms are defined in the Key Terms section of this document. See “set of screens” to determine when a group of screens in a Mobile Application are considered a set.
 
-The glossary terms were also reviewed and most of them applied to mobile applications, as written. Some applied with additional notes or edits (largely related to phrases like “Web page(s)”), and a small number of terms were only used in Level AAA success criteria which are not addressed by the WCAG2Mobile Note at this time.
+The glossary terms were also reviewed and most of them applied to Mobile Applications, as written. Some applied with additional notes or edits (largely related to phrases like “Web page(s)”), and a small number of terms were only used in Level AAA success criteria which are not addressed by the WCAG2Mobile Note at this time.
diff --git a/sections/status.md b/sections/status.md
@@ -1,6 +1,6 @@
 This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
 
-This is a W3C Group Note on “Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)”. The purpose of this work is to build upon ["Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile"](https://www.w3.org/TR/mobile-accessibility-mapping/), but with a stronger focus on Mobile Applications and including changes made in WCAG 2.1 and 2.2.
+This is a W3C Group Note on “Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)”. The purpose of this work is to build upon ["Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile"](https://www.w3.org/TR/mobile-accessibility-mapping/), but with a stronger focus on Mobile Applications and including changes made in WCAG 2.1 and 2.2.
 
 To comment, [file an issue in the W3C `matf` GitHub repository](https://github.com/w3c/matf/issues/new). The Task Force requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to [public-agwg-comments@w3.org](mailto:public-agwg-comments@w3.org?subject=WCAG2Mobile%20public%20comment) ([comment archive](https://lists.w3.org/Archives/Public/public-agwg-comments/)). In-progress updates to the guidelines can be viewed in the [public editors’ draft](https://w3c.github.io/matf/).
 

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,3 @@`
`1`		-This document, “Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)”, describes how the Web Content Accessibility Guidelines (WCAG) version 2.2 [[WCAG22](https://www.w3.org/TR/WCAG22/)] principles, guidelines, and success criteria can be applied to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps. It provides informative guidance (guidance that is not normative and does not set requirements).
	`1`	+This document, “Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile)”, describes how the Web Content Accessibility Guidelines (WCAG) version 2.2 [[WCAG22](https://www.w3.org/TR/WCAG22/)] principles, guidelines, and success criteria can be applied to Mobile Applications, including but not limited to native mobile apps, mobile web apps and hybrid apps using web components inside native mobile apps. It provides informative guidance (guidance that is not normative and does not set requirements).
`2`	`2`
`3`	`3`	`This document is part of a series of technical and educational documents published by the [W3C Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/) and available from the [Mobile Accessibility Overview](https://www.w3.org/WAI/standards-guidelines/mobile/).`