A usable player exposes labelled controls, logical focus order and understandable state changes, such as whether captions are on or playback is paused. Screen-reader support is about the interface as well as the programme. It does not automatically provide audio description for visual content.
Test the whole viewing task
Opening a title is only the beginning. A viewer may need to pause, seek, change audio, enable captions and exit full screen. Controls that are visually obvious can still be difficult if they have no accessible name or disappear before keyboard focus reaches them. Evaluate the actual task sequence.
Keep interface and media access separate
A screen reader can announce a button, but it cannot infer every meaningful action inside a film. Audio description or a descriptive transcript addresses that different need. Similarly, accessible menus do not guarantee that a particular programme includes captions or an appropriate descriptive track.
Report a precise barrier
Describe the control, expected action, screen reader, operating system and player version. State whether keyboard focus is missing, the label is unclear or the announced state is wrong. That is more actionable than a general claim that accessibility does not work. Avoid sharing credentials or private viewing histories in a public bug report.