There should be a reasonable amount of accessibility markup too (in how it's structured plus some specific accessibility items) for screen readers as well.
Seamonkey is an old school fork of Netscape before they pulled out Firefox. I suspect the CSS rendering is marginal CSS 2.
I use Seamonky on OpenBSD i386 arch as Firefox no longer supported. I am using deliberately low spec computers for personal surfing.
The links render shows the 'skip to main content' link which is always a good sign that accessibility has been addressed.
Loads fast, looks clean, content seems to be available - each of the 'cards' opens a page with a graphic, a table of contents in a contrasting grey colour and then text giving information. There is then a 'classified ads' section with links at the bottom.
Looks identical on my 'normal' machine with Firefox 102-esr and ublock origin and more ram/faster processor &c.
A quick look in the text mode browser links in a uxterm window showed that text content was available. The home window links show as two rows of text links - works ok.
I'm on a pretty fast G4 'mobile broadband' connection in UK with around 2.5Mb/sec (probably the old Thinkpads wifi limit) and around 45 mSec latency from ping.
Just one observation:
https://allaboutberlin.com/ works fine
https://www.allaboutberlin.com/ gives a page not found.
This reply is not very timely - I'm not logged in on HN that often!
