Skip to main content
Version: 1.28 (Current)

Accessibility

Audience: Low-code Engineers, Business Users

General Description​

Plant an App's page layer and default components (menu, Forms 2.0, listings, tabs and dashboard) are built on accessible components: labelled fields, standard controls, page landmarks and a "Skip to main content" link. Themes, content and layouts belong to each site, so each portal can be tuned to the standard its organization answers to, such as WCAG 2.1 AA, Section 508 or EN 301 549.

Assessment and Conformance Report​

In October 2026, Plant an App completed an assessment of the end-user experience against WCAG 2.0 Level A and AA, which also covered the WCAG 2.1 and 2.2 criteria.

  • Remaining items: keyboard operation of a few controls, focus handling around dialogs, a consistent visible focus marker, and the default colour contrast. They're being fixed in the shared components, so every site gets the fix.
  • Conformance report: an Accessibility Conformance Report (VPAT 2.5, Section 508 edition) is in progress. An international edition, which covers EN 301 549 and WCAG 2.1, follows later.
  • Outside the report: builder and administration screens, Forms 1.x and features labelled experimental.

Building an Accessible Portal​

  • Test each portal. Test the delivered pages against WCAG 2.1 AA as part of acceptance: content, colours and custom components included.
  • Declare the language. Mark each page with the language of its content, for example lang="ro" for Romanian. See Languages.
  • Use the default components where you can. Custom HTML, scripts and themes need their own checks.

Revised 11/14/2026