Nintex Automation accessibility enhancements

KB003712

Introduction 

This article outlines recent accessibility enhancements implemented Nintex Automation K2 5. Previous versions of K2 SmartForms established foundational accessibility features, as documented in the existing Accessibility Compliance Whitepaper.
Building on that foundation, Nintex Automation K2 5.9 introduces targeted improvements to address key accessibility issues.

Accessibility Enhancements in Nintex Automation K2 5.9

1. Visual Labels for Screen Reader Tools

Issue:
Some form controls lacked proper visual labels or accessible names, limiting the effectiveness of screen readers.

Resolution:
A new Accessibility Text property has been added for selected controls.
This property allows users to define custom text that is read aloud by screen readers when users navigate through form controls.

Controls Enhanced:

• Dropdown List Control
• File Attachment Control
• Image Attachment Control
• Calendar Control
• Text Area Control
• Textbox Control
• Radio Button List Control
• Checkbox List Control
• Slider Control
• Multi-Select Control
• Listbox Control

Certain controls such as Labels, Data Labels, Radio Buttons, and Radio Button Groups were already accessible and did not require modification.

2. Selected and Unselected State Announcements

Issue:
Some list and multi-select controls did not announce item selection states when used with a screen reader.

Resolution:
The following controls now announce selected and deselected values during interaction:

• Multi-Select Control
• Listbox Control
• Checkbox List Control

This enhancement allows users to better understand their selections without requiring visual confirmation.

3. Screen Reader Navigation Improvements

Issue:
Certain controls could not be fully navigated using a keyboard when a screen reader was active.

Resolution:
Keyboard navigation has been improved for:

• Dropdown List Control
• Slider Control
• Image Attachment Control
• File Attachment Control

This enables a more consistent experience when using screen readers or navigating without a mouse.

4. Popup and Frame Title Announcements

Issue:
Popups and dialogs in the Management site lacked visible titles and were not properly read by screen readers.

Resolution:
Popups in Management now announce when they receive focus, including correct reading of frame headers and control options such as minimize and close.

This improvement ensures users are aware when new dialog windows open or change focus.

5. Link Text Accessibility Enhancements

Issue:
Some links in Workspace and Management did not include readable text, making them inaccessible to screen readers.

Resolution:
Descriptive link text has been added to key areas including:

• Quick Search Icons
• Refresh Icons
• List View Paging Links
• Expand and Collapse Links
• Calendar Control SVG Links (Date, Time, and Date-Time options)

These updates improve clarity and context when navigating interactive elements via assistive technologies.

6. Item View Table and Table Control Enhancements

Issue:
Screen readers made redundant announcements such as “table” and “row” repeatedly while navigating controls inside table containers.

Resolution:
Unnecessary declarations have been minimized to streamline the reading experience.
Users now experience smoother navigation and clearer control descriptions when using screen readers on form views containing table layouts.

Best Practices for Accessibility Implementation

To ensure optimal results when designing accessible forms and views, the following best practices are recommended:

1. Use Clear, Descriptive Accessibility Text
   • Avoid special characters.
   • Provide short, meaningful descriptions for controls.
   • The Accessibility Text property can be left blank, in that case, the screen reader defaults to the control name.
2. Avoid Redundant Tooltips
   • Tooltips are also read by screen readers, potentially duplicating information.
   • When using both Accessibility Text and tooltips, ensure the text provides complementary and not repetitive information.
3. Simplify User Interaction
   • Keep labels concise and consistent across forms.
   • Avoid nesting too many controls within tables, as this can create verbose audio feedback.
4. Validate Screen Reader Experience
   • Test forms using popular screen readers (e.g., NVDA, JAWS) to ensure accurate reading order and control accessibility.

Future enhancements will build upon this progress to deliver even greater accessibility alignment across the Nintex platform.