Lectura / Web / Mejoras de escritorio / Preguntas frecuentes

From mediawiki.org
This page is a translated version of the page Reading/Web/Desktop Improvements/Frequently asked questions and the translation is 28% complete.


¿Cómo activar o desactivar Vector 2022?

¿Cómo puedo desactivarlo en una o en todas las wikis de Wikimedia?

En primer lugar, comprueba si te has conectado a tu cuenta. Los usuarios desconectados no pueden cambiar de skin.

Una wiki Todas las wikis
Disable
  1. Accede a las preferencias globales
  2. Abre la pestaña Apariencia
  3. Comprueba la caja de la izquierda
  4. Comprueba "Versión heredada de Vector (2010)"
Enable
  1. Accede a las preferencias de usuario
  2. Abrir la pestaña Apariencia
  3. Comprobar "Vector (2022)
  1. Ir a las preferencias global
  2. Abrir la pestaña Apariencia
  3. Seleccionar la casilla de la izquierda
  4. Comprobar "Vector (2022)"

Ver también:

¿Por qué el enlace de desactivación no está disponible para las personas no lo logadas?

Esto se debe a la capacidad limitada de nuestros servidores. Los usuarios desconectadas pueden utilizar extensiones del navegador que les permitan personalizar su interfaz, o pueden crear una cuenta.

Ver también:

¿Cómo puede Vector 2022 convertirse en la opción predeterminada en mi wiki?

Contáctanos. Presentaremos el proyecto a tu comunidad y comenzaremos una conversación.

¿Cómo puedo habilitar Vector 2022 para mí?

Si quieres ver nuestras mejoras,

  1. Asegúrate de haber descargado $1
  2. Añade las siguientes líneas en tu $1:
$wgDefaultSkin = ‘vector-2022;

¡Nos alegra saber que aprecia nuestras mejoras!

¿Cómo personalizar Vector 2022?

¿Por qué no se ofrecen alternativas para elegir entre diferentes versiones de las funcionalidades?

Eso sería demasiado complicado de mantener y desarrollar.

Cada preferencia es algo así como un cruce de caminos en el que los usuarios pueden elegir entre distintas opciones. Muchas opciones indican muchas combinaciones. Las preferencias nos harían responsables de todas las combinaciones. Tendríamos que mantenerlas y, además, en el caso de construir nuevas funcionalidades, comprobar si éstas son compatibles con cada una de las combinaciones. Por ahora, no podemos asumir eso.

En su lugar, damos a las comunidades la opción de crear gadgets, scripts de usuario y configuraciones individuales. Como siempre, proporcionamos el espacio para la creación ascendente, y ayudamos a los usuarios técnicos a mantener su código.

Ver también:

¿Por qué no hay preferencias para los usuarios anónimos?

Las preferencias anónimas harían que las páginas se cargaran muy lentamente.

La mayor parte del tráfico proviene de personas desconectadas. Para ello, disponemos de algunos "servidores de caché" que sólo guardan y envían "instantáneas" de las páginas web. Estas "instantáneas" tienen una antigüedad de hasta 7 días, sustituyen a la generación de páginas web y son las mismas para todos los usuarios desconectados. Esto nos permite una carga rápida de las páginas.

Las preferencias requieren la generación de diferentes versiones de las páginas web. Ofrecer esta posibilidad a las personas no connectadas sobrecargaría nuestros servidores. No queremos hacer eso porque tenemos que reducir la fragmentación de la caché.

La única forma de proporcionar preferencias a los usuarios desconectados ahora que la configuración se cargue siempre después de la página. Esto requiere [1$ más de tiempo de carga] y tiene un aspecto extraño. Por ejemplo, si una persona que haya cerrado la sesión viera el modo oscuro en acción, inmediatamente después de cargar cada página, vería primero la interfaz luminosa durante un breve momento, y luego la interfaz se volvería oscura.

Para contextualizar, la única razón por la que tenemos preferencias para los usuarios registrados es que no les servimos esas "instantáneas". Y esto se debe a que el tráfico procedente de los usuarios registrados es bajo.

Ver también:

