Optimal layout for readability?

Seeing in the history of this template and the fact it was once just an incredibly tall column certainly, breaking it into two like so certainly makes more sense from a page layout perspective. However, I find the fact it has duplicate headers that logically follow directly on from one another but are spatially separated makes it a little more awkward to comprehend than necessary. To remedy both of these issues, I propose an unbroken completely horizontal layout instead, like so:

Ability Score Modifier Chart
Ability Score:	0	1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18	19	20	21	22	23	24	25	26	27	28	29	30
Modifier Value:	-5		-4		-3		-2		-1		+0		+1		+2		+3		+4		+5		+6		+7		+8		+9		+10

An additional idea would be to embolden the text of Ability Score "10" to allow the eye to pick it out as a central reference point, given as it is the 'neutral mark' on the ability score scale.

- — unsigned comment by AstraTheDragon (talk) 20:33, 26 October 2023

I feel like you've discovered for yourself the very reason why we would rather have a tall ability table than a wide one. Even with the font size changes the table hangs off of my view because I look at the wiki with half monitor. I personally favour the current compact template over both a single vertical and single horizontal table, though I might just be biased because it's the one I've always seen

-Sky (talk) 20:39, 26 October 2023 (CEST)Reply[reply]

Using a horizontal table would cause problems for mobile users, and isn't very accessibility friendly. Willowisp (talk) 20:42, 26 October 2023 (CEST)Reply[reply]