Content Fragments HTML tags accessibility improvements

[#1]

Request for Feature Enhancement (RFE) Summary:	Using OOTB Content Fragments multiedit resource type, all <strong> and <em> HTML tags are being replaced with <b> and <i> tags.
Use-case:	Using OOTB Content Fragments multiedit resource type, all <strong> and <em> HTML tags are being replaced with <b> and <i> tags. The OOTB content fragment js should have logic to retain <strong> and <em> tags and not replace them with <b> and <i> tags. This is possible in the OOTB RTE component and is an issue only with multi-edit resource type for CF.
Current/Experienced Behavior:	We are facing an issue with OOTB Content Fragments multiedit resource type wherein all <strong> and <em> HTML tags are being replaced with <b> and <i> tags. This is causing accessibility issues and based on our analysis, we have to override the StyledTextEditor.js file (located at /libs/dam/cfm/admin/clientlibs/v2/authoring/contenteditor/editors/StyledTextEditor.js) to modify this default behavior.
Improved/Expected Behavior:	The OOTB content fragment multiedit js should have logic to retain <strong> and <em> tags and not replace them with <b> and <i> tags. This is possible in the OOTB RTE component and is an issue only with multi-edit resource type for CF.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as Cloud Service
Customer-name/Organization name:	Abbott
Screenshot (if applicable):
Code package (if applicable):

[#2]

@rampai 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-14681. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.