Currently it seems that the json file generated uses system encoding. Unfortunately WebVOWL does not load the file using the system encoding, but rather UTF-8.
OWL2VOWL could at least use utf-8 by default to encode, or propose a commandline option to define the encoding to use.