The high level goals of WASM do include access to browser APIs, but the MVP version that is being implemented now, does not yet allow it:
https://github.com/WebAssembly/design/blob/master/JS.md
WASM code can call external functions defined per module, and the external code can be JS code that interacts with browser APIs. So indirect use of browser APIs is possible.
Re:WebAssembly Browser Preview
by smitherfield on Monday October 31, 2016 @01:39PM
(#12839034)
Right now it's more like Flash or Java applets, running in a sandbox within a sandbox.
Re:WebAssembly Browser Preview
by TazeTSchnitzel on Monday October 31, 2016 @02:03PM
(#12839305)
Huh? WebAssembly, like asm.js before it, can access Web APIs (albeit via JS).
Re:WebAssembly Browser Preview
by hackcasual on Monday October 31, 2016 @03:22PM
(#12840043)
Not exactly. You have to export those APIs into the WebAssembly module. It's certainly possible to have a WASM implementation that doesn't provide web APIs, but is still WASM.
Do you have a reference? I'm confused about why you wouldn't want to access browser APIs.