No, sorry. I'm no longer accepting extra code complexity for variants. They're incredibly unpopular.

I'm merely getting the NVUI caught up with the standard version of the game. To be clear, I am not adding new festures, I'm sinply naking existing features for sighted players accessible to those who cannot see.

Is there any circumstance you would accept this functionality? Is there any way I could implement it that would satisy your, totally fair, ideal of keeping code complexity down? Is there an LOC, or similar target that would be considered acceptable?

It's not a goal to have all the website features available with NVUI. There are just too many, most of which I would never accept in the website if they were proposed now. Namely, the niche features that only a small fraction of players use. Such as variants.

Many of the website features are only here because it's almost impossible to remove them. All I can do is avoid having their complexity propagate to new sections, like NVUI.

So far I have just been implementing anyrhing my visually impaired friends ask about when I use.
What are ports to the NVUI that it could use that would be accepted as "necessary" so I don't waste my time in the future?

There are too many for me to list them preemptively. We'll have to evaluate it on a case-by-case basis. I recommend you open a discussion before starting to work on the code. It could be in a new issue.