Implementation of accessibility for screen readers

[ksb749]

First of all, does the Jellyfin Media Player rely on the Jellyfin-web or is it two seperated projects that dont sync code?

Reason for my first question, is that Jellyfin-web and jellyfin Media Player lacks screen reader support (NVDA and Jaws + keyboard shortcuts like m = mute/unmute, F = full screen of movie playback, arrow up/down is audio up/down. But Jellyfin-web lacks headings for easy navigation heading 1, 2 and 3 - but also more boxed content - like a libary, the screen reader catch both the poster, but also the name of the libary below, and much more, which makes it extremely annoying to navigate in Jellyfin Media Player and Jellyfin-web

Sorry if mixing things up, but the focus to figure out for me, is should i write issues in here, or at the jellyfin-web project?