@gaditb idk if you break lynx you probably break braille too
which, i think you should support braille
@Lady I think you SHOULD support braille, yeah, but I wasn't thinking of "to do things accessibly" or "to make a statement about accessibility".
Similar to "Best Viewed in Netscape/IE/Chrome" -- or, websites being written in X particular language and not having a translation (or, frankly, many unusably sparkly and bad-colored Geocities pages and Tumblr themes) -- those aren't a matter of deliberate exclusion (well, except e.g. some of Google's c. 2012 Chrome Experiments stuff). they're just the result of a person having a specific render-tool that is in their loop of building the site, for their one-person test audience of themself-using-that-one-tool.
And being satisfied with that, because they didn't really care much about an audience far beyond themself.
If you're PUBLISHING publishing, yes definitely if you can't do lynx and braille you should Feel Very Bad, but I think, like, more people should build unimportant things to a primary audience of themself-using-a-screenreader.
@Lady Probably would be, de facto. I'd be interested (in addition) to see if someone could put together a website that works in a screenreader but is borked in Lynx. Just to see if it's possible (and if that uses some interesting effects).