My spouse and I own a condo. The property management company that the home owners' association hired is generally mediocre (which is a huge step up from the usual scenario where most are actively awful). They do a reasonably good job of keeping us informed, but they way they do it is hilariously bad. Every email they send is sent as a .jpg and a .docx file with no actual text in the message. My email client renders it and I can read it, but it makes all of their emails unsearchable, and it makes filtering beyond the basic "emails containing address x" impossible.

I've asked them personally several times both electronically and in writing to please stop sending such correspondence and just send a regular email. (I honestly don't care whether it's plain text or HTML, just so long as it's searchable and filterable.) But it's so far been to no avail. I brought it up at the last HOA meeting and they agreed to also include their messages as text in the body of the email, but they don't. If I'm really lucky they'll have one or two sentences in text, but the rest is a .jpg and a .docx (or .pdf) of the actual body of the message. I've tried to explain that this is bad for people with disabilities and may even run afoul of the Americans with Disabilities Act, but they didn't seem to care.

It's not clear to me how one ends up sending emails in this form. I don't use any Microsoft products, which they probably can't comprehend, but I suspect this is some sort of Windows thing. Does anyone know how this happens and why? And more importantly, does anyone have suggestions for getting them to stop?

I presume a lot of you might have noticed the discourse surrounding Sekiro and the notion that games like Sekiro could benefit from having a complementary "easy mode". The discourse is hot, and the takes are flying left and right but I'm curious to what the people of Tildes think about it.

I have poor vision and I rely heavily on a Firefox plugin called Stylus to make websites readable - in particular the trend for low contrast and small text. That includes Tildes.

I updated it to v1.5.0 and now the styles I set for Tlldes no longer work - most other sites still appear to work but I've not checked them exhaustively.

I immediately tried rolling back a release or two (1.4.23 and 1.4.22) but those versions no longer work for any site. I tried randomly downgrading to even older versions but the same result. I think I'm stuck with the latest version..

I notice in the browser console there are 2 errors reported on Tildes e.g. on this page I see:

Content Security Policy: The page's settings blocked the loading of a resource at inline ("script-src"). new_topic:1:1
Content Security Policy: The page's settings blocked the loading of a resource at inline ("style-src"). new_topic:1:1

Using the Firefox Developer tools Inspector - I see my style settings for Tildes injected by Styuls (after the body) but they do not work any more.

Since only Tildes so far is not working with my Stylus settings I guess there is also a recent change to Tildes that is causing Stylus to fail.

This is a rather serious issue for me as all the colour options in the setting are low contrast and cause eye strain which becomes painful without the Stylus settings.

Thanks for any help you can offer.

I ran a Lighthouse audit for performance and accessibility on a comments page (specifically this one); the results are pretty good on the whole, but there are definitely a couple of things I think ~ could do better.

Performance

IMO the performance of ~ is fine; Chrome thinks that the time to first meaningful paint is a bit high (3.1s on a simulated 3G connection with CPU throttling), but I don't know what you can do about that without doing things like inlining all the CSS, which would make the very first page load faster but hurt every request after that. Maybe minifying the CSS/JS would help? I don't know if the performance benefit would be enough to justify the increase in complexity to handle the minification, and you'd also lose the easy legibility of the source (which I personally really like).

Accessibility

There's some really small text on ~! The Lighthouse audits I ran don't catch it, but the SEO audit does, and it's not hard to see it with your own eyes either. The suggested minimum size for easy reading in that audit is 16px, which is the current size of all post and comment text on desktop, although mobile only gets 14px (I don't know if this is actually a problem, since you probably hold your phone closer to your face than your monitor).

Edit: posting this from my phone - yes, the 14px font on mobile is definitely harder to read than 16px would be. I don't know if that's just me (I have a fairly severe visual impairment), but I would definitely prefer 16px text everywhere, not just on desktop.

There's also a good amount of text that doesn't have a great deal of contrast (even using the default white theme – I'm sure it's much worse with Solarized). This is mostly all the grey text, although Lighthouse also complains about the links when they're on a grey background (especially the "visited" colour, which is much closer to grey than the normal colour).

Some specific examples: The timestamp and "Link" text for each comment is only 10px, which is a bit small for me, especially with the low contrast on "Link". Similarly, the post timestamp is a bit hard to read.

The worst offender by far, though, is the "Comment deleted by author" notice (example). It's tiny and grey and incredibly easy to miss, and is directly relevant to the flow of the conversation, unlike the timestamps. I'd really appreciate it if that could be bumped up to at least as large as usernames are currently displayed.

Hi!

This isn't a topic I know a ton about (beyond basics like the need for image descriptions for screen readers), but @nil's layout bug stemming from a very large font got me thinking about accessibility.

Has accessibility been discussed and worked on so far?

(If not, I'd like to suggest taking a look at online accessibility guidelines to see what would apply to tildes in particular. It's one of those things that's easiest to add towards the beginning of projects, and it takes making a conscious decision to include it.)