Ma'ruf

Explain the reason for using React.portal

1

The reason for using React.portal is not well-explained.

fix: (accessibility) explicitly specify role mapping for pagination

1

List semantics are overwritten when used with list-style: none; CSS property on some versions of Safari on MacOS ( [More here](https://bugs.webkit.org/show_bug.cgi?id=170179) ). Solution is to explicitly provide role mapping.

fix: adjust button to have visual borders on forced colors mode

1

By default, when forced colors mode is enabled, button doesn't have visual borders, which may be hard for the users to know the areas of button. Before: After:

As a keyboard user i noticed 2 problems in the home page: 1) After focusing on theme toggle button, if user presses tab (to focus to next element) the focus...

The reason for using React.portal is not well-explained

Fixes #5354 Now focus works as expected. Focus doesn't disappear, and goes to menu items if the menu is open. Otherwise it goes to next focusable element.

### What is the URL where the issue is happening https://roadmap.sh/ ### What browsers are you seeing the problem on? Chrome ### Describe the Bug This bug violates WCAG criteria...

fix bug with tab navigation for mobile devices mode

2

As a keyboard user, i noticed one little bug, which made the usage a bit inconvenient. Specifically: Everything seems good, but when i pressed tab to navigate to next controllable...