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
Starting around the time that the vs code iconography was changed to the new pencil thin "high contrast" versions, the field icon became hollow and outlined.
This does not match the iconography in any other Microsoft product, or IDE in general, and is objectively more difficult to identify at a glance.
For those who are visually impaired, these icons are difficult to tell apart since the only difference between field and property are the width of the icons (which is only a few pixels):
New "improved" iconography:
Old, universal, easy to see and easy to understand icon:
Same icons in Visual Studio (2017 and 2019):
I'm requesting that the field icon be changed back to how it was before, as it impacts accessibility and productivity, especially for visually impaired people.
The text was updated successfully, but these errors were encountered:
mhoelzel142
changed the title
Iconography: The field icon is too similar to the property icon (Accessibility)
Iconography: The field icon is too similar to the method icon (Accessibility)
Mar 17, 2020
Starting around the time that the vs code iconography was changed to the new pencil thin "high contrast" versions, the field icon became hollow and outlined.
This does not match the iconography in any other Microsoft product, or IDE in general, and is objectively more difficult to identify at a glance.
For those who are visually impaired, these icons are difficult to tell apart since the only difference between field and property are the width of the icons (which is only a few pixels):
New "improved" iconography:
Old, universal, easy to see and easy to understand icon:
Same icons in Visual Studio (2017 and 2019):
I'm requesting that the field icon be changed back to how it was before, as it impacts accessibility and productivity, especially for visually impaired people.
The text was updated successfully, but these errors were encountered: