When the student tried on a school device, the problem was solved. So this turned out to be a non-issue (as far as the WeBWorK side of things). I can't confirm whether it was a browser issue specifically, but it was something to do with an issue on the student's machine.
Alex and Glenn: thanks for your clarification!
Alex and Glenn: thanks for your clarification!