Tag Info

New answers tagged

13

Marco Zehe, Mozilla accessibility QA engineer and evangelist, provided some advice in an article about implementing tabs in web apps with WAI-ARIA. He advocates cursor keys for moving focus between tabs in a set and then spacebar to activate the focused tab, which is consistent with the native desktop experience. Left and Right arrow keys should move ...


0

I'll stay away from the "general opinion" on this pattern and try to answer your question on if it is suitable. As pictured in the Yelp app, the items that "pop out" (Check In, Review, Photo) do not seem like sequential steps (if they are, it is not well represented.) It is also my understanding that they do not all need to be completed. Those are "Big" ...


0

Most modern default mobile browsers support tabs in such a way that would mirror the current workflow of your existing desktop users. I would take another look at developing a mobile site rather then an app. I understand the desire to keep users inside your app, but your users may have the expectation that clicking links will take them to the browser, ...


1

If a user takes the effort to open the in-page tab in a new tab/window, you can assume they do so because they want to read the contents later on, but are currently reading the info on the screen right now. My advice would be to open the new browser tab with the selecte in-page tab shown, while keeping the current page the way it is.


0

Accordions What Problem Does This Solve? When there are too many items to fit into a limited space or when the number of items, if displayed all at once, would overwhelm the user, then the question is how to give the user access to all of the items in digestible chunks and without requiring scrolling, which can remove the user from the context or page ...


0

The main difference between Tabs and Accordions are defined by their interaction and display characteristics, since they are both essentially containers that allow people to organize and access a large amount of content. Unlike trees and maps they do not have a deeper level of organization and hierarchy (unless you order them or group them within other ...


0

Be wary of solutions that require the user to hover over a UI element: these won't work with touch-based UIs. Some extra visual strategies to explore: If few elements are interactive on your UI, increase the contrast for both active and inactive UI elements (e.g., a bright-coloured background for active elements and a light grey one for inactive ones) ...


0

There are a few strategies you can try: You can simply remove any hover-over or on-click style changes to show that something is not interactive You can remove any stylistic embellishment (e.g. borders, shadows) to indicate a different state to other active UI elements You can bring up a prompt or tooltip to show why the component is inactive You can use a ...



Top 50 recent answers are included