¿Qué hacemos para las personas editoras que necesitan herramientas y funciones específicas?

  • Nos ponemos en contacto con voluntarios con conocimientos técnicos para garantizar la compatibilidad con la versión anterior. Les pedimos que comprueben el código que han escrito, y les ofrecemos ayuda si el código necesita cambios.
  • Hacemos posible la configuración y personalización de nuestros cambios. Colaboramos con voluntarios con conocimientos técnicos que quieran crear nuevos gadgets y scripts de usuario.
  • No sustituimos el trabajo de las personas voluntarias con conocimientos técnicos. En principio, no realizamos ediciones de plantillas ni creamos nuevos gadgets, pero podemos asesorar cuando sea necesario.

¿Arregláis los accesorios que no funcionan con vuestros cambios?

Depende.

Ayudamos a las personas voluntarias a reparar los accesorios y user scripts. En ocasiones, los reparemos nosotros mismos. Pero en general, trabajamos en el propio MediaWiki. Los accesorios y los user scripts son escritos y mantenidos por personas voluntarias. Por su naturaleza, éstas son siempre menos estables y predecibles.

¡Si no estás seguro de cómo solucionar un problema con un script o gadget - contacta con nosotros! Haremos todo lo posible por aconsejarle sobre posibles soluciones.

Ver también:

  • Tecnología en Meta-Wiki - aquí también puedes pedir soporte técnico
  • 1 - una propuesta de política sobre las funciones y responsabilidades relacionadas con los gadgets y los scripts de los usuarios

¿Qué clases de CSS deben utilizarse para personalizar Vector 2022?

  • 1$ para ambas skins
  • skin-vector-legacy para Versión heredada de Vector (2010)
  • skin-vector-2022 para Vector 2022

¿Cómo restaurar el ancho completo?

Una wiki Todas las wikis
  1. Ir a preferencias de usuario
  2. Abrir la pestaña Apariencia
  3. Marca "Habilitar el modo de ancho limitado"
  1. Ir a las preferencias globales
  2. Abrir la pestaña Apariencia
  3. Selecciona la casilla de la izquierda
  4. Selecciona "Habilitar el modo de ancho limitado"

See also:

How to disable the sticky elements?

Add the following CSS code to your global.css:

  • Header – add
    .vector-sticky-header {display:none;}
    
  • ToC – add
    .sidebar-toc {position: static;}
    

How to restore the old table of contents?

Use the following JavaScript code:

$('.mw-table-of-contents-container').removeClass('mw-sticky-header-element' ).removeClass('mw-table-of-contents-container').appendTo(document.getElementsByTagName('mw:tocplace')[0])

How to make the button with language links appear at the top of the main page?

  1. Ask your community to agree to set up the main page heading. (See our explanation why this is a good idea.)
    1. The heading will be displayed in Vector 2010, Minerva, Timeless, and Vector 2022. It will not be visible in Monobook.
    2. The heading can be configured by edits to MediaWiki:Mainpage-title-loggedin for logged in users and MediaWiki:Mainpage-title for logged out users. For mobile logged in users, MediaWiki:wikimedia-mobile-mainpage-title-loggedin is used. See the details about the main page heading settings.
    3. Test what the main page looks like and work with the button at the top by adding the ?vectorlanguageinmainpageheader=1 parameter to the URL. See the example on the Icelandic-language Wikipedia. Note that the Icelandic-language Wikipedia hasn't the heading set up, so only the button appears.
  2. Contact us and ask us to move the button to the top.
    1. We will change the settings for your wiki.
    2. When we do this, the button will be visible at the top of the page in Vector 2022. In other skins, the list with language links will be displayed in the standard place which varies by skin.

How to restore the previous user menu?

It's not possible to do that currently.

How to change the logo to a temporary one?

The logo in Vector 2022 is made of 3 elements, each can be changed independently with CSS.

  • To change the icon image (e.g. globe on Wikipedia):
    .mw-logo-icon { content: url("INSERT NEW IMAGE URL HERE") };
    
  • To change the wordmark (e.g. the word "Wikipedia"):
    .mw-logo-wordmark { content: url("INSERT NEW IMAGE URL HERE") };
    
  • To change the tagline (e.g. the words "The free encyclopedia"):
    .mw-logo-tagline { content: url("INSERT NEW IMAGE URL HERE") };
    

Contact

How can I contact your team?

Choose one of the following options:

How can I follow your activities?

Do you host or attend online meetings?

Yes!

We organize open online meetings for the communities (office hours). At these meetings, Olga (our product manager) makes presentations about the recent developments. Next, community members can ask any questions about the project.

