Translations:Page Previews/41/en

At the project level, administrators can determine how long a user should dwell on a link before a hover is triggered. If a project wants to be conservative, the lag can be longer. WMF will have a recommendation as to optimum dwell time that provides the best user experience while minimizing accidental hovers. Unfortunately, there is no good way to tell users about a new feature without showing it to them first. Central notice banners have been suggested, but running them for 2 weeks would not solve the needs of future users and we do not want to run them continuously. Notifying a user of a new feature is best done using a...hover-over. According to A/B tests we did not see a large decrease in session depth across all Wikipedias. Average session depth (average number of pages viewed per session) remained relatively equal between the Previews on and off groups. Page Previews only activate when the focus/hover state occurs over a link. They are usable for people who use keyboard navigation. For screenreades, Page Previews have proper WAI-ARIA semantics declaring them as tooltips. In short, screenreader software ignore Page Previews. Please go to the Page Previews discussion page.
 * Why can't users just turn on Page Previews if they want them?
 * Why can't users just turn on Page Previews if they want them?
 * What impact to Page Previews have on page views?
 * What impact to Page Previews have on page views?
 * What about accessibility?
 * If I have Page Previews feedback or if I have a suggestion for making them better, where should I go?
 * If I have Page Previews feedback or if I have a suggestion for making them better, where should I go?