Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Managing the main content of your application

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

Define the primary content of your documents to ensure that users who rely on assistive technology can navigate your application with less effort.

When you create an application in App Studio, Pega Platform sets WAI-ARIA roles for different content areas automatically. For screen layouts that you set up manually in Dev Studio, Pega Platform assigns the main content WAI-ARIA role to the central area in a screen layout by default.

However, if the UI that you want to build is unusual, and the main content belongs in an area that is not a default area, change the WAI-ARIA assignment manually to ensure that assistive technology can interpret the screen correctly.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the User Interface category, and then click Harness.
  3. Open the harness that contains the screen layout that you want to edit.
  4. Select the main area of the layout, and then click the View properties icon.
  5. In the Panel properties window, in the Accessibility section, define the role for the area:
    • To remove semantic markup from the area and make it neutral to screen readers, in the Aria role list, select Presentation.
    • To designate the area as the main content area, in the Aria role list, select Main.
  6. Click Submit.
  7. On the harness form, click Save.
What to do next: If you set the WAI-ARIA role to Presentation and want to designate another layout as the main content area, assign a WAI-ARIA Main role to that layout. For more information, see Assigning WAI-ARIA roles to a Dynamic Layout.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us