Accessibility question

[Sir Osis of Liver]

The font sizes are a mix of em, px, and %.  Just on board index -

  font: 95%/115% Roboto, verdana, Helvetica, sans-serif;

  font: 78%/130% Roboto,"Verdana", "Arial", "Helvetica", sans-serif;

  font-size: 0.85em;
  font-family: Roboto,verdana, sans-serif;

[Antechinus]

It looks like it looked to me on my phone yesterday. Size in % is fine. That has always been zoomable.

Although iPhone is obviously not Android, and all previous discussion in this thread was about Android. And Firefox for iShiz is up to Version 129 now. 115 is out of date.

Anyway, it should be able to zoom text without issues in default form. If you have somehow managed to stop it doing that, it's an impressive accomplishment.

[Sir Osis of Liver]

I'm on my Samsung tab, Android, using FF 68.0.2.  There is no browser setting for default zoom.  FF 115 for Windows is the latest supported version for Win 8.1, it's on extended support until Sep 24.  I think the important point here is that try as you might to format a nice looking forum, it can display quite differently on different devices using different browsers and operating systems.  To some extent it's an exercise in futility, as are most things in life.

As a side issue, quick edit does not work on this tab.

[Antechinus]

Well now we're back to Firefox 68, which hasn't been patched for years. If you are running obsolete browser versions then you are pretty much on your own, and having tested it I know the problem is not with the Nightbreeze theme.

[Aleksi "Lex" Kilpinen]

Windows 8.1 End Of Life was also almost 2 years ago. Even though the browser still might have received security updates until last week, the OS is long unsupported.

[Illori]

he said on android, i assume the tablet has different versions of FF then on windows.

[Arantor]

Given that FF 68 for Android expects Android 4.1 and we're expecting Android 15 any day now, and that current FF for iOS is version 130, I'm going to assume that the browser really is several years old.

[Aleksi "Lex" Kilpinen]

he said on android, i assume the tablet has different versions of FF then on windows.

They are actually pretty much the same.
Android is on 129, Windows is on 130.

[Illori]

he said this is a kindle fire tablet, those are not always on the most updated android OS and i bet the amazon app store may be outdated as well.

[Aleksi "Lex" Kilpinen]

I'm on my Samsung tab, Android, using FF 68.0.2.

Samsung Tab, not Kindle Fire. The Kindle was mentioned earlier.
Kindle Fire is not strictly speaking even Android, while it is based on Android though, can't really say for compatibility - I have no experience with any Kindle device. https://en.wikipedia.org/wiki/Fire_OS

[Illori]

the user has the kindle SOoL has the samsung tab. i think it was the users device that has the issue with firefox.

[Arantor]

Does it matter? If it's on Firefox 68, it's aiming for 5 year old browser. It's also out of support - 68 isn't even an extended support release, the oldest I can find of those is 78 and that was EOL'd 3 years ago.

In equivalent terms this is trying to support the pre-Chrome version of MS Edge.

There are times I wish we were back in the IE 6 era! It might have been janky but it was supported for years and didn't exist in this era of landfill technology.

[Sir Osis of Liver]

Windows 8.1 End Of Life was also almost 2 years ago. Even though the browser still might have received security updates until last week, the OS is long unsupported.

Win 8.1 went eol in Jan 24, it was on extended support.  It's a better OS than Win 11, running on a better computer than the new one I purchased in April.  I'll continue using the 8.1 desktop until it won't do something I need to do.  The problem being discussed here concerns forum display on tabs.

Well now we're back to Firefox 68, which hasn't been patched for years. If you are running obsolete browser versions then you are pretty much on your own, and having tested it I know the problem is not with the Nightbreeze theme.

You did mention a problem with Nightbreeze display template.  My Samsung tab is running FF 68, current Android version is 121.  No idea why it hasn't updated, don't think I disabled auto update on the tab.  I only use it as ereader, and occasionally to view one of my forums or this one, and it displays them fine.

he said on android, i assume the tablet has different versions of FF then on windows.

My original post concerned a new Kindle Fire, the OS is a fork of Android, it's been crippled to discourage users from doing things that don't involve Amazon.  My Samsung tab is running Android, just using it to get an idea what forum looks like on different devices.  I use FF responsive design mode to view phone emulations.

There are times I wish we were back in the IE 6 era! It might have been janky but it was supported for years and didn't exist in this era of landfill technology.

I miss Netscape.

[Aleksi "Lex" Kilpinen]

Eh, no 8.1 Extended support ended in January 10, 2023.

[Sir Osis of Liver]

Hmm, appears you're correct.  Nonetheless I'll continue using it.  Not suggesting anyone else should.

[Arantor]

Mainstream 8.1 support ended in 2018, extended support is only for the people paying Microsoft the big bucks - since by 2023 the cost would have been $400 per machine to receive it. (Started at $50/machine and doubled each year). So, uh, what are the odds you paid the extra hundreds of bucks for security patches since 2018? Because you had to pay to get them and you'd likely remember paying...

Hope you don't get hacked. There are known security holes that have not been (and will not be) patched, and many of them are readily discoverable from reverse engineering Win10 patches.

Win10's extended support is allegedly going to start at $61/machine for the first year (less for schools) but also double every year until it's cut.

Using old browsers and devices seems like a good idea - it's environmentally more friendly, it's better for the budget but *it is not safe and pretending otherwise is foolish*.

[Sir Osis of Liver]

Mainstream 8.1 support ended in 2018, extended support is only for the people paying Microsoft the big bucks - since by 2023 the cost would have been $400 per machine to receive it.

You may be right (you usually are), but I don't remember any of that and wasn't paying for support.  I'm aware of the risks, but have worse things to worry about.  As it turned out, auto update hadn't been working since I started using the computer in 2014, so I'd been running the original OS plus a few updates that were installed when I first set it up.  Was able to fix it (database problem) and installed 110 updates around the same time I bought the new desktop. 

[Antechinus]

Well now we're back to Firefox 68, which hasn't been patched for years. If you are running obsolete browser versions then you are pretty much on your own, and having tested it I know the problem is not with the Nightbreeze theme.

You did mention a problem with Nightbreeze display template.

I said that the font size set by default for post content was ridiculously small for use on a phone. Which is very easy to fix. Apart from that the theme seemed fine.

[Sir Osis of Liver]

Well, yes, that's pretty much what this topic was originally about.  What it boils down to is the only way to see if css changes help an elderly member is to look at the forum on his device, and hope it looks ok on all other devices for other users.

[Antechinus]

If you change the font-size for post content it will affect all viewers equally. It's such a basic bit of CSS that every desktop and mobile browse under the sun has supported for ages. Just bloody do it.

Code Select Expand

.post .inner {
font-size: 1rem;
line-height: 1.5;
}
It's that simple. Yes, I just tested it live. Stop yer ******ing and go do it.
Or, if you want to get fancy, and leave it the same as it was on desktop:

Code Select Expand

@media screen and (hover:none) {
.post .inner {
font-size: 1rem;
line-height: 1.5;
}
}
Or if you really want to get super-duper fancy, and make things a bit easier to read for those of poorer eyesight, without making it look broken up, by employing subtle and sophisticated typography tricks...

Code Select Expand

@media screen and (hover:none) {
.post .inner {
font-size: 1rem;
line-height: 1.5;
letter-spacing: .02em;
word-spacing: .04em;
}
}