To make portal and application pages accessible, you must follow multiple guidelines, regulations, and success criteria. The four principles of the WCAG alone comprise approximately 90 success criteria.
Accessibility requirements can, therefore, result in an extensive list with all the test and success criteria. See this overview or list, starting with the section WCAG, BITV and Intrexx.
Auto-generated accessibility
Equally, Intrexx is well-equipped for creating accessible portal and application pages. Intrexx has an out-of-the-box accessible layout, for example.
In the Accessible Layout in Intrexx, key conditions for accessibility are already satisfied:
-
The contrast between the background and font is great enough.
-
Elements are highly visible and in focus.
-
The page structure is preserved when zoomed to 200%.
If you create application pages using the Page Wizard, they are immediately accessible. For example, they are always responsive (a key guideline in the context of accessibility) and generate a heading with the HTML tag "h1" (also a key guideline for accessibility), so that all the requirements are met for a meaningful (semantic) page structure.
Another important aspect, especially for screen readers, is the use of ARIA roles and attributes. These can also be used to make text that is not displayed on the (visible) surface of a page accessible to screen readers, and therefore, audible for blind users. Intrexx automatically preassigns ARIA roles and attributes for (operating/control) elements at all necessary points. Yet, it is easy to manually assign ARIA roles and attributes at any time through a separate "Accessibility" tab.
These examples illustrate the extensive, automatic out-of-the-box support offered by Intrexx. It lets you satisfy several conditions for accessibility without having to intervene explicitly or manually.
Manual adjustments
By using Intrexx, you already automatically satisfy a large quantity of the success criteria for accessibility. But you will probably need to make some manual adjustments to meet all the accessibility conditions.
One of the reasons for these adjustments is that some activities involved in creating portal and application pages have to be performed manually as a rule. For example, this is true for recording text alternatives or the arrangement of elements on a page. It is your responsibility as a Web author to arrange elements on a page in a comprehensible and sensible way.
In the overview or list with the WCAG or BITV guidelines WCAG, BITV and Intrexx), you will see a raft of notes and instructions on how to make manual adjustments related to accessibility for each guideline.
Best Practices
Intrexx offers you out-of-the-box support to make your portal and application pages accessible. Additionally, the following section How to make your pages accessible - Best practices practices provides some best practices with basic tips on how to create portal or application pages. If you follow the instructions, you will have already achieved some key requirements for the accessibility of your portal.
Email us