The importance of good navigation

Navigation may be the most important element in web design. If users can not navigate the site, they leave the site or miss important content.

The home page should contain a menu or a list of categories, with all internal pages linked accordingly. Users should see a link back to the homepage from every part of the website.

Category names should be familiar to users and can be listed in alphabetical order or in order of importance.

Navigation – An Alternative to Carousal Tabs for Cell Phones?

I design a mobile application for business, so we use tabs for the desktop view, as you can see in the picture below. I want to design the same for mobile devices. So if we're using carousel tab navigation, we'll have to swipe to get to the last tab, and it may be less discoverable.

Enter image description here

Mobile views

  1. Carousel Tab Navigation

Enter image description here

  1. Tab with more dropdown

Enter image description here

So wanted to know if there are any better alternative to?

Accessibility – NVDA does not read text in navigation using the arrow keys

I am facing a problem with the NVDA screen reader, where the links or text in a navigation are not read.

Link – https://codepen.io/yogesharora28/pen/WNNPQKV

I use the arrow keys to navigate in NVDA, and when I switch from a submenu to the next menu, e.g. Go from "home" and read the items in its submenu. Go to the menu "About us" and do not read "About us". Instead, read the submenu items for About Us.
Any idea what could go wrong?

magento2 – Disables navigation to the item when clicking

If you click on the details of a product since Magento 2.3.3, the page will be moved there. I think this happens because of the offset or the Aria roles. However, I tried to remove it, tried different methods, and can not disable it.


       

Offset_Details

I use the postage theme, but I think it started with the Magento 2.3.3 update, as I also looked at postage theme files and did not find anything.
There are other places where this happens, such as: OnePageCheckout etc. etc.

OffsetAria_Osc

How can I disable it? / Is there a solution that prevents this? I tried e.preventDefault() . return false. href = javascript:; In addition, but nothing, the page always moves to the element that I click.

I think the script below is responsible for this, but when I delete it, the page moves on to the item I click.


Ease of Use – What is the best screen navigation method for invalid user input?

Consider an Angular app with lots of user input through screens A, B, and C. Screen C requires valid inputs from A and B; B only from A; and A is independent. For example, suppose the user enters invalid inputs on screen B.

Question: Which navigation should I support for B in this case?

I currently think that I will not allow navigation to C due to data validation issues. But what about the return to B? On the one hand, there are no validity issues, and the user may want to look up screen A to help screen B enter. On the other hand, this would complicate the status management of the app. An alternative is to disable such navigation, possibly with the option to restore the last valid inputs to B.
Since I lack experience in UX, I would be glad about answers that help me with this compromise.

Navigation bar – How do I change a text view of a fragment?

I am trying, but from object zero pointer

    public void addidoso(View view){
   Idoso idoso= new Idoso(SlideshowFragment.nomeV,SlideshowFragment.cpfV,SlideshowFragment.idadeV,SlideshowFragment.pesoV);
   if(cuidador.addIdoso(idoso)){
       Toast.makeText(this,"Idoso Cadastrado!, verifique a aba (Ver idosos)",Toast.LENGTH_LONG).show();
       switch (Cuidador.quant_idosos){
           case 1:
               GalleryFragment.idoso1.setText(String.valueOf(idoso.getNome()));
               break;
           case 2:
               GalleryFragment.idoso2.setText(String.valueOf(idoso.getNome()));
               break;
           case 3:
               GalleryFragment.idoso3.setText(String.valueOf(idoso.getNome()));
               break;
           case 4:
               GalleryFragment.idoso4.setText(String.valueOf(idoso.getNome()));
               break;
           case 5:
               GalleryFragment.idoso5.setText(String.valueOf(idoso.getNome()));
               break;
       }
   }else{
       Toast.makeText(this,"Você não pode Cadastrar mais idosos!",Toast.LENGTH_LONG).show();
   }

}

fragment:

public class SlideshowFragment extends Fragment {

// Add seniors
private slideshowViewModel slideshowViewModel;

public TextView name;
public TextView cpf;
public TextView age;
public TextView weight;
public static String vName;
public static String cpfV;
public static String ageV;
public static String weightV;

public View onCreateView(@NonNull LayoutInflater inflater,
                         ViewGroup container, Bundle savedInstanceState) {
    slideshowViewModel =
            ViewModelProviders.of(this).get(SlideshowViewModel.class);
    View root = inflater.inflate(R.layout.fragment_slideshow, container, false);
     nome=(TextView) root.findViewById(R.id.nome);
     cpf=(TextView) root.findViewById(R.id.cpf);
     idade= (TextView) root.findViewById(R.id.idade);
     peso= (TextView) root.findViewById(R.id.peso);
     nomeV= nome.getText().toString();
     cpfV=cpf.getText().toString();
     idadeV=idade.getText().toString();
     pesoV=peso.getText().toString();
    final TextView textView = root.findViewById(R.id.text_slideshow);

    slideshowViewModel.getText().observe(this, new Observer() {
        @Override
        public void onChanged(@Nullable String s) {
            textView.setText(s);
        }
    });
    return root;
}

Sharepoint Enterprise – CSS in the style of UL on the page also formats Top Navigation

Yup. This is how CSS works. The rules you define are applied to all elements that match the selection. So if you use something

ul {background color: red;}

Will suit everyone ul Element tag on the page and change the background to red. That's why the Navi is currently being formatted – because it's a list.

Luckily, you can create more specific selectors. If you need to refresh your selectors, and like the work I recommend CSS Diner, it's a fun way to learn your selectors.

Usually, we create a selector that basically says, "Change only items that are in the main content area of ​​the page." You do not know exactly which SP version you are using or which master page, but we have SP 2013 and use Seattle.

#contentBox ul{background-color:red;}

This says, "Apply this style to ul elements that are a descendant of the element that has the id of content box, "

Another approach that you can use is to create such a rule

ul.clj-style{background-color:red;}

This says, "Apply this style only to ul, which has a class of Clj style, This would require that you change the markup of a list that you want to format.