>The same with standards, and you are misunderstanding on purpose.
While I get what you mean, the use of the term "standards" just conflates an orthogonal issue.
You can be 100% standards compliant and not readable on Lynx, or 100% standards compliant and readable on Lynx.
Relying on JS is not some niche obscure corner or some bypass of the standards as per the English/Greek analogy. It's basically the norm for most SPAs today.
The problem is that the standards are not compliant with Lynx (or rather that Lynx is not compliant with the standards).
What you want is not Google to use the standards, but to use the part of the standard that is about simple, not JS dependent, HTML.
While I get what you mean, the use of the term "standards" just conflates an orthogonal issue.
You can be 100% standards compliant and not readable on Lynx, or 100% standards compliant and readable on Lynx.
Relying on JS is not some niche obscure corner or some bypass of the standards as per the English/Greek analogy. It's basically the norm for most SPAs today.
The problem is that the standards are not compliant with Lynx (or rather that Lynx is not compliant with the standards).
What you want is not Google to use the standards, but to use the part of the standard that is about simple, not JS dependent, HTML.