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
On storybook examples of page header with top nav, the built in storybook accessibility plug in is failing due to two elements having a banner role and all roles should be unique.
🪜 How to reproduce
Tell us the steps to reproduce the problem:
Go to page-header sticky-with-content-and-footer example
Click on accessibility plug in in the drawer
See the error
alternatively the error can be replicated on our https://design.sis.gov.uk/top-navigation-page-header-pattern/
If you do a full page scan using the 'axe Dev Tools' browser plugin, it appears as a moderate issue.
If you do an Accessibility Assessment using the IBM Equal Access Accessibility Checker it also appears.
📸 Screenshots or code
🧐 Expected behaviour
It should only have one banner.
Additional info
Weirdly page header doesn't have a banner role. This doesn't fail accessibility insights fast pass either so it's hard to tell if it's a weird quirk of storybook or not.
The text was updated successfully, but these errors were encountered:
Summary of the bug
On storybook examples of page header with top nav, the built in storybook accessibility plug in is failing due to two elements having a banner role and all roles should be unique.
🪜 How to reproduce
Tell us the steps to reproduce the problem:
alternatively the error can be replicated on our https://design.sis.gov.uk/top-navigation-page-header-pattern/
If you do a full page scan using the 'axe Dev Tools' browser plugin, it appears as a moderate issue.
If you do an Accessibility Assessment using the IBM Equal Access Accessibility Checker it also appears.
📸 Screenshots or code
🧐 Expected behaviour
It should only have one banner.
Additional info
Weirdly page header doesn't have a banner role. This doesn't fail accessibility insights fast pass either so it's hard to tell if it's a weird quirk of storybook or not.
The text was updated successfully, but these errors were encountered: