4.1.3.3 Sounds
Description
This section describes cultural considerations for using sounds.
Command Line Interface
Not applicable.
Character Interface
Not applicable.
Graphical Interface
Sounds can be used in a product to indicate status or to signal an error. The meaning of sounds can differ from one country
to the next. A ringing telephone and a siren sound differently in different countries.
Also, people can react to sound in different ways. While it is common to hear computers bleeping error messages in a workplace in the
United States, the audibility of mistakes is more embarrassing in a country such as Japan, where people work closely in small groups,
often with a supervisor within earshot. It is important to remember that hearing-impaired users require alternatives to
sounds.
Application Protocols
While images can be made generic, it is difficult to make generic sounds. Protocols that involve sound requests can have language or locale parameters as part of the string.
Storage and Interchange
Like messages, sounds can be stored by locale, separate from code. They are not usually part of another resource file, rather they are stored individually. Sound formats themselves are not locale-sensitive.
Application Programming Interfaces (APIs)
Similar to application protocols, APIs can provide locale-specific sound data.
Requirements for Compliance
Command Line Interface
No requirement.
Character Interface
No requirement.
Graphical Interface
Providers should treat sounds as localizable resources. To facilitate localization, sounds should be stored in external files. If a product contains sound, it must offer an easy way for users to turn the sound off. Also, if a product uses sound to convey information to the user, it should always provide an alternative textual format. Providing alternatives to sound accommodates users in a variety of locales, as well as people with hearing impairments.
Application Protocols
Providers should supply a protocol that allows for locale specification with a sound element, where relevant.
Consumers must give locale information when required in the protocol.
Storage and Interchange
Providers must supply locale-specific storage for sound elements.
Consumers must store localizable sound elements by locale.
Application Programming Interfaces
Providers should supply a protocol that allows for locale specification with a sound element, where relevant.
Consumers must give locale information when required in the protocol.
|
|
Print-friendly Version
