Open the menu

    Accessibility

    This section addresses the support for accessibility of LumisXP. Some recommendations and tips are provided on how to set up or use the product for building websites within accessibility standards.

    With LumisXP, it is possible to build accessible solutions according to W3C recommendations. Therefore, all codes and layouts of pages automatically generated by LumisXP, which cannot be modified by users, are based on the accessibility recommendations contained in the documents “Web Content Accessibility Guidelines 1.0” and “Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0”, provided by W3C.

    Lumis services are not accessible, but can be made so through customizations of the XSLs of their interfaces, for example. The standard services Search and Navigation Bar have non-default styles, which make them accessible.

    Below, the main configuration points are listed and how the Lumis services can help build an accessible solution:

    Coding Standards

    LumisXP by default uses the XHTML10_STRICT specification. Therefore, the portal pages present the header <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN">

    The configuration of the encoding type to be used can be found in portal settings, in the item lumisportalconfig.xml.

    Language

    With LumisXP, it is possible to build solutions in different languages, through the service Localization Selector. It automatically inserts the corresponding language value in the HTML tag of the page. If the language is not specified using the service, a default language can be configured. The configuration of the default language used can be found in portal settings, in the section about lumisportalconfig.xml.

    CSS

    Stylesheets can be configured to be applied to the site pages. For accessible solutions, a custom stylesheet following the W3C standards must be used, which should be registered in the portal, through the CSS Manager.

    Files and Images

    There are specific rules for using images and links to documents in accessible solutions. The Lumis Documents and Images services allow registering information such as description and caption which can be updated dynamically, without requiring changes to the source code. Such information will be available in the XML and used by the adapted XSLs. The coding of the XSL performed by the developer must follow the W3C recommendations to make the solution accessible.

    Forms

    By default, in the DOUI framework, when clicking, for example, on an "OK" button, a java script is executed that validates all fields on the client side, before making the post to the server. The interaction, in this way, is better for the end user, as, for example, the refresh of the page is not performed.

    To create accessible forms in the DOUI framework, changes to the XSL of the form are necessary.

    1. Override the default XSL template lum_formHeaderProcessActionControls, specifying the identifier of the process action that should be executed on the POST.
    2. In the button that performs the process action (usually the "OK" button), instead of executing the default script, which performs client side validation, it is necessary to place an input control that performs the POST.

    In the XSL of the Search service (Search.xsl), for example, the mentioned changes have been implemented. Note that the execution of the process action "doSearch" is forced on the POST of the form:

    With these changes, forms created in the DOUI framework become accessible. However, field validations are performed on the server, minimizing user interaction in terms of decreased performance.

    References:

    Other information: