Live data from Hacker News

Plain Text Sports

plaintextsports.com

101–110 of 113 posts

Re: Plain Text Sports

#102
post #92

Earlier quoted context omitted.

This is something that frustrates me: it's actually really hard to design for screenreaders because it's hard to actually check the results in a free/volunteer context. So you often just have to just hope you're being "semantic" enough. And I did try to use Orca but I just could not get it to work, the TTS service was sulkily disinclined to accept any requests.

Firefox's Accessibility tree inspector is nice.

Link for the curious: https://developer.mozilla.org/en-US/docs/Tools/Accessibility...

Re: Plain Text Sports

#103

Earlier quoted context omitted.

> Does it really need to override my font size? 13px is too small for my display The advent of good browser-based zooming has made non-default font-size users like yourself a small segment. The days of having to author everything in em/rem is mostly over – keeping everything scalable was tedious and prone to issues. I'd bet you encounter issues regularly: explicit font sizes on a root element are a ubiquitous practic…

I'm sure I have "problems" quite often but the sites listed are quite readable. Sure, I would prefer them to use my default font size but something with their contrast, font or otherwise seems to make it not stand out. > non-default font-size users like yourself What does this even mean? The default font is being overridden and irreverent here. Are you suggesting that there is a default default font that is expected…

> Are you suggesting that there is a default default font that is expected to be used across all browsers?

Yes – 16px times new roman.

Almost everything overrides the default font size because almost every browser has a default of 16px, while almost every desktop OS uses a UI font of <13px.

Re: Plain Text Sports

#104
post #70

This does look really nice, and the author should be proud, however I wanted to make a general comment (which isn't a critism of this website). If you aim is to help people who want pure text-based interfaces (the blind in particular), this is much worse than a proper HTML page, which they can easily explore by headers. Well-formed HTML is actually one of the most accessible formats, and drawing boxes with CSS (rathe…

To add – the two aren't mutually exclusive. You can have page layouts with divs and correct tags that screen readers can understand AND draw ascii borders around it.

Yep exactly, heck you could just link in tui.css and go wild making something that looks like text but is 100% accessible with ARIA labels and semantic markup: https://github.com/vinibiavatti1/TuiCss

Re: Plain Text Sports

#105

This does look really nice, and the author should be proud, however I wanted to make a general comment (which isn't a critism of this website). If you aim is to help people who want pure text-based interfaces (the blind in particular), this is much worse than a proper HTML page, which they can easily explore by headers. Well-formed HTML is actually one of the most accessible formats, and drawing boxes with CSS (rathe…

Why not also include an audio file generated from the text of the page with TTS.

By including the audio file, which only includes the readable text, one can avoid the problem of screen readers trying to read ASCII art, decorative elements, etc.

Some news websites, for example Bloomberg, have been including audio files for years. Wikipedia also offers audio files created with TTS.

Re: Plain Text Sports

#106

Earlier quoted context omitted.

Why not also include an audio file generated from the text of the page with TTS.

I believe vision-impaired users would greatly prefer their own TTS, in part because many can listen at 5-10x speed since they're so used to hearing that particular voice.

"... would..."

It sounds as though the author has not actually asked vision-impaired users.

And of course audio is not only for vision-impaired users.

I can play audio directly from a webpage at 5-10x speed easily, but I use the command line programs like ffmpeg/mplayer/mpv/vlc, not a browser like Chrome.

Assuming a Google employee's belief reflects what all web users actually prefer (doubtful!), websites could offer a variety of audio with the same TTS voices that screen readers use.

Re: Plain Text Sports

#107
post #32
post #8

I'd love something like this for European football leagues. The "best" I've found is https://livescore.com but for a while they stopped working on iPhone (they really wanted you to download their app) and I'm quite sure they're probably full of trackers and stuff.

I've used https://m.livesoccertv.com/ or https://www.bbc.com/sport they're not too heavy

https://m.livesoccertv.com/ took more than 4 MB. And if you navigate to Sunday's results it took 18.2 MB, which I think is too heavy. I wish there was something light weight like HN.

Re: Plain Text Sports

#108
post #32

Earlier quoted context omitted.

I've used https://m.livesoccertv.com/ or https://www.bbc.com/sport they're not too heavy

https://m.livesoccertv.com/ took more than 4 MB. And if you navigate to Sunday's results it took 18.2 MB, which I think is too heavy. I wish there was something light weight like HN.

I'd happily throw something together myself by scraping a collection of different sites, but I suspect the "live" part is what could be tough. I don't imagine there's free live scores API floating around. And even BBC's scores are frequently minutes behind. And I don't think this is the kind of thing I can justify spending money on (unless I plastered ads all over it, defeating the original purpose).

Re: Plain Text Sports

#110

Hey, HN! Creator here! I started building Plain Text Sports last year when I was watching an NFL playoff game in rural southwest Wisconsin. We had poor TV reception -- the image was going in-and-out -- and the local radio station was mostly static. I tried to check ESPN, but the loading bar was as frozen as the ground outside. I then had the idea for a website designed for the pure sports fan: no ads, no images, just…

Love it and found it via Gruber's post. Question: why not use a proportional font for all things other than the score? It would make readability much better. Is the output being mapped to individual character widths, that's why? EDIT: One more question, is there a URL I can share that enables dark mode? e.g. https://plaintextsports.com/?mode=dark

Also, Nanum Gothic Coding has a fantastic monospace font that is highly readable. Might be worthwhile for you to consider using this free font since it will greatly increase readability.

It also has the added benefit that the "+" and the "---" align (I only mention this because I noticed the system monospace font on macOS does not align at the box score border "+----")

https://fonts.google.com/specimen/Nanum+Gothic+Coding?catego...

Post reply on HN