MANSOQ Knowledge
← Knowledge library

Getting started

Use language, direction and accessible form feedback

Choose an enabled interface language and understand the supported form and dialog affordances without assuming a full accessibility certification.

Current source · source reviewed · 3 min read

Before you begin

1. Choose an available language

At login, use the language choices shown below the sign-in experience. Within the application, use the language selector where the page provides it. Only locales listed in the deployment’s availableLocales setting are shown.

2. Confirm Arabic direction and labels

The application synchronizes the HTML language and direction with the selected language. Arabic is a defined locale, and the canonical facility type catalogue supplies explicit English and Arabic labels. Check the active language after changing it.

3. Read field feedback

Shared form controls connect their labels, descriptions and validation-message identifiers to the input and expose an invalid state when validation fails. Read the message associated with the field and correct it before resubmitting.

4. Use the visible dialog controls

Shared dialogs include a labelled Close control and visible focus styling. Use the screen’s Cancel or Close action when you need to leave the dialog. Follow the ordinary confirmation or unsaved-change behavior of the specific workflow.

5. Use the appropriate layout and controls

The application has responsive sheets, drawers and navigation in several workflows. On a touch screen, use the displayed controls rather than keyboard-only instructions. If a required control is inaccessible with your input method, report the exact page, action and browser to the deployment support team.

Remembered language choice

The language selector saves an explicit user choice in browser storage when available. Initial language selection considers the explicit choice, tenant default, browser preferences and enabled locales.

Known validation boundary

The inspected source supports language direction, labelled form feedback and accessible dialog primitives. This audit does not establish complete WCAG conformance, every screen-reader interaction, contrast compliance or consistent keyboard behavior for every custom plugin.

Translation scope

The presence of Arabic as a locale and bilingual facility labels does not prove that every clinical term, custom questionnaire, imported document or plugin has a complete Arabic translation. Those contents require their own review.

Troubleshooting

Arabic is absent from the language choices

Ask the deployment administrator to verify that Arabic is included in the enabled locales. The selector filters out languages that are not enabled.

A custom clinical form has untranslated labels

Ask the form or terminology owner to review that configured content. Changing the interface language does not automatically translate every custom clinical asset.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.