A web page with interface sounds effects should not be intrusive to the user. Certain Arwes applications may make the user expect sounds effects implicitely, but this is not necessarily the default case. See the UI/UX guidelines where some recommendations are made.
Since some browsers have Audio Autoplay Policies, they block the sound playback on window load until first user interaction. It is not recommended to play sounds on window start time. Only after first user interaction.
Arwes sounds tools will not play sounds until the browser audio is unlocked. They will not throw errors nor show warning messages.
If the application requires to play sounds as normal user experience, it is recommended to "explicitely" request permission from the user, such as showing a start page with a button to request user interaction before access to the application.
The sounds tools allow the programmer to define if the sounds are enabled, the sound volume, and the rate of playback. It also allows to set settings by categories of sounds. It is recommended to show the user a settings panel where to configure these behaviors.