If you rely on assistive technologies (TTS, Braille display, enlarged fonts), what would be your preferred terminal output from a compiler or other CLI tool telling you where an error occurred

@TheQuinbox I think that proposed format would still work with the go-to file and line behavior of many terminals, so that would be an addition benefit. In context, without additional information, is that output clear enough for most people? How would it sound as proposed. And what about path/to/file.rs:10, col 29? Maybe the column isn't necessary in most cases...

@ekuber Hmm, yeah, putting , col 29 is a good way to do it too. I like that a lot

@ekuber you could also use a unicode arrow instead of `->` but it is honestly the worst option. Consider using the `@` sign which has the convenience of search uniqueness. For line and column people will get used to whatever you do but it might be nice to tie the form to verbosity setting. also a different separator for path and line:column, again for quick `/:` search. A screen reader landing on colon would generally read both the line and column since the selection is in middle of a "word".

@bondolo I want to avoid Unicode symbols for this because they tend to be super verbose on TTS ("THIN RIGHT ARROW" would be terrible). The option of doing "path/to/file.rs:10, column 29" is appealing to me because that keeps both readable information *and* the terminal hyperlink behavior to open the file at the right line.