Like Tove and Wyomi pointed out, we are working towards WCAG 2.x Level AA compliance. I write 2.x since 2.2 is just out, but most significant changes in 2.2 are about Level AAA. We are fully committed to meeting this global standard, but we cannot say that we are fully meeting the AA level today. However, we can't work against regional and local standards, but we lean on the global WCAG which covers the most important aspects of accessibility. Of course, we understand that in some industries and regions/countries there are specific standards, in particular in public sector or gov organizations; we see ADA with Section 508 in the US, BITV in Germany, etc. In Asia there are Japanese Industrial Standards X8341-3 and in China national accessibility standards with GB/T 37668-2019, etc.However, most standards are a subset of WCAG, and some are supersets of WCAG. Some of these also include services and tools in addition to software.However, when it comes to the use of IFS Cloud, WCAG covers m
A solution for this problem has been developed and the correction will be in the next possible Service Updates for both affected tracks. Will solve the issue in both Chrome and Edge (given they are using the same engine). 22.1.15 (22R1 SU15) , 22.2.8 (22R2 SU8) Fingers crossed Chromium doesn’t change it’s HTML/CSS styling interpretation again related to this. Again, we understand the frustration this causes users, and hope it’s a driver for taking the latest SUs.
Thanks for reporting, being investigated.
Hello,This work has been based on extensive research with both customers, real end users and pre sales. I am happy to say that we actually base the changes on real research and input from users of both end user lobbies and people doing Lobby configurations. At the same time, realize a change like this may always take some getting used to - and as always with UX there are many opinions.There are multiple reasons for the changes, but a few of them includes Theming support (Light and Dark) of Lobby and the introduction of Appearance Designer where we have the ability to “brand” the Aurena UX including Lobbies. This has been very well received, including feedback from 21R2 Pioneer customers.Part of the change is also to set focus to the actual data in the lobbies. So not sure why you say White is a poor choice. You don’t say why.We learned the readability (usability) was poor for some data visualization elements (charts etc) when sometimes configured using strong background colors.When it
Appreciate the feedback on Sticky Notes.It’s clear that the easy of use and the “in your face” aspect is key here. We as users of IFS software are humans, and we like to make analogies to the real world and sticky notes are a tangible thing. That was the whole idea behind sticky notes. Custom fields or a separate tab or a regular Notes field could seem to serve the same purpose, and as much as it does that from a tech point of view (rich text and images a side) - it doesn’t provide the same user experience.Note also that Stickies are stored as a connected objected (sort of), so the data is not searchable on the main business object, such as Customer Order or an Invoice. It is also not possible to put the data on a report etc. Sticky notes uses RTF (Rich Text Format) which is a (dying) Microsoft format used mostly in Windows - so it is not suitable for cross platform and web use. It is clear sticky notes is very important for some of you. It is also clear Sticky Notes is not implemented
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
