The component InputColor is a wrapper for the native HTML element <input type="color">
which has accessibility problems:
- With NVDA, the element is announced as "clickable" and not as an input element.
- It's not possible to select a color using a screen reader.
For full accessibility, consider using predefined colors lists, e.g. using KolSelect or KolCheckbox.
When a table column changes its sort order (i.e. when its aria-sort
attribut changes), screen readers announce this change automatically.
For unknown reasons, this sometime does not happen in NVDA.
🐞 GitHub issue (PR) #5780 🐞 NVDA issue #10890 🐞 NVDA issue #8132
The components InputNumber and InputDate render their respective native HTML elements <input type="number">
and <input type="date">
which both support the
attribute readonly
.
When focusing the element, it's expected that the readonly
attribute is announced as part of the element description. This isn't the case for NVDA.
🐞 GitHub issue #5554 (For number) 🐞 GitHub issue #5749 (For date) 🐞 NVDA issue #13672
Toasts are rendered in a container that's appended as first element of <body>
and elevated using a high z-index
.
When using modal Dialogs these are rendered above toasts on the top layer. Hence, toast messages are always blocked by Modal Dialogs. We recommend completely avoiding Toasts in Modals and giving feedback within the modal directly.
The search
of this component is highly browser-dependent. For example, the close button is either shown or hidden depending on the browser. Accessibility is therefore not achieved.
🐞 GitHub issue #6307
KolSelect is using native HTML <select>
.
When using KolSelect with the multiple
property, the native HTML <select>
may cause problems with screen readers.
Often the entire selection is not read out, but only the last one. Therefore, the KolSelect has no full accessibility.