Well, I would still make difference between PlayerView and Player itself.

The problem is that part of the player functionality (controls) lives in PlayerView and rest of it in PageRegion (actual player, audio element). It seems to be hard to incorporate both in one class. 

Small benefit of current approach is ability to instantiate player class once, while if I move it into PlayerView, I have to wait for audio element, then find audio element and only after that check attribute of that element.

However, if that contradicts coding style, I can move it into PlayerView.