OverviewStarting in 24.2, the Styled Text Editor Component is available directly in the product. Consider using this in place of the plug-in moving forward. For more information, review: https://docs.appian.com/suite/help/latest/Styled_Text_Editor_Component.html
Visit https://community.appian.com/w/the-appian-playbook/1378/end-user-rich-text-editor-component for more information. If you have any problems installing or using the component, please see the https://community.appian.com/w/the-appian-playbook/1603/rich-text-editor-component-plug-in-troubleshooting-guide
Key Features & Functionality
Supported Browsers: Chrome, Firefox, Edge, SafariSupported on Mobile
Our application got flagged for some accessibility/508 violations related to this component, due to the instructions and label not being read by a screen reader when navigating via keyboard tabbing into the field. Are there any plans to address this? Note that we cannot use the native styled text editor because we need the additional formatting options that are available on this plugin.
The label/instructions framework of component plugins is not specific to this plugin, nor does any plugin have any control over it. I would recommend opening a ticket with Appian Support along the lines of "Common Parameters of Component Plugins do not adhere to Accessibility Standards (one example Rich Text Editor Plugin)".