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

fix: add corrected text for color contrast tests #3399

Merged
merged 4 commits into from
Sep 25, 2020
Merged

fix: add corrected text for color contrast tests #3399

merged 4 commits into from
Sep 25, 2020

Conversation

shanisebarona
Copy link
Contributor

Description of changes

Updated the text for the assessment's adaptable content contrast test and fastpass to address issue #3337.

image

image

Pull request checklist

  • Addresses an existing issue: Text changes related to color-contrast 'needs review' #3337
  • Ran yarn fastpass
  • Added/updated relevant unit test(s) (and ran yarn test)
  • [n/a] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
  • PR title AND final merge commit title both start with a semantic tag (fix:, chore:, feat(feature-name):, refactor:). See CONTRIBUTING.md.
  • (UI changes only) Added screenshots/GIFs to description above
  • (UI changes only) Verified usability with NVDA/JAWS

@shanisebarona shanisebarona requested a review from a team as a code owner September 24, 2020 17:28
@ghost
Copy link

ghost commented Sep 24, 2020

CLA assistant check
All CLA requirements met.

Comment on lines 57 to 59
<b>
Assessment {'>'} Text legibility {'>'} Contrast
Assessment {'>'} Adaptable content {'>'} Contrast
</b>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed this was previously in bold, so I left as is, but it seems that most of the bold styling is wrapped in <Markup.Term></Markup.Term>. Should this be changed to <Markup.Term> instead?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! I agree that it would be an improvement to be consistent about using the semantically-named components; I think reusing Term would be better than using <b> here.

@ferBonnin ferBonnin requested a review from LiLoDavis September 24, 2020 17:41
Copy link

@LiLoDavis LiLoDavis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text changes look good to me.

Copy link
Contributor

@dbjorge dbjorge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me once the <b> -> <Term> thing is updated!

@shanisebarona shanisebarona merged commit c2ef285 into microsoft:master Sep 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants