Does not meet WCAG standards for accessible text

[Korilakkuma]

Describe the Issue

Does not meet WCAG standards for accessible text according to check by browser.
Actually, I think that this contrast is hard to see ...

Expected Result

Actual Result

[rtoy]

Can you explain how you got the image for the actual result? When I use Firefox (on mac), I pretty much see that the draft document looks very similar to the candidate recommendation image. In particular, the table of contents is not white text on a black background; it's black text on a white background). The "Latest published version" looks black to me. (The element inspector says the color is black: rgb(0,0,0).)

[Korilakkuma]

Maybe, the contrast is hard to see in the case of dark mode (macOS Catalina). Therefore, to set light mode, the contrast is easy to see.

[rtoy]

Ah, I see. Yes, in dark mode, the draft spec is basically illegible. But the latest published version looks fine. I think we should update the draft to do whatever the published version does. Would that work for you?

Or are you expecting the main text to work well in dark mode with white text on a black background?

[Korilakkuma]

you expecting the main text to work well in dark mode with white text on a black background

Yes. Because the latest published version looks fine. Therefore, I expect that the main text to work well in dark mode with white text on a black background.

[rtoy]

Weird. On my Mac, the published version has black text on a white background when I turn on dark mode. Are you saying this should be white text on a black background? That's not what I see in dark mode.

But I agree that the draft version is definitely broken in dark mode. I'll have to dig in to the differences between the draft and published version. I don't think we made any changes about that.

[rtoy]

This could be related to bikeshed now supporting dark mode. See speced/bikeshed#1773

[rtoy]

See speced/bikeshed#1790.

[rtoy]

This should be fixed soon. Thanks for reporting the issue.

[rtoy]

Bikeshed fix is done. I'll have to wait a bit until the changes propagate and then wait for the next PR to update the spec or force Travis to run and update the spec.

[Korilakkuma]

Thanks !

[rtoy]

By chance I found another typo in the spec. (Well, bikeshed-o). When bikeshed is updated I'll fix the typo and get a new version up. So I don't forget where it is: https://webaudio.github.io/web-audio-api/#dom-baseaudiocontext-createbuffer-length. It says "atleast 1", not "at least 1". This is bug speced/bikeshed#1470.