We are also open to invitation to any community event online. These may be local, country-wide, or international meetings.


WP20Symbols community1.svg


What are Vector 2022 and the Desktop Improvements?

Is this a redesign?

No.

A redesign would be a single major change which affects how the site works.

In the case of this project we have made a series of individual changes. Each feature was a separate small project.

At the end, these features were joined together by a cohesive visual design.

What is the timeline of this project?

We have been working on Vector 2022 (originally known as modern Vector) since 2019.

Between early 2020 and mid-2022, we were building and releasing different features on "early adopter" wikis. (You can read more about that in the answer to the question below, points 2–4.) We have finished that part. Vector 2022 isn't "beta" anymore.

Currently, we inform about our intention to introduce Vector 2022 on more wikis.

By the end of March 2023, we hope that Vector 2022 would be the default skin across almost all Wikimedia wikis.

Why do you use the word Improvements?

The term early adopter is used in the English Wikipedia article Technology adoption life cycle.

Because we have data indicating that the changes are for the better:

  1. We identified problems through research with both readers and editors. During this phase, in 2019, we studied the way people used the sites and identified the largest usability issues. We also identified issues to exploring the site further, becoming more engaged with reading or editing. We did this by interviewing readers and editors across multiple countries, locations, and languages. See: Research and design: Phase 1, Research and design: Phase 2.
  2. We built and tested prototypes. We built out the ideas of each feature and began showing them to the users. Each feature was tested with readers and editors through interviews and wider rounds of prototype testing. For testing with editors, we used central notice banners. We displayed them across multiple language and Wikimedia projects so that we can get a wide and diverse audience. Each prototype was tested by approximately 200 editors on average. (Example)
  3. We refined and built our features. We took the feedback from the prototype testing and refined or changed the prototypes accordingly. In some cases, we asked for additional feedback to ensure we're making the right decisions.
  4. We contacted various wikis asking to join the early adopters ("pilot wikis"). This was the "beta" phase. On these wikis, we performed quantitative tests for whether each feature worked as expected.
    1. We performed A/B testing on logged-in users. Unfortunately, we are not able to perform these on logged-out users. This is why we make before and after comparisons.
    2. When we had the test results, we compared the results with the criteria of success we had previously defined. When we got negative results from our test, we changed the feature and test again.
    3. Since this phase, we have also monitored usage across all wikis, where many account holders have already been using Vector 2022.

See also:

On which wikis have you tested these changes?

The pilot wikis where we have been testing Vector 2022 have been:

Wikipedias de escritura latina: * Wikis de escritura no latina: * Proyectos hermanos:
Wikisource en árabe Yes Yes
Wikipedia en árabe marroquí Yes
Wikipedia en bengalí Yes
Wikipedia en catalán Yes
Wikiviajes en alemán Yes
Wikipedia en euskera Yes
Wikipedia en persa Yes
Wikipedia en francés Yes
Wikiquote en francés Yes
Wikcionario en francés Yes
Wikipedia en indonesio Yes
Wikipedia en hebreo Yes
Wikipedia en coreano Yes
Wikinoticias en polaco Yes
Wikisource en polaco Yes
Wikinoticias en portugués Yes
Wikipedia en portugués Yes
Wikiversidad en portugués Yes
Wikipedia en serbio Yes Yes
Wikipedia en tailandés Yes
Wikipedia en turco Yes
Wikipedia en veneciano Yes
Wikilibros en vietnamita Yes
Wikipedia en vietnamita Yes

Adicionalmente:

Why do you use this naming: Vector 2022 and legacy Vector?

The new skin is a continuation of many of the ideas in the original Vector skin.

It is being built using the code the Vector skin uses. We wanted to maintain functional and visual continuity.

Everything built and meant for legacy Vector should be working with our changes, or can be configured to do so fairly easily.

The version built in 2010 and developed until 2019 has been frozen.

In other words, we will keep and maintain it, but will not be building new features for it.

We use the name Vector 2022 for purely technical reasons.

This name marks when the new Vector was available to third-party wikis as a new skin.

(Third parties mean those who install MediaWiki).

On each wiki, the skin name can be overriden by changing MediaWiki:Skinname-vector-2022.

However, this may cause confusion since it won't change the associated skin key that is used for site and user styles.

See also:

Will you remove legacy Vector?

No.

