Earlier quoted context omitted.
Gemini is to a large degree a reaction to the commercialization of the web, all that huge load of Javascript etc. arose through the ad economy. Accessibility isn't that, accessibility is something that people trying to do business would prefer to avoid. But letting the disabled be first-class citizens in an online community alongside the rest of the population is a matter of justice. Adding accessibility features isn…
> Adding accessibility features isn’t making a standard "bloated", it is simply doing the right thing. Yes, and the other million people are going to say their proposed features are "simply doing the right thing". It may be that marking up what language a short except of text is in is a good feature to have (and would be fairly easy to achieve if Gemini used the Markdown format as you could simply us a tag). A counte…
Gemini does aim at being more than text[0]:
> The "first class" application of Gemini is human consumption of predominantly written material - to facilitate something like gopherspace, or like "reasonable webspace" (e.g. something which is comfortably usable in Lynx or Dillo). But, just like HTTP can be, and is, used for much, much more than serving HTML, Gemini should be able to be used for as many other purposes as possible without compromising the simplicity and privacy criteria above. This means taking into account possible applications built around non-text files and non-human clients.
Lots of documents and books contain passages in other languages, it's reasonably common -- I don't get why people are saying this is a niche concern. Books get around that problem because they have controls around presentation, and they're not designed to be consumed visually, not as a semantic, parseable format. But Gemini, at least in theory, is designed to be parseable.