Re: a solution for this problem?

I have been on the Google accessibility list for years, and remember when 
JavaScript change was announced.
The google staffer actually said that only hackers do not use JavaScript.
In a blog etc.
The only  place where I have access to my gmail account in basic html is on 
shellworld.
google thinks it is my home computer, and believe me, its a creative hard 
won  battle, for which I gladly pay for shellworld services alone..but I 
have other reasons to stay of course.
If you have  the cookies from when gmail let you log in with lynx, it 
might be possible, otherwise I  am unsure...sorry!
Kare



On Sat, 14 Jan 2023, Mouse wrote:

>> Verizon is using my Gail account, which still works in basic HTML for
>> me.
>
> You later mention "Gmail", leading me to assume the "Gail" above is
> supposed to be "Gmail".
>
> If so...what do you have to do to make that work?  One of my workplaces
> uses Google for their mail and, they said that "starting March 24,
> 2022" we "won't be able to sign into [our] accounts on browsers that
> don't support JavaScript".  The actual date was somewhat after that; I
> haven't been able to find any record of exactly when, but it happened.
> And I just now tried again and got
>
> | Couldn't sign you in
> |
> |    The browser you're using doesn't support JavaScript, or has JavaScript
> |    turned off.
> |
> |    To keep your Google Account secure, try signing in on a browser that
> |    has JavaScript turned on. Learn more
>
> Of course, it don't bother explaining how requiring the exposed attack
> surface of a JavaScript engine can possibly make anything more secure
> than...not.
>
> I would *love* to switch back to using lynx, but I haven't found any
> way to get anything more useful than the misleading refusal above.
>
>> However, when I hit enter on this link, I get a badly formed address
>> error...which I admit is new.
>
> It's been a while, but I do have a fuzzy memory that, years ago, I
> found lynx erroring on links that "worked fine everywhere else" but
> were not actually well-formed according to the spec.  Unfortunately,
> that memory is too fuzzy for me to say much more.
>
> /~\ The ASCII				  Mouse
> \ / Ribbon Campaign
> X  Against HTML		[email protected]
> / \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>
>