Open ling1726 opened 1 year ago
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
This issue is ongoing, we have investigated aria-owns for providing 'true' order, however it is not a spec fully supported by the accessibility tools - we are investigating the possibility of an aria-reverse flag that would enable reverse order of components in the accessibility tree to align A11y with Flex CSS
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Was hoping to drive this via enabling support in A11Y/Accessibility tools so that CSS matched accessibility - as currently flex-reverse is fully inaccessible, I plan now to reverse this in code instead, so that DOM matches layout.
Using flex-direction to change orientation of items is an a11y antipattern since screen readers and keyboard navigation libraries will always follow DOM order. The change was introduced in https://github.com/microsoft/fluentui/pull/26985.
The usage of flex-direction should be removed because of a11y trap that users can fall into