With a screen reader, Ceros currently reads out text character-by-character (or line-by-line, if you have accelerated text rendering turned on). Component Mode will allow the browser and screen reader to read entire text boxes more fluidly.
Component Mode is a huge step forward in our efforts to improve the accessibility of the Ceros platform. Text in Ceros will now be truly readable by screen readers with Component Mode, which is a requirement of accessibility audits.
As such, Component Mode has a number of additional key benefits:
- Improves experience load times because there is significantly less HTML to render, and less data to load so pages load faster
- Improves SEO by allowing crawlers to read whole sentences of text rather than character-by-character or line-by-line.
- Supports Accessibility (as a requirement) by allowing Screen Readers to read whole blocks of text rather than character-by-character or line-by-line.
Additionally, anyone who has experienced jumbled text while using Adaptive Layouts will be delighted to learn that Component Mode resolves this issue.
How It Works
Component Mode is located in the Studio, under Settings > Experience Performance > Text Rendering Mode. You will now see these three options under text rendering mode:
- Component (Recommended) NEW!
- Line (Formally Accelerated Text Mode)
- Character
Notes
- For new experiences, the text rendering mode will default to Component Mode.
- Old experiences remain in the mode they were originally set to.
- To change the text rendering mode on existing experiences to component mode- Go to Experience Settings > Experience Performance > under Text Rendering Mode- Select Component Mode
- You must republish existing experiences after switching text rendering modes
- When switching text rendering modes on existing experiences, this can sometimes affect the layout. Most text components won’t require any changes but it might be possible that a text component would need to be resized slightly to achieve the same layout