-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document convention - Unnecessarily hard to read high stakes information #359
Comments
Apologies - I'm not sure why the quoted text has come through with an underline. It wasn't a deliberate attempt at irony |
Thanks for submitting the feedback. I'm not responding yet to the substance of your issue, but just to this comment:
The problem was unescaped HTML. I edited your issue, changing <ins> to |
Gathering some details about this. @mr45144 , on which browser and operating system did you observe the content? For comparison, in Windows 10 I see the following in Chrome 126: and in Firefox 127: |
This is a style that is set by the W3C document style in the CSS used for the |
It was noted in Edge and explored further in Chrome - both on Windows. On both font size is medium but I think the OS is set to 125%. |
Hi @fantasai Is this something we could make easier to read? My understanding is that the issue happens when large chunks of text are wrapped in Thanks much. |
Comments as requested by recent email)
Document Conventions require "Replacement text that is presented to show how an SC would read as modified by the advice in this document are in elements visually styled as bold green text with a dotted underline."
For an accessibility organisation this is ironically very difficult to read with corrected eyesight let alone if more spacing is required for print-disability. The underline is tight up against the descenders/bottom of all characters even when applying the requirements of 1.4.12.
**Expected behaviour ** A document from W3C should be stylistically designed for accessibility.
As published - hard to read
With text spacing - even harder to parse
Without underline - still distinguised by bold and [ text ] - significantly easier to parse
The text was updated successfully, but these errors were encountered: