Hello world! Welcome to WordPress. This is your first post. Edit or delete it, Read More → kobi September 2, 2022 1 Comment
Uncategorized Quasi distinctio molestiae quibusdam excepturi quia accusamus Molestias et omnis ex. Corrupti aperiam dolor sed vel veniam praesentium sit. Read More → kobi April 28, 2020 No Comments
Uncategorized Optio cum asperiores vel Id ut ratione porro sed rem ipsa sit A voluptatum in et Read More → kobi April 28, 2020 No Comments
Accessibility Guide Estimated reading: 3 minutes 132 views Cellosign is an accessible product in AA standard. However, in order for the forms and business processes to be accessible to the end users, a number of basic rules must be followed. Controllers Each visible (not hidden) controller in the form should have a field label and an additional description if necessary. Note: in Paragraph controller, if you use copied content, make sure that the “design” is not copied as well. Before pasting the content, you must first transfer the content through the Notepad software, which will clean the CSS styling, and then you can paste the text into the content editor. Images For the uploaded images, you must enter a value for accessibility, a text indicating what the image is, for example: In the case of a logo: the logo and company name must be specified. In the case of a signature image it must be stated: “the signature of” and the full name of the signer and his position. In the case of inserting images in the integration, an “Alt” tag must be applied to each image that is uploaded to the form. Headers labelling Emphasis should be placed on the structure of the document in terms of headers. The reference to headers labelling is very similar to the implementation of a document in WORD for example. See the example below. When using the header labelling as shown in the example, the end user’s browser will automatically adjust the text size, without further intervention. Should try to avoid using a specific font size and leave it only for exceptional cases. HTML developers can use a code editor to make additional labelling as shown here. Colorfulness The rule of thumb for color is maintaining contrast. Cellosign application for the end user comes with a built-in accessibility menu that also includes contrast, keyboard support and more. However, the starting point of an initial display for the form is to maintain a contrast of colors, for example dark text on a light color. In the picture here, the implementation of the colors is not correct since there is no high contrast between the background and the text. As a general rule, try to avoid different backgrounds than the default. Links Links in a paragraph field must be labelled according to the type of link. For a link to a website, select the text, click on the link icon, select “URL” and enter the desired address, for example: https://support.cellosign.com/. For the link to send an email, select the text, click on the link icon, select “E-mail” and add the address for sending an email, for example: support@cellosign.com. CSS In the Cellosign template, it is possible to implement CSS tags for use in the form elements. This option is open for the implementers with appropriate knowledge. Here are some highlights: The use of CSS is under the responsibility of the customer. We do not provide support for changes made to this component for accessibility or in general. Do not use image elements for backgrounds. If changes were made to the colors of the components, it is recommended to use a contrast test to make sure that the changes did not affect the accessibility of the form Client side In order for the clients to activate the accessibility of the received form they need to open the “Support and Accessibility Menu” from the top corner of the form and mark the “Activate accessibility” check box. Accessibility - Previous Accessibility statement