QlikView Accessibility Extensions - Section 508

[Anonymous]

Hello Community,

Is there anybody who works with the

QlikView Accessibility Extensions ?

I have the Exetension from

Here ist some Information about it (see Link Section 508 VPAT 😞
http://www.qlik.com/us/explore/solutions/industries/public-sector/government

The Exetension ist aviable on Qlik-Market:

QlikView Accessibility Client Extension

But there is no dokumentation about how to develope it.

Please Help.

Thanks,

Daniel

[sgk]

The object folders should be in this path ...AppData\Local\QlikTech\QlikView\Extensions\Objects\QlikView

I suspect the error is that you are missing the final QlikView folder.

/Sara

[sgk]

Same reply as above:

The object folders should be in this path ...AppData\Local\QlikTech\QlikView\Extensions\Objects\QlikView

I suspect the error is that you are missing the final QlikView folder.

/Sara

[#4]

Sarah --

Suppose I have a button that shifts a variable value which then prompts the display of an additional text box to appear. In my use I have a 'open help document'  button that launches a help text object to appear on the screen. Once the open button is clicked, only then does this additional text arise AND the open help doc button dissapears and a close help doc button appears. In the tab indexing. I have set this open to 10, the help text box to 11 and the close to 12. However, because the initial open disappears the keyboard tabbing to the next object isnt working properly. Do you have any suggestions? I am building this for users that will not have a mouse.

Thanks!

[sgk]

Hi Katherine,

I'm not sure it would work but perhaps you could use the variable to change the behavior of button 1 so it would toggle between open and close?

That way button 1 is always there, making button 2 obsolete, and you should be able to tab to the text object.

However, I'm a bit hesitant to objects appearing and disappearing in an accessible app.

Regards,

/Sara

[#6]

Thanks Sara for the suggestion. The more I consider the extension and an accessible console, I am more and more leaning to leaving the non-compliant version as is and creating a separate compliant version.

One last question - in the accessible straight tables, a screen reader is suppose to be able to read each cell within the table, right? I will soon be using JAWS screen reader, but am using NDVA in the short term. In NDVA, only the column headers can be read.

Thanks again!

[#7]

Another question. I have been trying to work around this all day. I need to launch a URL to open from a button. The accessibility documentation says to use a macro for this. I was able to successfully do this in desktop. BUT, macros dont work on ajax web clients. Any ideas?

[sgk]

Sounds like a good idea in this case.

The extension is tested with NVDA so I will look into that problem.

What version of QlikView are you running?

/Sara

[sgk]

I'm not a developer and my knowledge about macros in QlikView is extremely limited so I'm afraid I cannot help you out here. Sorry.

/Sara

[jerrysvensson]

Some macros do work in Ajax, altough not in Developer when working in WebVIew mode.

Have you tried it in a published application?

[sgk]

Hi Katherine,

I tried out a simple application with NVDA and it actually read out all of the cells in my accessible straight table as I was moving around in it.

I'm using QV11.20 SR10 and the latest version of NVDA, 2015.3.

/Sara