• 1 Post
  • 68 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle

  • I kind of understand why someone would honestly. Jellyfin subtitles are still a hot mess for a lot of formats unfortunately. Also, while plex has tried really hard to ruin their UI, I’ve still had more trouble explaining where to find things in Jellyfin. And if you’re sharing your collection with friends or family members there’s a lot more technical stuff involved.

    So I can see why the balance might still tip toward paying plex still for some people.

    Luckily I bought a lifetime license ages ago before the first price hike so this doesn’t affect me yet. So I’m just riding out the decline, running them in parallel until plex completely breaks. slowly transitioning the family as they get annoyed with broken features. Plexamp is quickly taking care of that 😅



  • I think your confusion is the other side of what the article was discussing.

    The problem is, there have been a lot of number systems in the past. The one we currently use is based on the Arabic system. In common usage you would simply call them numbers. But in a technical sense, to distinguish from other numbering systems past and present, they’re also called Arabic Numerals because that’s their origin.

    Clearly this ignores the fact Arabic is still around and using real Arabic numbers and that is both confusing and maybe problematic. But I think the technical reason it sticks around is to acknowledge their source and have a more specific term when there is a need















  • It doesn’t have to not include JavaScript, that would be quite difficult and unreasonable. Accessible sites are not about limiting functionality but providing the same functionality.

    I haven’t gone fully down the rabbit hole on this but my understanding is even something like Nuxt if you follow best practices will deliver HTML that can be interacted with and serve individual pages.

    That said, screen readers and other support shouldn’t require running without any JavaScript. Having used them to test sites that might be the smart approach but they actually have a lot of tools for announcing dynamic website changes that are built into ARIA properties at the HTML level so very flexible. There are of course also JavaScript APIs for announcing changes.

    They just require additional effort and forethought to implement and can be buggy if you do really weird things.


  • Also the EU and technically a lot of US sites that provide services to or for the government have similar requirements. The latter is largely unenforced though unless you’re interacting with states that also have accessibility laws.

    And honestly a ton of sites that should be covered by these requirements just don’t care or get rubber stamped as compliant. Because unless someone actually complains they don’t have a reason to care.

    I kind of thought the EU requirements that have some actual penalties would change this indifference but other than some busy accessibility groups helping people that already care, I haven’t heard a lot about enforcement that would suggest it’s actually changed.