Mercury Dokumentation

In order to be able to use these settings optimally, advanced technical understanding and knowledge of HTML and CSS are helpful.

Vorlesen

ReadSpeaker aloud page reading

Allows to read the content of a page aloud using the 'ReadSpeaker' service.
Dynamic function documentation
ReadSpeaker aloud page reading
Description of all element settings

Note: ReadSpeaker is a paid service! The service can only be used if the website for which the service is to be used has been activated by ReadSpeaker for a fee.

Weitere Informationen auf der ReadSpeaker Webseite
ReadSpeaker Sitemap configuration

ATTENTION: ReadSpeaker is NOT activated by default!

In order to use ReadSpeaker on a website, the sitemap configuration must be adjusted.

The easiest way to access the sitemap configuration of a website is to open the Sitemap Editor and select “Advanced” > “Sitemap configuration” from the toolbar menu.

In the sitemap configuration editor, add an additional “master configuration” using “+”. Enter the following file path in the field:
/system/modules/alkacon.mercury.bistuemer/configuration/readspeaker.master.addition.xml

When you activate ReadSpeaker for a website, ReadSpeaker will provide you with a customer ID for that website.

To use ReadSpeaker on this website, you must enter this customer ID in the file property “readspeaker.customerid” on the website’s site folder.

Adding the ReadSpeaker button to a page

The dynamic function “ReadSpeaker aloud page reading”

To be able to read a page aloud, the dynamic function ReadSpeaker aloud page reading must be dragged onto the page. This also creates the ReadSpeaker button.

To do this, select “Add content” (magic wand) in the toolbar at the top of the page editor. Switch to “Advanced elements” and select “Dynamic function.” Use drag & drop to drag the "ReadSpeaker aloud page reading" function onto the page to the place where you want the button to appear.

The ReadSpeaker Customer ID can also be set individually in the element settings of the dynamic function.

Choosing the area to read aloud using a CSS selector

By default, i.e. if no specific element settings have been made, the entire website, including the header and navigation, is read aloud. 

To restrict the area that is read aloud, the element setting “CSS modification” can be used on any elements (including layout rows) to select one of the possible options for reading aloud, e.g. “ReadSpeaker should read aloud”.

This can also be done for multiple elements on the page. In this case, all selected elements will be read aloud.

Supported content elements

For financial reasons, not all available content elements have been optimized for usage with "ReadSpeaker". Therefore, it is possible that certain content may not be read aloud optimally or correctly.

The following elements have been optimized for ReadSpeaker:

Problems with reading aloud may occur, particularly with content elements that make intensive use of JavaScript.

This function sets cookies in the “External content” group.

This function uses JavaScript from other servers.

The execution of the ReadSpeaker read-aloud function is controlled by the cookie banner. The ReadSpeaker option will therefore NOT be displayed if the web user has not consented to external cookies.

This function only affects pages on which the ReadSpeaker read-aloud function is also used.

When the page is loaded with external cookies enabled, various cookies are set by the ReadSpeaker provider. These may include tracking functions for the web user. It is not known in what form the cookies set are used for tracking the web user.

External JavaScript files are loaded from the ReadSpeaker provider's servers for this element. These are executed in the context of the page. This enables extensive tracking of the web user's activities on the displayed page. It is not known whether this is actually used for tracking the web user.

Further information on data protection with ReadSpeaker is available on the provider's website:
https://www.readspeaker.com/privacy/