Legacy Vector will continue to be available as an option in Preferences, similar to other skins that have been default in the past, such as Monobook.


WP20Symbols chemistry.svg


Target audience

Are these changes made for readers, and not for editors?

Not exactly.

Our team (Web) works on the reading (viewing) experience on desktop and mobile browsers.

Those who both view and edit, and those who view but do not edit, are one large group of the interface users.

We work for all of them, bearing in mind that new and advanced editors have specific needs.

The goal of this project is to improve the reading experience on desktop without making editing more difficult.

That said, our movement strategy recommendations implore us to improve our user experience in an inclusive manner.

In this spirit, the project has a specific goal of ensuring the free knowledge grows equitably in the future. When building, we made sure to collect the voices of readers from different demographics and geographies.

We also want to make their opinions a focus when defining what we were to work on, and evaluating whether a given idea was able to satisfy their needs.

See also:

What tools are the Foundation building for editors?

At the Foundation, there are other teams working on projects dedicated specifically to editors.

Among them, there are:

Do your changes have a negative effect on the editing statistics?

No.

We collect statistics of the editing activity on all wikis.

Compared to wikis with Vector legacy (2010) as the default, on wikis with Vector 2022 as the default, there are no negative differences.

Do your changes make it more difficult to explore the community side of the wikis?

No.

Readers and new editors are intimidated by large numbers of links, options, and ways of exploring the editing (in other words, the community) side of the Wikimedia projects.

This is a finding of our research.

We want more users to join the communities.

We do this by limiting the number of the unhidden links, and bringing additional focus on the most relevant ones.

All this is done in collaboration with the Growth and Editing teams.

See also:

Are you focused on Wikipedia articles?

Yes.

Wikipedia articles, as a whole, have the most part of the viewership and readership compared to other namespaces on Wikipedia or any other projects.

We also make adjustments to pages from other namespaces and special pages.

Pages which we have made special adjustments and configurations for include: main pages, pages specific to some sister projects, special pages, the 2010 wikitext editor, the 2017 wikitext editor, and the Visual Editor.

We have also been working with the Editing team to ensure that the work they are doing for talk pages aligns with our work, and that special configurations for talk pages are put in place.

Have you been mindful of sister projects?

Yes!

We aim to change the basic elements of the interface.

Most features work on the sister projects just as well as they improve Wikipedia. We have made sure to test and build for different sister projects from the beginning of the project.

We still make adjustments to the default features where necessary.

Non-Wikipedia projects, such as French Wiktionary, were also a part of our partner communities since 2020.

We ensured we have had direct communication and feedback from them.

Regarding the adjustments, for example, on Wikisource, the limited width does not apply to the Page namespace provided by the Proofread Page extension.

Are you focused on English Wikipedia?

No.

We take into account the needs of various communities and test our changes across 30+ languages. We are also inspired by the interface and gadgets built on various wikis, for example Korean and Vietnamese Wikipedias.

What do you do to ensure that the change would work on my wiki?

What do you do to ensure that the change is not half-finished?

We make tweaks both before and after we introduce the changes on wikis to make sure they are up to the needs for individual communities. If you think your community would benefit from more adjustments and gadgets, see:

After making these changes on all wikis, we will work on projects related to Desktop Improvements.

Accessibility

Have your changes been tested on users with disabilities?

Yes. We are working with the American Foundation for the Blind. We are asking various questions related to the accessibility of Vector 2022. See more on Phabricator.

Will the wikis be less accessible for users with slow Internet connection?

No.

We want to keep the new skin similarly code-heavy to legacy Vector.

See also:

Mobile, large screens, and responsiveness

Are the changes inspired by mobile design?

No.

These changes are created specifically for desktop interfaces. All research and testing done for this project has been focused on desktop users only. We have, however, considered the experiences of people who use desktop in narrower screens (for example, if you have two tabs open side by side).

At this time, we do not have plans to merge the desktop and mobile experiences.

Will the new interface be responsive?

We've been working towards that goal, but it's not an official goal of the project.

If you want to make the interface responsive now and you're using Wikimedia wikis, add

if

( mw.config.get("skin") === "vector")

{

document.head.innerHTML += '<meta name="viewport" content="width=device-width, initial-scale=0.77, maximum-scale=1.0, user-scalable=0">';

}

to your global.js.

If your community would like this to be the default, please start a conversation on your wiki, and contact us when consensus is reached. We can then make the change.

