You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been gradually improving the keyboard accessibility of Outline but one place stands out as being a major problem is the popover menus, where a lot of functionality is still kept.
I'd like to start moving to the Reakit framework for controls where possible to ensure we're following best practices and aria standards here. This should be relatively straight forward as the DropdownMenu code is already centralized, and will likely just mean removing a lot of custom logic for menu positioning and state management.
The text was updated successfully, but these errors were encountered:
- Makes menus fully accessible and keyboard driven
- Currently adds 2.8% to initial bundle size due to the inclusion of Reakit and its dependency, popperjs.
- Converts all menus to functional components
- Remove old custom menu system
- Various layout and flow improvements around the menus
closes#1766
We've been gradually improving the keyboard accessibility of Outline but one place stands out as being a major problem is the popover menus, where a lot of functionality is still kept.
I'd like to start moving to the Reakit framework for controls where possible to ensure we're following best practices and aria standards here. This should be relatively straight forward as the
DropdownMenu
code is already centralized, and will likely just mean removing a lot of custom logic for menu positioning and state management.The text was updated successfully, but these errors were encountered: