Document Cloud View SDK - is failing Accessibility test for Screen Readers
Hi
We are developing a Public Sector web site, in the UK. This, like every Public Sector web site in the UK, is governed by Legal enforced requirements for Accessibility (WCAG 2.1 AA standard). This means that all text on the web site must be Accessible via a Screen Reader (e.g. NVDA - the most popular reader, and supported by Adobe).
We tested the Embeded pdf capability of the Document Cloud View SDK (now called the pdf Embed api ?). It was great – just what we wanted – brilliant product. BUT – we then tested with NVDA.
Failure – the Screen Reader cannot see the text based pdf – at all ! Export it to Standard Acrobat Reader, and NVDA ‘sees’ it fine. So there is a bug with the View SDK viewer.
Retested using the Bodea test page at
https://documentcloud.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf
This failed on NVDA – so its easy for Adobe support to check out.
Made a Case - ADB-14021967-Y1N5 – you can see all the testing details there. Support asked me to post this on this forum. NVDA Support team also tested this – they agreed there is a problem with the Adobe View SDK – and they showed me that there is a Hidden Checkbox in the demo page view SDK – that turns off Accessibility for Screen Readers ! (i.e. its not just on the demo page - its part of the View SDK) Very strange, and not what Adobe should be doing ?
Please can you investigate and fix – if the View.SDK is not able to work with Screen Readers, then no Public Sector web sites, in most countries worldwide, will be allowed to use it – not a good thing ? Thanks Andrew
PS - Just to clarify - Adobe Support had phoned me, and told me that the support method on this product is via this Forum - rather than the normal Adobe Support cases - i.e. I am not looking for any assistance from other users on this, but I am providing the info for the Adobe development team, to report a bug. I am a bit confused by this process - surely a bug report should have gone in via the Adobe Support Case, but apparently that is not how it works - the support case has been closed by Adobe (although the bug still exists and development have not been informed), and development now have to hear about the bug from this Forum posting !
