You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Oskari map in our public app. I could not find any mentions about accessibility in your docs.
What is Oskari's take on accessibility?
Is there some level of accessibility goal in your open source development of the map implementation (A/AA/AAA in WCAG 2.1) or comments in regards to EU accessibility directive?
If not, do you have future plans to improve accessibility?
How to implement accessible maps with Oskari? What common pitfalls are there?
Ask for more.
The text was updated successfully, but these errors were encountered:
In short: adding more accessibility features would be awesome but we would definitely need and appreciate help adding these. At the moment this is not something we are actively working on nor have a target level.
And as an update to the actual question: there has been discussion on Oskari's accessibility this year in Oskari's Joint development forum. I think that there's more interest on the topic at the moment and keeping this as an open issue on GitHub until it is resolved would be good.
We are using Oskari map in our public app. I could not find any mentions about accessibility in your docs.
What is Oskari's take on accessibility?
Is there some level of accessibility goal in your open source development of the map implementation (A/AA/AAA in WCAG 2.1) or comments in regards to EU accessibility directive?
If not, do you have future plans to improve accessibility?
How to implement accessible maps with Oskari? What common pitfalls are there?
Ask for more.
The text was updated successfully, but these errors were encountered: