Earlier quoted context omitted.
1. The web crypto api was indeed made to secure communications, such as stated by the W3C on http://www.w3.org/TR/WebCryptoAPI/ (...) "Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications. " 2. Yes, you are definetly right, an detailed audit of the protocol is necessary by more than one expert. 3. Here is a short description of…
It seems like there would be a lot of uses for something like a jQuery for the WebCrypto API. There are enough ways to get it wrong, and enough commonality among 80% use cases, I can see something like this being better than the alternative.
What you want instead is a library that carefully selects primitives with an emphasis on:
1. Security
2. Performance
3. Ease of use
You want a high-level API, like I'm building for PHP 7.1, not a low-level API, like openssl, mcrypt, WebCrypto, etc.