Joel Parks, MESCIUS
Accessibility has become an increasingly important consideration in modern web development. As organizations build applications for larger and more diverse audiences, developers need to ensure their applications are usable by everyone on every platform, including individuals who rely on assistive technology like screen readers, keyboard navigations, and high-contrast displays when using computer applications. For enterprise applications, accessibility can be particularly challenging. Complex user interface components, such as data grids, charts, and input controls, often require specialized interactions that must be accessible to users with different needs. Building these experiences can be time-consuming, especially when developers must account for accessibility requirements alongside application functionality.
To help address these challenges, MESCIUS USA, Inc. has made significant investments in accessibility across the Wijmo JavaScript UI component library. Over the past two years, Wijmo has introduced improvements to keyboard navigation, screen reader compatibility, color contrasts, and more, culminating in the milestone 2026 v1 release, which included WCAG 2.2 AA support across applicable control requirements. These improvements continued with Wijmo 2026 v2, demonstrating our ongoing commitment to making enterprise JavaScript applications more accessible.
The Web Content Accessibility Guidelines (WCAG) are internationally recognized standards developed by the World Wide Web Consortium (W3C). These guidelines provide recommendations for making web content more accessible to users with visual, auditory, physical, and cognitive disabilities. WCAG organizes accessibility around four fundamental principles: perceivable, operable, understandable, and robust. Each principle addresses different aspects of the user experience, from ensuring sufficient color contrast to supporting navigation without a mouse.
WCAG 2.2 builds upon previous versions of the guidelines by introducing additional requirements that improve accessibility for users with limited mobility, low vision, and other disabilities.
For developers building enterprise applications, following these standards is important for both usability and organizational accessibility requirements. However, compliance can be difficult when applications depend on complex third-party components. This is where Wijmo’s built-in accessibility features can make a difference.
Over the past two years, Wijmo’s development team worked to improve accessibility throughout the component library, progressing through WCAG 2.0 and 2.1 before reaching the applicable requirements of WCAG 2.2 Level AA. This initiative involved more than updating individual controls; the team revisited how users interact with components, how assistive technologies interpret their content, and how visual elements are presented under different accessibility settings.
Several areas received particular attention, including keyboard interaction models, focus management, WAI-ARIA attributes, screen reader announcements, color contrast, and interactive target sizes. The Wijmo 2026 v1 release marked the completion of the major WCAG 2.2 accessibility roadmap, while subsequent releases have continued to refine individual behaviors to improve the user experience, because accessibility is never done.
One of the most significant areas of improvement has been keyboard navigation. Many users rely entirely on their keyboards to interact with web applications. For these users, essential functionality cannot depend exclusively on mouse actions such as dragging, hovering, or clicking.
Wijmo has expanded keyboard support across its controls to make common operations more accessible. These improvements are particularly noticeable in FlexGrid, Wijmo’s JavaScript data grid component.
For example, FlexGrid now supports keyboard commands to resize and rearrange rows and columns. When the corresponding grid features and header focus settings are enabled, users can perform operations that traditionally require a mouse. These additions allow keyboard users to take advantage of more advanced grid functionality while maintaining a consistent interaction experience.
Similar improvements have been made across Wijmo’s filtering, navigation, and input controls, helping users move between components and complete tasks without relying on a pointing device.
Another important focus has been improving compatibility with screen readers.
Screen readers help individuals with visual impairments navigate applications by announcing the contents and functionality of interface elements. However, these technologies depend on applications to provide accurate semantic information via HTML and accessibility attributes. Wijmo uses WAI-ARIA attributes to communicate information about its controls, including their roles, states, labels, and relationships.
Recent accessibility improvements have refined these attributes and the information announced by screen readers such as NVDA, JAWS, Narrator, and VoiceOver. These updates help users understand the current state of interactive controls, identify available actions, and navigate complex interfaces more effectively.
For example, Wijmo 2026 v2 corrected an issue in which FlexGrid's ColumnPicker announced a column's underlying data index rather than its actual position in the displayed grid. Previously, a screen reader might announce a column as the eighth column even though it appeared fifth in the interface. With the improvement, the announcement reflects the visible column position, providing more accurate information to users navigating the grid.
Although this may seem like a small adjustment, improvements like these can significantly affect how easily individuals navigate data-heavy enterprise applications.
Accessibility extends beyond keyboard navigation and screen readers. Visual presentation is equally important, particularly for users with low vision or those who depend on high-contrast operating system themes.
Wijmo's accessibility updates include refinements to text and non-text contrast, control boundaries, selection indicators, and focus visibility. These improvements help distinguish interactive elements from their surrounding content and make it easier for users to identify their current position within an application.
The updates also address the sizing and spacing of interactive targets, making controls easier for users with limited motor precision to operate. For applications containing numerous buttons, icons, and interactive data elements, these changes contribute to a more consistent and usable interface across different accessibility configurations.
While Wijmo provides built-in accessibility support, creating a fully accessible application remains a shared responsibility between the component library and the developer.
Developers must still consider how individual components are configured and integrated into their applications. Custom templates, application styling, form labels, and navigation workflows can all influence the accessibility of the finished product.
For example, developers using FlexChart should provide descriptive chart labels and accessible alternatives for important visual information. Applications should also be tested to ensure users can navigate between components logically and complete essential workflows using assistive technologies.
Tools such as Axe DevTools and screen readers such as NVDA can help identify accessibility issues during development.
By combining Wijmo's built-in features with appropriate application-level testing and accessibility practices, developers can create more inclusive user experiences without implementing every accessibility interaction themselves.
With the completion of its major WCAG 2.2 accessibility roadmap in 2026v1 and further enhancements in 2026 v2, Wijmo continues to demonstrate its commitment to accessibility as an ongoing development priority. To learn more about Wijmo and keep up with its accessibility updates, visit the MESCIUS website.