Will you build a dedicated setting for high resolutions?

We don't have plans to build a specific setting at this time. We want the experience to be optimized for the majority of users, while still providing the tools necessary at all resolutions. We believe the current version of the new skin does this successfully. That said, we encourage personal customization!

See also:

WP20Symbols MediaWiki.svg

Why is the width of the content limited?

Why have you replaced the area used for content by an empty space?

Reading efficiently is crucial to most people using our projects. Our goal here is to improve the readability of the content. There are several factors that affect it – i.e. font size, contrast, font, line length, and empty space.

Shorter lines
  1. When reading short lines, readers don't move their eyes too much, use the eye's muscles less intensively, thus avoiding eye strain.
  2. Narrow paragraphs allow readers to memorize new information better.
  3. On websites, there should be between 35 and 100 characters per line. Numbers closer to the smaller end are preferred.
  4. The overwhelming number of major websites have similar limitations on content width. For example: academic journals like Nature, news websites like The New York Times, government and intergovernmental websites like the United Nations, academic documents like LaTeX, and word processors like Google Docs and Etherpad.
Empty (white) space
  1. White space is used for the eyes' resting spots. It helps readers focus on content and increases content comprehension by 20%.[1]
  2. People are able to focus more easily without the distraction of sidebars or other elements.
  3. We are using some of this space for other functionality. We have made the sidebar sticky, and have placed the table of contents next to the content. Also, limiting the content area gives us new options for the more distant future. Community members have suggested to put infoboxes, images, or references there. As a separate project, we will consider ways of using this space.

See also:

Why can’t we leave it for readers to narrow their browser windows down?

Most users don't resize their browser windows or use browser plugins to improve the design of the websites they view. Wikis should be good-looking immediately, in their basic form.

Some tables and templates don’t fit within the limited width

We should make sure that all of our content is as responsive as possible to accommodate all visitors. A large percentage of our users, who don’t have large screens and are accessing Wikipedia from their laptops, already had issues with tables and templates even before the change.

Why don’t you just make it a setting?

We want it to be default. We are building a common experience that is shared between editors and readers. This could be helpful to editors when making decisions about page layouts*. Currently an editor might be editing a page at a width of 1500px, while a reader reads it at a width of 1200px. By implementing a limited width, we don’t remove this discrepancy (because there would still be variation below the max-width, for people with narrower screens), however we would be greatly limiting the range of variation.

[{note|1=Note: 1024px is mentioned as a minimum size to consider in the English Wikipedia Manual of Style, though that’s not quite the same thing.}}

Why did you change the list of language links?

Why couldn't the list of language links stay in the sidebar?

Because from the readers' perspective, the sidebar is not a place for useful links. Most readers focus on the content area. Links in the sidebar are practically hidden from their sight.

Also, we need to promote the variety of language versions of Wikimedia projects.

For more than 15 years, the list has been displayed in the sidebar. The most active users have developed muscle memory to look for that list in that place. This is why in the sidebar, we have placed a box with information about the language button being displayed in a new place.

Will the Wikidata links be closer to the list of language links?

Yes.

"Agregar enlaces interlingüísticos", "Editar enlaces interlingüísticos", and "Elemento de Wikidata" will eventually be part of the menu activated by the language switching button ("language menu"). This is a task for the Language engineering team.

How to fix the coordinates displaying incorrectly near the languages button?

