ACCESSIBILITY - Web Content Accessibility Guidelines (WCAG)

[ted]

Can you point me to the Quasar documentation for this please?

[dobbel]

@ted you have to reply to his post. Like I do to your post, otherwise he’ll never see your message…

[ted]

@rstoenescu Can you point me to the Quasar documentation for this please?

[ted]

@dobbel thanks!

[ccheng]

@ted, only the one short line at https://quasar.dev/introduction-to-quasar#Best-practices-integrated-by-default is devoted to it in the entire documentation:

• Accessibility features

I agree it’s not as informative nor comprehensive as in the link you provided in your OP. Which is odd, since the Quasar documentation is of top-notch quality on other topics.

[indranil]

@rstoenescu Could you please clarify to what extent WCAG guidelines are followed? Here’s a link from PrimeTek (dated 7th Feb, 2021) that implies Quasar does not follow these guidelines to qualify as an accessible framework:

https://primetek.hashnode.dev/primevue-vs-vuetify-vs-quasar-vs-bootstrapvue

I love Quasar - it would be great to know the current extent of compliance of WCAG guidelines.

[metalsadman]

@indranil that’s a comparison table for primevue to look good and some info there are not accurate, just saying.

[indranil]

@metalsadman we still need more documentation to understand the extent of WCAG compliance - especially to refute such information. The post in question from primevue also compared other frameworks and did acknowledge that those are compliant. So just saying that their information is inaccurate won’t save the day for us

[dsl101]

+1 for more details—one line in the docs isn’t enough to convince a client we’re all set…

[dobbel]

@dsl101

I agree, you could create feature request in github:
https://github.com/quasarframework/quasar/issues

or open a new discussion about it on the new forum( this forum is dead):
https://github.com/quasarframework/quasar/discussions