decisiondecided

UI Target Age Policy and Separation of Age-Related Operations

Context

  • Ambiguous UI difficulty goals under the banner of “usable by everyone” cause design decisions to drift
  • The game industry widely uses recommended-age notations (e.g., 8+, 10+, 14+) as a common convention
  • The service’s Terms of Service minimum age (13+), the UI design target age, and the per-title recommended age are conceptually distinct
  • Conflating these creates the following problems:
    • Over-simplifying the UI to target “all ages” undermines gameplay depth
    • Lowering the UI target age without regard to ToS creates the impression that we recommend the service to minors
    • Users may misinterpret a title’s recommended age (e.g., 8+) as the service’s own target age
  • Unrealistic goals such as “ages 2 to 99” fail as concrete design criteria and become hollow slogans
  • UI validation sometimes benefits from observing children operating the interface, but this must be clearly distinguished from offering the service directly to children

Options

OptionDesign clarityLegal safetyConvention fitTotal
A. Claim “all ages” (no target)- -- -0-4
B. Align UI with ToS age (13+)0++-+1
C. Separate UI target, ToS age, and per-title age++++++5

Decision

Adopt Option C. Define the UI design target age, the Terms of Service minimum age, and per-title recommended age as three independent operational rules.

1. UI Design Target Age

  • Target: Operable without stress by users aged 8 and above (equivalent to a second-grader in Japanese elementary school)
  • Positioning: A quality criterion for UI design. A concrete articulation of the goal “an interface anyone can use with ease”
  • Rationale: This target is a consequence of pursuing broad operability; it does not indicate that children are our intended customer segment
  • Validation criteria (examples):
    • Vocabulary that does not depend on advanced kanji or furigana for UI standard labels (JA)
    • Physical reachability of tap targets (users with small hands)
    • Low-cognitive-load icons, colors, and layout
    • Minimization of jargon

2. Terms of Service Minimum Age

  • Minimum age: 13 years old
  • Positioning: The age of contractual capability under the Terms of Service and Privacy Policy
  • Operation:
    • Age verification during signup flow
    • No recommendation of the service to users under 13; no ad targeting toward minors
    • Compliance with COPPA, GDPR-K, and equivalent child-protection regulations

3. Per-Title Minimum Age Display

  • Display: Each game title’s detail page shows the recommended minimum age for that game (e.g., Age: 8+, Age: 14+)
  • Positioning: Informational presentation of a recommended age based on the game’s content difficulty and theme
  • Operation:
    • Independent of any service-usage recommendation
    • Does not imply that the UI is playable by users of that age
    • Presented strictly as “information about the game content”
    • The relationship with the service minimum age is defined in the Terms of Service (see Follow-up of this decision)

4. Observation of Child Users for UI Validation

When child-user observation is necessary to validate the UI design target (age 8 equivalent), such observation shall be conducted through the cooperation of relatives, under the following principles.

Positioning

  • Conducted as part of family interaction; it is neither work nor labor
  • No compensation is paid; it does not constitute child labor
  • The content under observation is the service’s regular game UI, containing no age-inappropriate expression or harmful material
  • Labor Standards Act (Japan): Voluntary cooperation within the family, without compensation, does not constitute labor. It does not violate the minimum-age provisions (Article 56) or any related provisions
  • Child Welfare Act (Japan): The content involves no harmful material and does not constitute an act harmful to child welfare
  • Legal frameworks and guidelines concerning children’s use of digital devices: The activity falls within the scope of ordinary household digital-device usage and is not subject to specific regulatory restrictions
  • COPPA / GDPR-K and equivalents: Conducted without collection of personal information from children (observation records are anonymized; no identifying information is retained)
  • Relationship to Terms of Service: Does not involve the creation or use of a service account by the child. Observation is limited to temporary interaction under the supervision of the relative, who is the child’s guardian

Operational Principles

  • Observation is conducted with the explicit consent and in-person supervision of the relative (guardian)
  • No personal information about the child is collected or stored
  • Information obtained from observation is used solely for UI improvement and is anonymized when recorded
  • No compensation or reward is provided to the child (strictly within the scope of family interaction)
  • Records of each observation session are retained as internal documentation

Rationale

  • Concretizing the design goal: We replace vague expressions such as “ages 2 to 99” with a verifiable criterion (“operable without stress by a second-grader”). This serves as a decision axis in design reviews
  • Alignment with accessibility: A UI operable by younger users also benefits elderly users and users in high-cognitive-load situations (commuting, fatigue). The “age 8 target” improves experience universally as a by-product
  • Isolation of legal risk: By not conflating the UI target age with the ToS age, we avoid being misperceived as a “service for children.” The ToS retains its 13+ requirement
  • Alignment with convention: The widely used age-notation convention in the game industry carries informational value. We adopt it while clearly separating it from any service-usage recommendation
  • Reconciling validation effectiveness with legal compliance: Observing actual child users is useful for validating the UI target, but must not conflict with child-labor, child-welfare, or privacy regulations. Conducting such observation under a family-cooperation framework reconciles both
  • Preventing misinterpretation: The explicit separation prevents misreadings such as “the game is rated 8+, therefore it is acceptable to have an 8-year-old use the service”
  • Separation of UI and ToS responsibilities: The UI displays information straightforwardly; legal interpretation and disclaimers of recommendation are handled uniformly in the Terms of Service. This avoids cluttering the UI with disclaimers and preserves the “minimum noise” UI principle

Consequences

Positive

  • Design reviews can concretely verify “whether an 8-year-old can operate this”
  • Overall accessibility quality improves (younger-user support generalizes to all users)
  • Clear separation of responsibility between legal/ToS and design
  • The apparent contradiction between title age notation and service minimum age can be resolved via the Terms of Service without adding noise to the UI
  • Incorporating child-user observation into UI validation becomes possible within a lawful and ethical framework

Negative

  • All stakeholders must understand and distinguish three age concepts (onboarding documentation required)
  • Marketing language becomes harder to simplify as “usable by anyone” (precise phrasing such as “anyone aged 13 and above” is required)
  • The dual display of “Age: 8+” on a title detail page and “Service: 13+” in ToS requires explanation
  • Conducting child-user observation incurs operational overhead for prior explanation to relatives, consent acquisition, and record retention

Follow-up

  • Decide whether to include “second-grader-equivalent operation testing” in UI validation tests
  • Define the signup-flow age-verification UI specification
  • Establish UI guidelines for per-title age display
  • Prepare a Help/FAQ article explaining the age notations
  • Develop operational documents for child-user observation (consent form, observation protocol, record format)
  • Add a provision to the “Minimum Age” section of the Terms of Service clarifying the relationship between per-title age notations and the service’s minimum age
    • Key point: Explicitly state that age notations displayed on game titles do NOT indicate the service’s minimum age, any recommendation of the service, or any guarantee of UI operability