but, you can do both, right? that's what alternative text titles and descriptions of images are for, and the font is used to render test that has already been d

but, you can do both, right? that's what alternative text titles and descriptions of images are for, and the font is used to render test that has already been downloaded as utf-8/ascii/whatever characters making up the content of the html tags in the document. lynx exists. screen readers for the blind exist. that's no reason to try and downgrade the aesthetic experience for everyone else. i mean, i remember usenet and gopher, the web and html are just better, prettier, nicer to look at - a well laid out and designed page of content makes me happy, assuming the content is something i'm interested in, but even that isn't nescessary sometimes. and sure, i'm sad for vision impaired people who can't experience that, and sites that don't provide accessible versions of their content are bad and wrong, of course - but that doesn't mean i need to dilute my own experience to match. it'd be like banning people from going hill-walking because wheelchair users can't participate. the correct response it to try and work out how to include and enable access foir the wheelchair users without destroying the experience for everyone else - put in a cable car or something, i don't know. so yeah, i agree with your sentiments in the last two paragraphs above, i just think there's a better way to solve that problem - upgrade everyone's experience.