Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Non-text elements lack sufficient colour contrast. #1758

Open
DaveTryon opened this issue Jan 17, 2024 · 1 comment
Open

[BUG] Non-text elements lack sufficient colour contrast. #1758

DaveTryon opened this issue Jan 17, 2024 · 1 comment
Labels
bug Something isn't working status: resolved This issue has been merged into main.

Comments

@DaveTryon
Copy link
Contributor

(This is split out from #1738)

From @delphinegilbert:

Hello,

An accessibility audit was performed on Accessibility Insights for Windows in our department and the following issue was found:

Description of issue

Right under "Live Inspect", there is a search input field that lacks any kind of visible border which makes it difficult to see. The input field's colour contrast fails against the white background.

Impact on users

This will especially impact people with low vision and non-keyboard, as users may not see at all that they the input field is there.

Steps to reproduce

Launch the program, and dismiss the startup windows. Using your mouse, hover or click on any other window for the program to start inspecting. It should then display an item tree, there there's a search field at the top.

image

@DaveTryon DaveTryon added the bug Something isn't working label Jan 17, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the status: new This issue is new and requires triage by DRI. label Jan 17, 2024
DaveTryon added a commit that referenced this issue Jan 19, 2024
#### Details

As called out in #1758, the search box doesn't meet non-text color
contrast requirements. This PR changes the border so that it's
consistently displayed in all themes.

##### Motivation

Address #1758

##### Screenshots

Mode | Before (only dark mode has border) | After (all modes have
border)
--- | --- | ---
Light |
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/84b2dab8-afa1-4179-9acd-95f77d80a226)
|
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/183dff19-de12-4db9-899d-02523fd44086)
Dark |
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/91c498c7-f64c-4dff-8948-2a2cf91fb8db)
|
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/67eb11c7-7904-4ccb-a549-d8c74f0c235a)
Aquatic |
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/1cc060ba-774f-4090-bb2a-1b6f207c0529)
|
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/220dbebc-ec2e-4bdc-9b90-5bddfc8cbe7b)
Desert |
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/92482f5c-fa25-40d3-805b-77bcbdd9780c)
|
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/188512a1-15e4-459e-af49-42d58ccb699a)
Dusk |
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/e1f07522-d18e-45f5-a375-33d20f3ed582)
|
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/6c340b31-b555-414c-b704-1d316591b3bc)
Night Sky |
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/bcbb5291-7b5b-4a78-8710-338575b8b922)
|
![image](https://github.com/microsoft/accessibility-insights-windows/assets/45672944/c39a1fb6-a38b-46e8-8cda-52ac16f6b4fe)

##### Context

<!-- Are there any parts that you've intentionally left out-of-scope for
a later PR to handle? -->
Since the `SearchPanelBorderThickness` value is now always 1, I replaced
the variable (originally added for dark mode) with a hardcoded value

<!-- Were there any alternative approaches you considered? What
tradeoffs did you consider? -->

#### Pull request checklist
<!-- If a checklist item is not applicable to this change, write "n/a"
in the checkbox -->

- [ ] Run through of all [test
scenarios](https://github.com/Microsoft/accessibility-insights-windows/blob/main/docs/Scenarios.md)
completed?
- [x] Does this address an existing issue? If yes, Issue# - 1758
- [x] Includes UI changes?
- [x] Run the production version of Accessibility Insights for Windows
against a version with changes.
  - [x] Attach any screenshots / GIF's that are applicable.

> Note: After the PR has been created, certain checks will be kicked
off. All of these checks must pass before a merge.
@DaveTryon
Copy link
Contributor Author

This is live in Canary and will be included in our next Production release

@DaveTryon DaveTryon moved this from Needs triage to Needs release in Accessibility Insights Jan 22, 2024
@DaveTryon DaveTryon added status: resolved This issue has been merged into main. and removed status: new This issue is new and requires triage by DRI. labels Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working status: resolved This issue has been merged into main.
Projects
Status: Needs release
Development

No branches or pull requests

1 participant