Pride Month is celebrated worldwide in June. This is a time when visibility, diversity and equality take center stage. What at first glance appears to be primarily a social and cultural focus can also be transferred to digital spaces. Today, participation means not only access to public and physical places, but also to digital offerings.<\/p>\n
Accessibility in software plays a central role in this. It ensures that all people\u2014regardless of physical or cognitive limitations\u2014can use digital products and services on an equal basis. This is a basic requirement for inclusion in particular and cannot be treated as a minor issue.<\/p>\n
It is worth focusing on accessibility, not only because Pride Month reminds us of the importance and relevance of equality, but also because manufacturers of digital products bear responsibility for whether people can participate in them or not.<\/p>\n
Accessibility is about designing software so that it can be used by as many people as possible, regardless of whether they have limitations. It is about identifying and removing digital barriers.<\/p>\n
Accessibility is not only aimed at people with disabilities, but also at older people with temporary limitations or unfavorable usage situations, such as very bright light or a noisy environment. Accessibility cannot therefore be classified as a special case, but is an essential part of a good user experience.<\/p>\n
Typical aspects of accessible software are:<\/strong><\/p>\n Accessibility is often seen as an extra or \u201cnice to have,\u201d but it\u2019s way more than that. Accessibility is a legal requirement, a sign of social responsibility, and a quality feature of modern software.<\/p>\n Accessibility is not an afterthought at NEXIS 4, but an integral part of the design process and product development. Over the past few months, we have been working specifically to further improve the accessibility of our software.<\/p>\n A key example of this is the filter areas: checkboxes now clearly and consistently indicate their status, making it immediately apparent whether a filter is active or not. Users who use screen readers no longer have to struggle with duplicate or contradictory output, but receive directly usable information.<\/p>\n In multi-step processes such as wizards, we have revised the ARIA attributes. The progress bar now clearly communicates where you are in the process \u2013 without generating unnecessary or repeated screen reader output. This provides orientation and reduces uncertainty when navigating through more complex processes.<\/p>\n Drop-down lists have also been adapted so that the currently selected option is programmatically recognizable. This makes it easier to select specific options and make decisions, especially when you cannot see the screen. Alternative texts for icons and images have also been revised: instead of generic descriptions, they now provide meaningful, context-related information that really helps screen reader users.<\/p>\n The login area has also been revised accordingly \u2013 in addition to visual adjustments, the focus was primarily on improving usability with screen readers. The form elements are now reliably read aloud, allowing users to log in without barriers.<\/p>\n These changes have one thing in common: they are intended to improve the actual user experience and not just meet technical requirements. It is important to us that NEXIS 4 is also easy to use for people with disabilities \u2013 and we are continuing to work on this step by step.<\/p>\n Accessibility is an ongoing process in the further development of NEXIS 4, in which requirements and technologies are constantly changing. That is why this topic remains relevant to us, as it specifically improves usability for many people.\n
Why accessibility is not just a \u201cnice to have\u201d<\/h2>\n
\n
Step by step toward accessibility: Current improvements in NEXIS 4<\/h2>\n
Conclusion on accessibility in NEXIS 4<\/h2>\n
\nIf you yourself encounter barriers when using NEXIS 4 or have suggestions for improving accessibility, we would be happy to hear from you.<\/p>\n