Antu mail-mark-notjunk.svg The recommended option Antu mail-mark-junk.svg A different option (not recommended)
  • If on your wiki, the coordinates are placed by a Lua module (for example, on French Wikipedia, there's Module:Coordinates), use the following code:
    titleText = frame:extensionTag( 'indicator', tostring(htmlTitle), { name = 'coordinates' }    )
    
  • If on your wiki, the coordinates are placed by a template, follow the instructions on Adding page status indicators.

Use the absolute positioning in the MediaWiki:Common.css, for example:

.skin-vector.skin-vector-legacy #coordinates { top: 0px; }

.skin-vector #coordinates { top: -20px; }

Consider pages which use page status indicators, pages which have banners or site notices, and the look of the pages at lower resolutions.

Why the button with language links doesn't appear at the top of the main page?

We have discovered that readers focus on the content page and ignore the sidebar.

They will be more likely to switch between languages if the button with the language links appears at the top of the page, next to the heading.

On many wikis, headings on main pages are hidden.

This is why the button with language links isn't displayed next to it. Instead, it's at the bottom of the main pages.

It is possible to make it appear at the top, though.

See also:

Why did you change the table of contents?

Why doesn't the table of contents work well on my mobile device or when I resize the browser?

Users on mobile and resized browsers account for a small fraction of page traffic. Because of this, we chose to build the feature for the majority of our users first. For narrow screens we plan to make the table of contents available as a sticky interface element that's accessible from anywhere in the page.

Note what is displayed to mobile devices differs from what you see when you resize your browser. On mobile devices, the site is currently presented as a zoomed out version of the desktop site.

Why doesn't it appear when I complete an edit?

The feature is still in development (T307251). This will be fixed before we make Vector 2022 the default on more wikis.

Is it possible to change the label indicating the top of the page? ("Inicio")

Yes.

This label should be distinct from the content headings. To do that, wikis written in different scripts (for example, Latin and Japanese) and different Wikimedia projects (Wikipedia and Wiktionary) may need to use different words and/or punctuation marks in this label. It is possible for each community to set up a label that would work just for them. This may be done by editing the page MediaWiki:Vector-toc-beginning.

How can I get both the old and the new table of contents?

This isn't possible.

We intentionally do not add the old table of contents in addition to the new sidebar location. It's a trade off. We have taken it to reduce the work involved maintaining the code and keeping the site work as good as possible. The old table of contents displayed in addition to the new one would have important technical disadvantages. It would increase the overall size of HTML, increase the storage requirement for our parser cache, and require additional CSS to render.

See also:

How do magic words work with this feature?

The __TOC__ and __FORCETOC__ magic words will not work as the table of contents is always in the sidebar and this cannot be changed.

However, magic words relating to the presence of the table of contents, such as __NOTOC__, will continue to work. So will templates which then create an alternate ToC. For example, an article can disable the default ToC and apply its own if necessary.

All magic words will continue to work for other skins which render the ToC within the article.

I can't see the table of contents when the sidebar is open

This is a known problem.

This issue should only impact logged in users who have opened the sidebar. In the long term, we plan to reduce the size of this menu, and make the sidebar overlay content. Details and a prototype of how that will look can be found in T302073. This change is planned in the latter part of the year (October-December 2022). Further information can be found on the page about Page tools.

¿Cuál es el alcance del proyecto?

¿Se verán afectados los temas Monobook o Timeless?

No.

These changes are applied to Vector only. Vector has been the default interface on Wikimedia wikis since 2010. Any other skins such as Monobook, Timeless, Minerva or Modern are not be changed at all.

While working on Desktop Improvements, we did clean up the old skins' code, though. We made it easier to roll out new changes to old skins, removed never used options, and removed 75% of the PHP code of these skins. All this had no effect on the side users interact with.

See also:

¿Mejorarás los gráficos, mapas, a- / f- / o- / tmboxes, infoboxes, navboxes u otras plantillas?

No.

We do not change anything within the light gray article content area (except for the table of contents):

Annotated Wikipedia Vector interface (logged-out).png


Are you building the dark mode?

No, not this time.

The Desktop Improvements project provides the architectural changes needed to build dark mode. Building it would be a separate project, though. This is because that project would require significant work with the communities. Now, many templates are not compatible with dark mode. We have learned that while working on the mobile apps.

Initially, our dark mode would be based on the user's operating system preferences. We would not plan to add an in-browser toggle. The reason is we currently do not have a system in place for anonymous user preferences. This could be added at a later date, though.


¿Cuáles son las métricas de éxito de la función?

Aumentar la utilidad entre nuestras audiencias existentes, representada por:

  • Interacciones
    • Incrementar las búsquedas por sesión en un 5% durante el transcurso del proyecto.
    • Aumentar el cambio de idioma por proyecto en un 5% durante el transcurso del proyecto.
  • Afinidad
    • Aumento de sentimientos positivos y acogedores hacia el sitio (a través de encuestas y pruebas de usuarios)
    • Aumento de los sentimientos de confianza y credibilidad (medidos a través de encuestas y pruebas de usuarios)

A medida que definamos los cambios que queremos hacer con más especificidad, ampliaremos e iteraremos en esta lista.

Referencias

  1. UI Design Newsletter – December, 2005, Human Factors International