Design/Archive/Wikimedia User Interface

 Problems we're solving & Goals User stories Share your story Collaborate with us

=Design Resources=  Sketch  WMFLabs  Icons 
 * SVG sprite format
 * Font format
 * Icons in SVG format

=Currently working on...=

High-priority 1 - Basic styles implemented with base CSS & accompanying HTML
 * Document "Basic styles implemented with base CSS & accompanying HTML" on MediaWiki on how to use
 * Double check to make sure that less file is working with other frameworks with users
 * Extracting Less from May's github repo & revise Less file

High-priority 2 - Enhance accessibility of OOjs UI & MediaWiki UI library / LSG / MediaWiki General to screen readers and color-deficient users
 * Footer does not have an assistive header
 * MediaWiki's assistive headers are broken in modern browsers
 * Empty Link in the content section below Wikipedia logo can trip web content reader
 * `#toctitle` shouldn't be set to `display: none`. Screen readers don't get it right.
 * Provide a color palette and design for buttons that are purely highlighted links, to distinguish them from actual UI buttons
 * Blueprint should include skip-to-nav and skip-to-content links
 * Consolidate documentation for recommended color palette
 * Gray for "inactive" elements in the toolbar is too light
 * Inactive notification badge colors not compliant with WCAG 2.0 accessibility guidelines
 * Wrap MediaWiki footer to HTML5 tag
 * OOjs UI Input validation should be annotated with more ARIA attributes
 * Improve color palette to comply with WCAG 2.0 min level AA and color-deficiency-friendly.

High-priority 3 - Style Guide - Guide on how/when to use components
 * Discussion group with community developers
 * Understand what non-technical contributors needs are in their work

Full to-do list

We manage our project, tasks and bugs on Phabricator. View our complete to-do list.

Log in to Phabricator with your MediaWiki login credentials to be involved in this project.

= Problems & Goals =

Problems


 * A specific icon (i.e.: star icon) can have many different meanings (i.e.: featured article, watch list, watch current page, portal of the week). This happens throughout Wikimedia projects even within the same culture and language. Conversely, one meaning can be represented by a few different icons.
 * One component type (i.e.: button, menu) with the same use case is implemented in many different ways
 * Deficiency in being screen-reader and keyboard-user accessible
 * Deficiency in being color blind-friendly and photophobia-friendly
 * Lack of mobile support and components are not finger-friendly (touchscreen-friendly)

Goals


 * Standardize Wikimedia's user interface components (i.e.: button, dropdown menu, radio button, list, etc.) so that they visually look and feel the same across any templates and pages within WikiProjects, Wikipedia article pages, every language Wikipedia, MediaWiki documentation pages, Meta-wiki, and so on.
 * Strengthen the mental model of our components (i.e.: button, menu, dropdown, text field) by reusing the same component type for the same use case (example: To “delete a comment," we should always use a red button. We should never use a green button to “delete a comment.” Conversely, we also shouldn’t use a red button to “create a new topic.”)
 * Make sure that Wikimedia project sites are largely accessible for the visually-impaired using screen-readers
 * Make sure that Wikimedia project sites are largely accessible for the color blind and photophobic
 * Make sure that Wikimedia project sites are largely user-friendly at all device sizes
 * Support for bi-directional - RTL (right-to-left) and LTR (left-to-right) language text

FAQ on the goal-setting process

Let us know if we're missing anything else under "Goals"

= Challenges & Execution =

Challenges


 * Wikimedia projects are built and improved by a large community of both technical and non-technical contributors. With that in mind, the solution must also be accessible for all kinds of contributors.
 * Our users' and contributors' use cases are varied across languages, cultures, projects and content types. With that in mind, our solutions should be a fundament for flexible use cases while preserving consistency.

Execution

To solve our current interface challenges, we have resorted to building a library of components. This library will conform to these guidelines to achieve all listed goals above: We want to hear about your thoughts around this execution method.
 * Web Accessibility Initiative – Accessible Rich Internet Applications (WAI-ARIA)
 * Web Content Accessibility Guidelines (WCAG 2.0)

=Team=


 * MGalloway (WMF) / violetto / IRC: violetto ([mailto:may@wikimedia.org Contact me] for design-related questions and if you'd like to speak about your user experience at any Wikimedia projects)
 * Volker E. (WMF) / Volker_E / IRC: Volker_E ([mailto:volker@wikimedia.org Contact me] for all organisational and technical questions)

=See also=
 * [ Create a new task] in this project (Tag project "UI-Standardization" under "Projects" field)
 * Work-in-progress library called OOjs UI
 * The Need for Web Design Standards by Jakob Nielsen
 * May Galloway on the need for consistency at Wikimania 2014 • Slide deck