NiceGUI elements for ARIA standard

[Elyon7]

Can we improve the library in order to have all NiceGUI elements automatically adapted for ARIA standard? At the moment we need to add the property for each element manually.
Thank you

[falkoschindler]

Thanks for sharing this idea, @Elyon7! Accessibility is definitely an important aspect and we should pay attention to it.

But how exactly can we improve UI elements to follow the ARIA standard? What attributes should be set automatically, which should be exposed as a parameter?

MDN writes:

Warning: Many of these widgets are fully supported in modern browsers. Developers should prefer using the correct semantic HTML element over using ARIA, if such an element exists. For instance, native elements have built-in keyboard accessibility, roles and states. However, if you choose to use ARIA, you are responsible for mimicking the equivalent browser behavior in script.

I wonder if we're already using "correct semantic HTML element" when using Quasar-based elements like ui.input etc. We should check what Quasar already does in terms of accessibility, what is missing, and what should be added via ARIA.

[Elyon7]

In this website I found the main element to pass ARIA label: https://www.w3.org/WAI/ARIA/apg/ I think that almost all the elements that start with ‘ui.’ need to be set accessible automatically and we can also add a free optional parameter for each element useful to explain the aim of the element in the context manually. I don’t know if people automatically read all HTML text images elements etc. by using a screen reader. I thought that a label ARIA was necessary. Yes we need to check if Quasar itself make the elements readable with a screen reader for blinded people. Thank you Eleonora