René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Consider white background for docs","articleBody":"\u003c!--\r\nPLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.\r\n\r\nISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.\r\n--\u003e\r\n\r\n## I'm submitting a...\r\n\u003c!-- Check one of the following options with \"x\" --\u003e\r\n\u003cpre\u003e\u003ccode\u003e\r\n[ ] Regression (a behavior that used to work and stopped working in a new release)\r\n[ ] Bug report  \u003c!-- Please search GitHub for a similar issue or PR before submitting --\u003e\r\n[ ] Performance issue\r\n[ ] Feature request\r\n[X ] Documentation issue or request\r\n[ ] Support request =\u003e Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question\r\n[ X] Other... Please describe: AIO css\r\n\u003c/code\u003e\u003c/pre\u003e\r\n\r\n## Current behavior\r\n\u003c!-- Describe how the issue manifests. --\u003e\r\nBackground of all pages is a light (20%) gray.\r\n\r\nThese light grays have been used extensively on the web because they soften the harsh black-and-white look. They also reduce contrast, which with some background-text combinations (such as 80% gray text on 20% gray background) makes the doc harder to use for some users. \r\n\r\nLight gray background also means that all graphics need to either be transparent or have borders so the white background of the graphics looks normal. \r\n\r\n## Expected behavior\r\n\u003c!-- Describe what the desired behavior would be. --\u003e\r\nIt would be interesting to see if a white background improves readability/look overall, esp with the blue font areas, in tables, and near graphics. \r\n\r\n## Minimal reproduction of the problem with instructions\r\n\u003c!--\r\nFor bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via\r\nhttps://stackblitz.com or similar (you can use this template as a starting point: https://stackblitz.com/fork/angular-gitter).\r\n--\u003e\r\nSee https://angular.io/guide/architecture#whats-next\r\n\r\n\r\n## What is the motivation / use case for changing the behavior?\r\n\u003c!-- Describe the motivation or the concrete use case. --\u003e\r\nAccessibility\r\nEase of creating graphics that look well-integrated with the site\r\n\r\n## Environment\r\n\r\n\u003cpre\u003e\u003ccode\u003e\r\nAngular version: X.Y.Z\r\n\u003c!-- Check whether this is still an issue in the most recent Angular version --\u003e\r\n\r\nBrowser:\r\n- [ ] Chrome (desktop) version XX\r\n- [ ] Chrome (Android) version XX\r\n- [ ] Chrome (iOS) version XX\r\n- [ ] Firefox version XX\r\n- [ ] Safari (desktop) version XX\r\n- [ ] Safari (iOS) version XX\r\n- [ ] IE version XX\r\n- [ ] Edge version XX\r\n \r\nFor Tooling issues:\r\n- Node version: XX  \u003c!-- run `node --version` --\u003e\r\n- Platform:  \u003c!-- Mac, Linux, Windows --\u003e\r\n\r\nOthers:\r\n\u003c!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... --\u003e\r\n\u003c/code\u003e\u003c/pre\u003e\r\n","author":{"url":"https://github.com/jenniferfell","@type":"Person","name":"jenniferfell"},"datePublished":"2018-05-18T01:12:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/23983/angular/issues/23983"}