Skip to content

Feature/should haves for inclusive language#19378

Merged
FAMarfuaty merged 148 commits intotrunkfrom
feature/should-haves-for-inclusive-language
Dec 13, 2022
Merged

Feature/should haves for inclusive language#19378
FAMarfuaty merged 148 commits intotrunkfrom
feature/should-haves-for-inclusive-language

Conversation

@agnieszkaszuba
Copy link
Copy Markdown
Contributor

@agnieszkaszuba agnieszkaszuba commented Dec 12, 2022

Context

  • This PR includes a number of improvements to the inclusive language analysis.
  • Note that this PR was set to non-user facing as the changelog generator had issues with the list. The items have been added manually to the user-facing changes in the changelog.

Summary

This PR can be summarized in the following changelog entry:

  • Improves the inclusive language analysis by expanding the number of non-inclusive phrases recognized as well as by improving the feedback, for example by adding more inclusive alternatives or fixing inconsistencies. Specifically, this includes the following changes:
    • Adds "OCD", "normal" and "abnormal" to the terms that are targeted by the inclusive language analysis in specific contexts.
    • Adds "stupid" to the terms that are always targeted by the inclusive language analysis.
    • Removes the term "African American Vernacular English" from the terms targeted by the inclusive language analysis.
    • Changes the terms "exotic" and "oriental" to be considered potentially non-inclusive in the inclusive language analysis, adds exceptions and updates their feedback.
    • Improves the categorization of the targeted terms in the inclusive language analysis by splitting the other category into a more specific one.
    • Improves the feedback for some (potentially) non-inclusive target terms in the inclusive language analysis.
    • Adds more alternatives to some (potentially) non-inclusive target terms in the inclusive language analysis.
    • Adds terms that are only considered (potentially) non-inclusive when they are followed by certain words or a punctuation mark.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • Smoke test the inclusive language analysis.

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Block/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • For RC testing, refer to the testing instructions in the individual PRs linked above.

  • QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

UI changes

  • This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

  • I have written documentation for this change.

Quality assurance

  • I have tested this code to the best of my abilities
  • I have added unit tests to verify the code works as intended
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label and noted the work hours.

Fixes https://yoast.atlassian.net/browse/PC-1036

hdvos and others added 30 commits November 14, 2022 10:58
…vePunctuation.js

Co-authored-by: Hans-Christiaan Braun <hans-christiaan@yoast.com>
Co-authored-by: Hans-Christiaan Braun <hans-christiaan@yoast.com>
Co-authored-by: Hans-Christiaan Braun <hans-christiaan@yoast.com>
…unctionWords.js

Co-authored-by: Hans-Christiaan Braun <hans-christiaan@yoast.com>
…7-target-phrases-based-on-function-words-participles-and-or-punctuation-marks
hdvos and others added 18 commits December 8, 2022 13:05
…ve-phrases

PC-981 Adds 'stupid' to non-inclusive phrases
…mprove-categorization-of-inclusive-language-phrases
…fat-and-obese

Inclusive language should haves: adapt feedback for 'fat' and 'obese'.
…mprove-categorization-of-inclusive-language-phrases
…com:Yoast/wordpress-seo into PC-978-add-normal-and-abnormal-to-non-inclusive-phrases

# Conflicts:
#	packages/yoastseo/spec/scoring/assessments/inclusiveLanguage/configuration/otherAssessmentsSpec.js
#	packages/yoastseo/src/scoring/assessments/inclusiveLanguage/configuration/otherAssessments.js
…com:Yoast/wordpress-seo into PC-1015-improve-categorization-of-inclusive-language-phrases

# Conflicts:
#	packages/yoastseo/spec/scoring/assessments/inclusiveLanguage/configuration/appearanceAssessmentsSpec.js
#	packages/yoastseo/spec/scoring/assessments/inclusiveLanguage/configuration/otherAssessmentsSpec.js
#	packages/yoastseo/src/scoring/assessments/inclusiveLanguage/configuration/sesAssessments.js
…o-non-inclusive-phrases

Add phrases with normal and abnormal to non-inclusive phrases
…com:Yoast/wordpress-seo into PC-1015-improve-categorization-of-inclusive-language-phrases

# Conflicts:
#	packages/yoastseo/spec/scoring/assessments/inclusiveLanguage/configuration/otherAssessmentsSpec.js
#	packages/yoastseo/src/scoring/assessments/inclusiveLanguage/configuration/otherAssessments.js
…f-inclusive-language-phrases

PC-1015 Improve categorization of inclusive language phrases
@agnieszkaszuba agnieszkaszuba added this to the 19.13 milestone Dec 12, 2022
@agnieszkaszuba agnieszkaszuba added the changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog label Dec 12, 2022
iolse and others added 3 commits December 12, 2022 17:11
…com:Yoast/wordpress-seo into PC-1021-non-inclusive-phrases-containing-punctuation-are-not-recognized
…ntaining-punctuation-are-not-recognized

inclusive language should haves: fix unreleased bug that phrases with hyphens were not recognized
@FAMarfuaty FAMarfuaty merged commit aaf1531 into trunk Dec 13, 2022
@FAMarfuaty FAMarfuaty deleted the feature/should-haves-for-inclusive-language branch December 13, 2022 09:58
@enricobattocchi enricobattocchi modified the milestones: 19.13, 19.14 Dec 13, 2022
@manuelaugustin manuelaugustin added changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog and removed changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog labels Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants