WASM is run in a "brain in a jar" type execution model, with basically zero knowledge or access to its external environment (the "host"). So it could absolutely take advantage of these kinds of peripherals, but the host enviornment would provide import functions that enable it to interact with resources like a video card.

The gap is definitely closing as you say, and WebAssembly provides a path for it, as well as a security model that doesn't put users at risk.

Uses it, but with more abstraction / less directly than machine code would.