Hello Robin, as far as I know the Lilypond Documentation does not specify the font to be used for this. So the system defaults to a standard monospace font.
So the font will depend on the system. We could ship a dedicated font with the documentation, but I'm not sure if we want that. Cheers, Valentin 04.01.2022 13:01:47 Robin Bannister <r...@dabble.ch>: > > 'Hear hear' to these recent posts from Thomas, Paul and the two Davids! > > I don't object to the fixed width, but the code font has always been spindly > compared to the rest of the documentation text. I find this makes it harder > to read anyway. > > The stroke width I see is 1px (Firefox at 100%). This makes the stroke > dominated by edge effects; the surrounding white dilutes its colour. > Do the WCAG recommendations recognise this? If not, please don't apply their > levels to this case. > > > The demo shows me text that is slightly discoloured. The differences in > colour are so vague that they require attention. Attention to the > differences detracts from attention to the colours. I don't get as far as > judging if attention to the colours aids attention to the text. > > > Cheers, > Robin
