Adobe Experience Manager supports standard accessibility features, such as alternate text for images, and extra features that can be accessed when creating content. Content authors use these features with components that use the rich text editor (RTE). The features includes adding alt-text, structural information through headings and paragraph elements, and so on.
Use the RTE plug-ins configuration to configure and customize the accessibility-related features. For example, use
paraformat to add extra block level semantic elements, including extending the number of heading levels supported beyond the basic
H3 provided by default. The rich text editing is possible using many components from the authoring user interface. The commonly used components are text, image, download, and so on.
The RTE functionality can be made available in many components. The primary component is the
Text component in Experience Manager, the following screenshot displays the rich text editor with a range of plug-ins enabled, including
For instructions to configure RTE, see configure the Rich Text Editor page. The article covers:
To activate a few or all features for a plug-in, configure the plug-in within the appropriate
rtePlugins sub-branch in CRXDE Lite.
New semantic block formats are made available for selection.
With structural elements available in the RTE via the paragraph format options, Experience Manager provides a good basis for the development of accessible content. Content authors cannot use the RTE to format font size or colors or other related attributes, preventing the creation of inline formatting. Instead, the authors can select the appropriate structural elements, such as headings and use global styles chosen from the Styles option to ensure clean markup and greater options for users who browse with their own style sheets and correctly structured content.
In some cases, content authors will find it necessary to examine and adjust the HTML source code created using the RTE. For example, a piece of content created within the RTE may require more markup to ensure compliance with WCAG 2.0. This can be done with the source edit option of the RTE. You can specify the
sourceedit feature on the
sourceedit feature carefully. Any typing errors and the unsupported features can introduce issues.