Just talking about accessibility, maybe interesting, Wikipedia on mobile allows to scale, but setting a minimum and maximum scale:

I have this look on Windows for

a {
  outline-style: auto;
}

Last Chrome	Last Firefox

This is the same as Q132: Why is there an `outline-style: none;` declaration for all links within Phorge/Phabricator?

In T15056#3210, @golyalpha wrote:

Another example of broken dark theme

When an fatal exception is triggered :

Because there are more and more referenced issues and, because some of them may need further discussion in order to find the best solution, IMHO it may be a good idea to create a sub task for each issue reported isn't it ?

Another on when displaying a maniphest with a lot of comments :

Concerning the dashbord's big pannel :

In workboard, when a maniphest's is drag and dropped, available triggers information windows is broken.

In workboard, when maniphest's edit button style is broken on mouse over.

I'll do it next time, I always do my best to serve my master !

Yeah bob, feel free to add your nice screenshots in the Task description for more visibility. You are a good minion!

In workboard, empty column's drop zone is a little bit 'agressive' isn't it ?

Hi, I can also see this one that looks weird in big pannels available on dashboards

Also, I apologize for not completing this, hadn't had much spare time until recently. I will work on this soon.

Done.

Hi @Bukkit can you please publish F281219? thanks :)

I don't see file F281219

Yeah but I think the "Normal" priority is better than "Low" since we are hackers hating white screens and so that is quite important ihih

"experimental" means "not really working yet"... When it's fully usable, the "Experimental" label can be removed.

The evidence that there are unfinished areas in dark mode is in its option, the option reads: Dark Mode (Expirimental). Users may opt into this 'expirimental' dark mode without realizing that there are unreadable areas until they go depper in the sea.

I agree that a small link to the original macro page would also be useful. Also, this mitigates some potential copyright troubles, since sometime the macro page contains some credits and disclaimers.

From reading the last messages in T109 (starting https://phabricator.wikimedia.org/T109#8874116), it sounds like adding that text will be bad for screen readers, because it will add lots of repetitive, "un-useful reading" to the page.