-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: Accessibility
-
None
-
1
The default font fails to provide a visually distinguishable difference between a bullet and a hyphen.
Command Prompt Font: bullet 9 pixels wide, hyphen 49 pixels wide. That is, the hyphen is more than 5.44 times as wide as a bullet. No one would ever have trouble distinguishing the two characters. The font Atlassian is using has a 10-pixel-wide bullet and a 12-pixel-wide hyphen. That is to say, the hyphen is only 1.2 times as wide as a bullet.
The problem I'm reporting is that, with the current default font, the hyphen is 4.5x less distinguishable than it would be with a comparable monospaced font as the default. This problem exists in every browser where the user's preferences and or add-ons aren't overriding the fonts.
Firefox 151.01:

Steps to duplicate:
- Edit a previous file, adding a comment that contains a space followed by a minus sign.
- Create a PR for that change
- View the differences in the PR by clicking on the modified file
- Click the gear in the upper right
- Set the Diff behavior to Side-by-side
- Under show, check whitespace characters
- See how the whitespace and the hyphen don’t look all that different
From what we see, this primarily affects Windows but does not appear to be specific to Chrome, as we have seen the same problem in Firefox and Edge. We suspect this issue could be solved by moving the Ubuntu font to the bottom of the list.
Here’s Edge version 148.0.3967.83:
This is not a new problem. Similar issues were seen in previous versions of Chrome and earlier versions of Bitbucket. This is still seen in Bitbucket 10.2.
This would seem to be an A11Y and Americans with Disabilities Act issue. The change will benefit everyone on Windows with Chrome, Firefox, or Edge who are not legally blind and need to be able to quickly differentiate one character from the next
Our request is to move Ubuntu Mono to the bottom of the list and add Courier New to the font list and use it as the default