Wikipedia:Color coding music genres
 | This is an essay. It contains the advice or opinions of one or more Wikipedia contributors. This page is not an encyclopedia article, nor is it one of Wikipedia's policies or guidelines, as it has not been thoroughly vetted by the community. Some essays represent widespread norms; others only represent minority viewpoints. |
 | This page in a nutshell: Color coding of music genre infoboxes is confusing to those outside of WP:Music and goes against WP:COLORCONTRAST |
I was actually about to start a discussion on such a change. All Wikipedia pages should meet the standards of Web Content Accessibility Guidelines (WCAG) 2.0 Level AA, including SC 1.4.3 (contrast.) As you have noted, many music genre infoboxes do not. In fact, Category:Articles using Template:Infobox music genre with invalid colour combination is one of the largest extant accessibility tracking categories. This is a not-insignificant issue. I think equally as important is that differently-colored infoboxes for genres ultimately impart no additional information to the reader. There is no indication on the infobox itself that the color relates to a genre (or in some cases, super-family of genres) or has any particular meaning whatsoever. The only guide to the colors exist on this page. I believe that for both of these reasons the bgcolor and color parameters in Infobox music genre and music genre footers should be deprecated. There's really no reason that they need to be colored other than that's how we've always done it.
- https://en.wikipedia.org/wiki/Category:Accessibility_issue_tracking_categories
- https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Accessibility/Infoboxes
- https://en.wikipedia.org/wiki/Wikipedia:Colour_contrast
- https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Music/Music_genres_task_force/Colours
- these too https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Music/Music_genres_task_force/Footer
- Some readers of Wikipedia are partially or fully color-blind. Ensure the contrast of the text with its background reaches at least Web Content Accessibility Guidelines (WCAG) 2.0's AA level, and AAA level when feasible (see WCAG's "Understanding SC 1.4.3: Contrast (Minimum)"). To use named CSS colors for text on a white background, refer to Wikipedia:Manual of Style/Accessibility/CSS colors for text on white for recommended colors. For other usage, here is a selection of tools that can be used to check that the contrast is correct:
- The Colour Contrast Analyser enables you to pick colors on the page, and review their contrast thoroughly. However, be sure to only use the up-to-date "luminosity" algorithm, and not the "color brightness/difference" which is outdated.
- You can also use Snook's color contrast tool, which is entirely up-to-date as of 11 January 2015[update].
- Google's Chrome Canary has a color contrast debugger with visual guide and color-picker
- Several other tools exist on the web, but check if they are up-to-date before using them. Several tools are based on WCAG 1.0's algorithm, while the reference is now WCAG 2.0's algorithm. If the tool doesn't specifically mention that it is based on WCAG 2.0, assume that it is outdated.
- Additional tools can be used to help produce graphical charts and color schemes for maps and the like. These tools are not accurate means to review contrast accessibility, but they can be helpful for specific tasks.
- The color scheme generator helps to choose a good set of colors for a graphical chart.
- Color Brewer 2.0 provides safe color schemes for maps and detailed explanations.
- There are some tools for simulating color-blind vision: toptal (webpage analysis) and coblis (local file analysis). There are also browser extensions for webpage analysis: Colorblinding (Chrome) NoCoffee (Chrome) NoCoffee (Firefox)
WCAG Success Criterion 1.4.3 <link>https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html</link>