35

Yes, the small caps you're using are bad for machines. People also may have issues with them. AceCalhoon pointed us in comments to a question on Super User about the usage and purpose of these glyphs. The top answer explains they're not intended for usage as regular written text, and that trying to use them that way breaks stuff: Those characters are not ...


18

Yes, let's do this. Make the d6 use numbers instead of pips. Theory background. Using text to represent graphics isn't really accessible, and tends to be done primarily because it “works” for people without accessibility needs. Using layout tricks to move “U+2022 BULLET” around the screen is a tidy example of how visual-centric design accidentally defeats ...


18

(Foreword so I can actually sound trustworthy as I write about this: I've been an accessibility developer for the past few years doing things exactly like this.) We don't actually have to change the appearance of the dice. Since we're dealing with screen readers, we can also make a change that targets screen readers specifically and gets them to read out a ...


16

The F in your iterations of Let Us Discuss This Further appears as a white box for me. Kind of a case-in-point: if this is happening to me, it’s happening to others, it’s degrading the readability and accessibility of the website, and therefore it should not be done. This site does not offer any feature that will correctly render small caps, and faking it ...


15

The observation is founded 1. Style is secondary to comprehensibility Though we do prefer to maintain the style used in sources, this isn't a hard rule and is always secondary to making sure posts are comprehensible. We also have a limited palette of styling tools available and have to make do with them. 2. These aren't small-caps anyway These aren't ...


13

You're right, there's an accessibility issue with these colors. The colors are #9f8010 for text and #fffdf7 for background. That gives us a contrast ratio of 3.7. The WCAG 2.1 contrast ratio guideline says that text at this size needs to have a ratio of at least 4.5. A ratio of 3.7 is mostly okay for those of us with good eyesight, but people with poor ...


12

The reasons are well-founded. The original question was not written in English. This meant it was extremely difficult to access the page using a screen reader. The SuperUser question Why shouldn’t I use Unicode characters to simulate typographic styles (such as small caps or script)? (linked a couple of times already) has a lot of reasons but it misses the ...


10

The fix Fake headers are easily fixed. When you want to make a header, there are three ways to create one: Click the Heading editor button: Select the heading text and type ctrlh. Manually type the Markdown code for a header, which is either an underline made from dashes or equal signs, or one to three hash marks in front of or surrounding it (“or”, ...


7

This is an odd Windows feature, it appears. What I discovered, after experimenting on Meta.SE, Christianity.SE, and here is that sometimes, after hitting window + H, to enable voice to text, you have to toggle the little microphone icon on and off once or twice to get it to work in the SE chat or the SE question/answer box. Not sure if Apple stuff behave ...


3

Be careful with level 1 headers The title of the question is an H1 (source: I just checked), and the entire question should be subordinate to ("below") the title. If the question contains a separate H1 in its body text, then this semantic relationship will fail. Putting an H1 at the top of an answer is not necessarily wrong, since the answer is a separate ...


Only top voted, non community-wiki answers of a minimum length are eligible