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
As a user, I want to try both the light mode and dark mode of this site to determine which is more usable for me, then use that one.
This came up in conversation with a Fable tester, who said:
I think [dark mode] should be an opt-in. Having it at the top. It gives an option for the user, [...] because sometimes with their current assistive technology, they need to use dark mode with a specific website, but with other websites they don't have to. So having the option to opt-in I think might be the best solution.
Acceptance criteria
I can toggle dark mode on or off without needing to change my browser or OS settings
I have checked the toggle feature using one of the following browser extensions and confirmed that it does not add any level A or level AA issues:
… <a> tag
Prior to this commit, if you don't supply an href value for
a child menu item, Lux will render an <a> tag without an
href. This is not focusable, so keyboard users will not be
able to activate that menu item.
This helps with pulibrary/allsearch_frontend#443,
since it allows us to create menu items that are keyboard
focusable that are not links (in this case, they will be
buttons that switch between dark mode and light mode).
High priority
User story
As a user, I want to try both the light mode and dark mode of this site to determine which is more usable for me, then use that one.
This came up in conversation with a Fable tester, who said:
Acceptance criteria
Implementation notes
The text was updated successfully, but these errors were encountered: