Boost contrast of the default colour theme, to be closer to
the other theme's saturation then boost the unpressed state for action
buttons.
This brings the icons to 3:1 contrast while keeping colour in themes.
Co-authored-by: Nolan Lawson <nolan@nolanlawson.com>
Use lowest possible contrast gray that meets WCAG requirements for
very deemphasised text.
Makes the notification page more readable without compromising access.
Co-authored-by: Nolan Lawson <nolan@nolanlawson.com>
Co-authored-by: Nolan Lawson <nolan@nolanlawson.com>
Depending on the operating system and therefore the system font
the back icon being a unicode arrow means it'll render inconsistently,
sometimes I've seen it looking really odd.
Instead make use of the font awesome arrow so that'll it render consistently
no matter ths system font.
Increase the background contrast for the selected page.
Increase the prominance of the indictor bar so we dont need to rely on
the background to have a strong contrast difference.
Generally phrasing that talks about "the disabled" or "the visually impaired"
feels othering, whereas it is more common these days to have identity focused
framing.
Some other parts of the interface for example URLs in profiles
use the invisible class, move this to the top level global file
so it'll be applied everywhere.
By changing the shape it means no matter what the colour difference between
pressed and non-pressed it'll be possible to know the state.
Co-authored-by: Nolan Lawson <nolan@nolanlawson.com>
ComposeBox already specified autoFocus for the ComposeInput.
However, this didn't work because the dialog was disabled when the ComposeInput code tried to focus the textarea.
To fix this, tweak A11yDialog to look for the autofocus attribute when determining what to focus.
This is consistent with the behavior for native HTML dialogs.
Then, have ComposeInput set this attribute if it's in a dialog.
Fixes#1839.
Previously, if focus was on an element inside a toot instead of the toot itself (e.g. moving to a toot and pressing tab), keyboard commands acted as if no toot was active.
In particular, this meant that the arrow keys scrolled to the first visible toot.
Fixes#2228.