Within Visual LANSA, I am attempting to understand the capabilities for generating an accessible web application. When I search on terms such as accessibility or ARIA or screen reader I get very little information or assistance.
Say, for example, I add an input box to a client side reusable part. Currently a screen reader will not read the caption because of the way the html is constructed. I can see no support for ARIA tags to overcome this issue. Similarly I see no simple way to add html such as navigation blocks.
Considering how accessibility is such a big topic on web sites and web applications, I am wondering whether I have missed how LANSA handles and deals with this?
If anyone has undergone investigation into this, can point me in the right direction, or suggest how they have created an approach to tackling this, it would be really helpful.
Accessibility & ARIA
Re: Accessibility & ARIA
I was told recently that its shipping in an upcoming EPC. You could ask your local rep when that is.
HTH
bark
HTH
bark
-
René Houba
- Posts: 220
- Joined: Thu Nov 26, 2015 7:03 am
Re: Accessibility & ARIA
This is part of EPC150060, coming out soon.
Kind regards,
René
Kind regards,
René
Re: Accessibility & ARIA
This is good news.
Thanks for the update.
Thanks for the update.