TVSailor

Rewatchable TV Insanity - 30 years!

Snapple Fact #432: I'm so tired, man.



YuushaRuby
@YuushaRuby
    Notes:
  • You can’t log in
  • You can’t navigate past the first page of someone’s profile
  • some css still works on chosts (notice my a tag styling is not working) screencap of the introduction chost on my profile, important info is that it’s showing that the red and pink colors used are still visible in this browser
  • egg bug is nowhere to be seen… you’d think there’d be an svg or asciii fallback egg bug somewhere…
  • huge
  • alt text doesn’t show up, this is browser specific though, doesn’t work in my website either except on a single image on my homepage, weird, I know

Ruby’s lofi accessibility Rating: ★ ☆ ☆ ☆ ☆

please note, I love cohost, this is a somewhat silly thing, though I think there could be improvements for people who maybe want to use the site this way, I’m not sure how reasonable that is, this is just the first site I decided to test this on, I’m going to be doing more Ruby’s lofi accessibility ratings in the future, thank you for your rubies

also Omg I did all the in line styling in this by hand this time without prechoster because I’m on my phone and prechoster is broken on mobile I know it’s extremely simple but I’m proud for remembering all these css properties and shit please clap

the game


TVSailor
@TVSailor

I've noticed and complained a little about this too, but slowly got used to it.


You must log in to comment.

in reply to @YuushaRuby's post:

Yeah I mean REALISTICALLY, the html and such should be semantic and legible to blind people sitewide regardless of what browser setup they use (it’s not) and what is being loaded, a current glaring issue is you basically can’t log in to cohost if you’re blind, which sucks

I really like cohost but it’s currently inaccessible to quite a lot of people that may otherwise enjoy it which is a bummer, I hope improvements are made before too long you know, I think a big improvement would be finding some workaround to be able to include semantic markup in chosts because everything is basically <div> elements when it comes to user content which… is not accessible, and then of course a lot of the same issues are present in the site’s own markup

in reply to @TVSailor's post: