as i’ve been out of the game here for quite a while, just checking @dflinn if it would be ok for me to run through some basic #a11y check over the preview at this point, and if so where’s best to look/file issues/PRs? already have a few low-hanging fruit/small tweaks (some unlabelled controls, for instance)
3 Likes
Hi @patrickhlauke, yes it is absolutely ok for you to run through some #a11y checks. We’ve have had some accessibility testing during the project, but I expect there are items we missed.
Feel free to log issues/PRs in Github as normal, you can tag my GitHub username and I will categorize the issues internally.
If you decide to open a PR, note that much of this work is behind the extension-refresh features flag, so you will need to enable it to contribute to the update. Docs here: Feature Flags | Bitwarden Contributing Documentation. The design system component changes are also currently on a separate branch, but will likely be merged to main sometime in the next few days.
As always, thank you for your efforts to support accessibility at Bitwarden.
I don’t know if this also part of the new design changes or for other reasons, but that post from @grb right now: Has Bitwarden lost all in-house expertise on entropy/password strength? reminded me of two other things for the generator:
- Though it may be problematic, if people “manipulate” too much with the password/passphrase settings, it is at least inconsistent with the “numbers” and “special characters” settings in the password section, that with passphrases, you can’t choose the number of numbers:
It seems, it is always just one number that get’s added by that option. (though it says “Ziffern” which implies the plural - but that may be a result of the translation into German?!).
I would like to choose more than one number. (and yeah, I know, that “complexity” is not recommended with passphrases, but more flexibility - and consistency with the password section, would be nice)
But - if you really want it to be only one number in any given case - than at least remove the plural. 
- Similar thing with the username section - but here it is even more plausible, being able to choose more than one number (until recently, the default was four numbers, I guess - what happened to that?), because a practical problem can be that such usernames with only one number may already be used by another person:
Here for comparison the password section again, where the “numbers” can be chosen:
With the added benefit that the truncated label “Zi…” can be interpreteted as either plural or singular! 
1 Like
… I don’t know if this thread here is still “active” - and maybe I should make a feature request instead (didn’t find one at first glance):
Today I needed the function to make a duplicate of a “Send”, because I needed the nearly identical one again. Was that ever possible, to make a duplicate of a Send? I thought I could remember doing that before… 
Anyway, neither the beta extension nor the current stable extension has a function for that. (PS: I guess the other clients face the same situation then…)
Besides, I think it is sometimes useful to be able to make a duplicate (example: some Sends to family members often have identical content…) and a bit inconsistent, to be honest, to be able to make duplicates of vault items but not of Sends. 
Please, if possible, give me some feedback if this can be considered - or if I should search for a corresponding feature request more intense or create one myself… @dflinn
PS: Just a comment on the passwords for “Sends”: wouldn’t it be useful to also be able to choose a password for a Send from an existing vault item? And the other way round: if you create a new password in/for a Send, it might be useful to be able to store that as either a login vault item or a secure not.
This was never possible, so it would be a feature request. There is an existing feature request on cloning Sends here. Another possibly relevant feature request is the request for Send templates to retain default settings.
For further feedback on the browser extension UI redesign, I would suggest using the more recent thread, linked below (although I agree that it is unclear whether @dflinn and/or @Kevin_Harris are still monitoring either of the two feedback threads):
1 Like
So I’m officially hallucinating. 
Thanks for the search I should have done myself - I will have a look at those threads.
When we’ll see update for this beta extension with fixes?
A post was merged into an existing topic: Usability issues (UX) in redesigned UI (2024.12.0)
The beta version is now in production (version 2024.12.0), so I am closing this thread. Any new feedback should be posted in the community forum feedback thread linked below (alternatively, create specific feature requests or post formal bug reports in the appropriate locations).