Standards & Global Markets

UX sound across markets: know the context.

A sound system developed for international use needs to account for its target markets, product category and users. The relevant requirements may come from legislation, technical standards, procurement conditions or a specific approval process.

This guide introduces selected frameworks and their scope. It is a starting point for project planning. It does not establish compliance for an individual product.

Last reviewed: October 7, 2026

Start with three questions

Where will the product be used?

Identify the target jurisdictions and any customer-specific requirements.

What kind of product is it?

An app, medical device, payment terminal and vehicle can fall under different frameworks.

What does the sound do?

Routine feedback, accessible speech output and safety alarms require different treatment.

Accessibility in digital products

International foundation: WCAG

The Web Content Accessibility Guidelines provide testable criteria for web accessibility. Version 2.2 is the current W3C recommendation used in this guide, but individual rules and contracts may reference earlier versions.

Directly relevant examples include:

  • Sensory Characteristics, 1.3.3: Instructions must not rely solely on characteristics such as sound, shape or position.
  • Audio Control, 1.4.2: Automatically playing audio lasting more than three seconds needs a way to pause or stop it, or control its volume independently from overall system volume.
  • Error Identification, 3.3.1: Automatically detected input errors must be identified and described to the user in text.

These criteria address specific aspects of a broader accessibility standard. Meeting the audio criteria alone does not establish WCAG conformance.

European Union and Germany

The European Accessibility Act applies to specified products and services, with requirements applying from June 28, 2025 subject to the relevant provisions and transitions. Examples include payment terminals, smartphones, consumer banking services and e-commerce services.

Germany implements the directive through national legislation including the Barrierefreiheitsstärkungsgesetz, or BFSG. Applicability depends on the product or service; the Act does not cover every website or device.

For relevant projects, audio and speech output should be planned as part of the complete accessible interaction.

United States

The ADA Title II web and mobile application rule specifies WCAG 2.1 Level AA for covered state and local government content and apps. This particular rule is not a universal technical requirement for all private-sector products.

For project planning, identify the organization providing the service and the applicable accessibility obligations before defining the technical baseline.

Switzerland

The Swiss federal administration references eCH-0059 Accessibility Standard Version 3, based on WCAG 2.1 Level AA. Its public-administration context should be distinguished from obligations for private products and services.

ICT accessibility: EN 301 549

EN 301 549 addresses accessibility requirements for ICT products and services. ETSI lists V4.1.1, published in September 2026. A newer publication should not automatically be treated as the legally referenced or contractually required version for every project.

Record the exact version required by the relevant framework or procurement brief.

Product & safety signals

Medical alarms and usability

IEC 60601-1-8 specifies requirements and tests for alarm systems in medical electrical equipment and systems. It is a relevant starting point for medical alarm design within its scope.

The FDA lists IEC 60601-1-8 Edition 2.2, the 2020 consolidated version, as a recognized consensus standard. Recognition and applicable editions should be checked for the actual submission.

FDA human factors guidance also emphasizes intended users, uses and use environments. Sound evaluation should therefore be connected to the device's risk and usability work.

A design brief should distinguish routine feedback from alarms and define the responsibilities for testing and regulatory assessment.

Consumer product signals

ISO 24500:2010 addresses auditory signals for consumer products within a defined scope. It applies to fixed-frequency signals, commonly called beep sounds, and excludes variable-frequency and melodic sounds. It is not a general standard for every branded product sound.

ISO 24501:2010 addresses methods for determining appropriate auditory signal levels for consumer products, considering interfering sounds and users with age-related hearing loss.

Japan also has a national standard, JIS S 0013, concerning accessible auditory signals for consumer products. Its current edition and applicability need to be established for a Japan-market project.

Danger signals in public and work areas

ISO 7731:2003 addresses design principles, ergonomic requirements and test methods for auditory danger signals in public and work areas. Its scope is different from routine notifications in a consumer app.

Exterior vehicle sound

UN Regulation No. 138 addresses quiet road transport vehicles and acoustic vehicle alerting systems. US FMVSS No. 141 sets minimum sound requirements for covered hybrid and electric vehicles.

These frameworks concern vehicle detectability. They should be assessed separately from app sounds and ordinary interior feedback. Relevant editions, vehicle categories and test conditions need to be established for the target market.

Cultural meaning needs evidence

Technical requirements are only one part of international design. Sounds can evoke different associations, and voice cues introduce language and pronunciation questions.

Rather than assuming a national preference, establish what needs to be tested with the intended audience:

  • Is the event interpreted correctly?
  • Does the perceived urgency match the intended meaning?
  • Does the cue resemble a familiar local signal with another meaning?
  • Does repeated exposure remain appropriate?
  • Are spoken messages intelligible in the required languages?

Turn requirements into a useful design brief

At the beginning of a project, define the target markets, product category, sound functions and responsible approval teams. This helps establish where creative design can develop freely and where specific requirements must be addressed.