* Style provider set up toast
* Correct translation strings
* Do not show provider organization management for non admins
* Product feedback for provider org description
* Correct message grammar
- `visibility:hidden` also hides text from assistive technologies, leading to the settings link lacking an accessible name when not hovered (focused with keyboard only, for instance)
- turn the styles around and hide the non-hovered link's span with "visually hidden" styles https://www.a11yproject.com/posts/2013-01-11-how-to-hide-content/
- also include `:focus` to make the text visible when hovered (for sighted keyboard users)
- more semantically accurate, will expose these as buttons to assistive technologies
- note: while having block-level elements like `<div>` inside a `<button>` is an html validation error, it does not affect functionality as long as there's no more structure inside it
* Add captcha to login page
* pull out shared method
* Update parse parameter logic
* Load captcha
* responsive iframe height
* correct i18n
* site key provided by server
* Fix locale parsing
* Add optional success callbackUri
* Make captcha connector responsive
* Handle parameter versions in webauthn
* Move variables to top of script
* Add captcha to registration
* Move captcha above `<hr>` div to be part of input form
* Add styled mobile captcha connector
* Linter Fixes
* Remove duplicate import
* Use listener to load captcha
* PR review
* Add captcha to login component
* Add catpcha to login page
* Update content width if captcha is visible
* extend submit to handle widening if captcha is required
* Improve login styling
* Add Captcha to registration page
* Remove padding from captcha div
The padding was messing up image selection of captcha items
* Update jslib
* PR review
* update jslib
* Parse captcha required from error messages
CaptchaProtectedAttribute produces an error with captcha information.
We want to parse that data out to make it easily accessible to components
* Don't show error on catpcha
The component should hande this situation.
* Add captchaResponse to captcha protected api endpoints
* Extract captcha logic to abstract base class
* Add captcha to register
* linter fixes
* Make sure to log Captcha required responses
* Match file naming convention
* Separate import into logical groups by folder
* PR review
