Here's a few points about the logistics and reasoning of why I did things this way:
The typical practice of script conditions is to release one file that can be configured by the user. This is seen in all other large script releases (see Axem's scripts, and even the command line for FSO itself). Generally the default settings are good for many users, but if a user does want to change a setting they can edit a line in a text file, which is good practice and helps many folks get more comfortable with the idea of possibly trying out modding themselves. (Speaking from personal experience and things I've seen with many other folks). The user options within this script are setup similarly to editing a table file or the command line, so the idea was following the practice setup by this community
If someone who wants to change a lighting setting in the command line is comfortable reading about that setting on the wiki and changing the value, the goal was to make it about the same experience as reading what the script settings do and changing that in the user options section of the file.
Having multiple iterations of the same release with one setting that is slightly different can lead to confusion, and it's much more difficult to keep things efficiently updated on the release logistics side of things. If each slight iteration had to be its own file, then that leads to many permutations of files (such as a grey scale that is 4k, grey scale that is 1080p, large text that is gray scale, large text that is 4k, etc). As an aside, I'm a teaching by nature and training, so I'd rather take the time to show someone how to change something then just give them a different file each time they want one setting changed
I'll also note that this script already scales by resolution. If the resolution is <1024, the script changes size and uses the smaller default text. If resolution is > 1024 but less then 3200 then it uses the default medium size text, and if resolution is higher, it uses the largest default text.
Regarding the landscape orientation to match the retail gauge style: the only two configurations I have coded in are the vertical and horizontal ones shown in the screenshot on the first page of the forum. These configurations allow for longer names to be displayed, whereas the landscape default of FS does not easily allow for that (hence why I went with those two options).
The accessibility option is something that I have thought about as well, and I definitely support the overall goal of making FSO more accessible!
Right now, the gauge can be set to use larger text and sizes in the options.
A grey scale version can also be used, and it was suggested to be during development of the script
To use the grey scale version all the user has to do is find the line
'CustomWingGauge.isgrayscaled = false'
and change it to
'CustomWingGauge.isgrayscaled = true'
The tricky part about making this single gauge much larger at the 1080 resolution is that the rest of the gauges will still be the same size, and this will look strange and have a higher probability of overlapping. The larger goal would be to have a HUD that scales all the gauges up if someone wanted the HUD to be larger, but that is alas far beyond the goals of this script.
Perhaps that was more exposition then you might have been looking for
I hope it helps explain my reasoning for things, and I very much appreciate your support and enthusiasm for the script! If you'd like I could make the default of the gauge to use the horizontal configuration, so it does not overlap any other lower gauges.