Skip to content

Editorial guideline

Tanya van Workum edited this page Sep 12, 2025 · 1 revision

Objective

The goal of this editorial guideline is to help contributors structure their input consistently while drafting WCAG2Mobile.

WCAG2Mobile provides informative guidance on how WCAG 2.2 principles, guidelines, and success criteria apply to (from our abstract):

  • Native mobile applications
  • Mobile web applications
  • Hybrid applications (native apps with embedded web content)

It explains how to interpret existing WCAG 2.2 content in a mobile context. The structure and tone follow the WCAG2ICT Note.

Although the scope of this document is broader, the working group currently focuses on native mobile applications (which should be clearly presented in the document text).

Goal for the Group Note #2

To produce a clear, minimal, and consistent group note that aligns with WCAG 2.2 and provides structured notes and examples only when necessary (when the note itself does not provide enough context).

This phase focuses on:

  • Success Criteria (with small variations)
  • Definitions

Structure for Success Criteria text

Each SC text block should consist of the following subsections:

Title

“Applying SC XXX [name] to native mobile apps, mobile web apps, and hybrid apps.”
This title will follow the official text of WCAG and WCAG2ICT.

Applicability

In this subsection, include the applicability of the SC and mention the applicability to native mobile apps, mobile web apps, and hybrid apps (similar to WCAG2ICT).
For example: “This applies directly as written, and as described in Intent from [Understanding SC XX].”

Normative text

Paste the normative text of the relevant success criterion.

If different or additional terminology should be used, include how the SC would read (similar to WCAG2ICT).

Notes

  • If exceptions or clarifications are needed, add them as a Note.
  • If a Note applies only to native mobile apps, mobile web apps, or hybrid apps, add the specific type in parentheses (e.g., “Note (native mobile apps)”).
  • If a Note applies to all three, no specification is needed.

Examples

  • If the Note does not provide enough context, add an Example under the Notes section.
  • Examples should be specific.
  • If an Example applies only to native mobile apps, mobile web apps, or hybrid apps, add the specific type in parentheses (e.g., “Example (mobile web apps)”).
  • If an Example applies to all three, no specification is needed.

Notes and Examples – logic

  • Only add a Note if the WCAG text is not fully clear in the mobile context.
  • If a Note or an Example becomes longer than a paragraph (approx. 3–5 sentences), or starts including multiple cases or edge cases, consider moving the additional information to the Understanding document.

Structure for Definitions text

  • Definitions that require additional explanation should be added in the subsection “Key Terms.”
  • After each definition, include applicability to native mobile apps, mobile web apps, and hybrid apps (similar to WCAG2ICT).
  • If exceptions or clarifications are needed, add them as a Note and include Examples where necessary.
  • Be specific about which parts the Note or Example applies to (native mobile apps, mobile web apps, or hybrid apps).
  • Notes and Examples should be short.
Clone this wiki locally