-
Notifications
You must be signed in to change notification settings - Fork 153
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Make failure highlight more visible (#6164)
#### Details <!-- Usually a sentence or two describing what the PR changes --> ##### Motivation <!-- This can be as simple as "addresses issue #123" --> close #5610 ##### Context <!-- Are there any parts that you've intentionally left out-of-scope for a later PR to handle? --> <!-- Were there any alternative approaches you considered? What tradeoffs did you consider? --> > Design team suggested trying multiple border colors with red in the center and white surrounding this. I implemented this based on one of the design team's suggestions listed in the issue. This will make failure highlight more visible, especially for a dark background as in the following picture. However, for pages with white or other background colors, it is not very effective. ##### screenshots/GIFs to description above Dark Background | Before | After | | ----- | ----- | |<img width="1267" alt="スクリーンショット 2022-11-03 20 00 00" src="https://user-images.githubusercontent.com/49313042/199704496-45e60ebe-4818-46a2-9203-c5d0364fd1f2.png">|<img width="1245" alt="スクリーンショット 2022-11-03 19 58 34" src="https://user-images.githubusercontent.com/49313042/199704535-48475702-dd3a-4b62-83ce-750d17137731.png">| White Background | Before | After | | ----- | ----- | |<img width="1015" alt="スクリーンショット 2022-11-03 20 14 26" src="https://user-images.githubusercontent.com/49313042/199707053-d05a56dc-be96-4a81-9fb8-c8e7ab1cc3d4.png">|<img width="1141" alt="スクリーンショット 2022-11-03 20 11 11" src="https://user-images.githubusercontent.com/49313042/199706541-03591b81-7287-4dd1-86c5-d437a87bc5fd.png">| #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [x] Addresses an existing issue: #5610 - [x] Ran `yarn null:autoadd` - [x] Ran `yarn fastpass` - [x] Added/updated relevant unit test(s) (and ran `yarn test`) - [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] PR title *AND* final merge commit title both start with a semantic tag (`fix:`, `chore:`, `feat(feature-name):`, `refactor:`). See `CONTRIBUTING.md`. - [x] (UI changes only) Added screenshots/GIFs to description above - [x] (UI changes only) Verified usability with NVDA/JAWS --- I've pushed an update that swaps to the box-shadow + outline version. It updates all the box drawers and their labels. It pushes the determination of box width to CSS to reduce the amount of per-element overhead in `style` attributes. It touches a bunch of files to change some `DrawerConfiguration` types from using `borderColor` to `outlineColor`. I also made some related refactorings while patching up the tests: * The `HighlightBoxDrawer` previously allowed for no formatter to be passed and contained a "default drawer configuration" for that case. This was never used except for tests; I've removed it and updated `drawer.test.ts` accordingly * Removed an obsolete `LandmarkValue` type (not used anywhere and referenced `borderColor`) I also fixed up some issues specific to the landmark visualizer; per discussion with @ferBonnin, I included the same white border there but reduced the width of the dashed part from 3px to 2px. I also fixed an issue I noticed with high-contrast-mode rendering of the landmark visualizer's dashed highlight boxes (previously, we used HC colors for the outer box, but not the text label box; this fixes it to be consistent). For reviewers, I recommend including the Deque Mars test page among your smoke tests; it has a lot of failures against non-white backgrounds that are good test cases. Screenshots of new behavior: ![ad-hoc automated checks](https://user-images.githubusercontent.com/376284/202323774-c748503a-1dff-442a-bc3a-0c29a81f0119.png) ![ad-hoc headings](https://user-images.githubusercontent.com/376284/202323853-6fdd3033-0a9d-4ea9-9431-5ba09fece587.png) ![ad-hoc landmarks](https://user-images.githubusercontent.com/376284/202323899-4f326328-15fa-498b-a71a-8c6d4e0f896b.png) Tab stops is not changed by this update and would need to be addressed in a separate PR: ![tab stops](https://user-images.githubusercontent.com/376284/202324015-d68a336a-99a3-4b4a-9cc1-9edfe02a8d3d.png) In Windows HC mode: ![automated checks visualizer in Windows high contrast Aquatic](https://user-images.githubusercontent.com/376284/202324100-16289224-d924-452e-9d98-ba4b093632dc.png) ![landmarks visualizer in Windows high contrast Aquatic](https://user-images.githubusercontent.com/376284/202328516-228ff77c-b564-4f19-b563-9163a75707ed.png) Co-authored-by: Dan Bjorge <[email protected]>
- Loading branch information
Showing
27 changed files
with
209 additions
and
180 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.