I am having some problems with the new Adobe Sign interface. If I switch on “Adobe Sign Manage” in the “For Signature” tab, it all works fine – at least, it works until the session times out. A pop-up message appears saying my session has timed out and asks me to click OK to refresh the session. This is where things go wrong.

The Adobe Sign Manage iframe gets blocked with a Chrome sad face page icon on a grey background. The console shows the following error and warning:

Refused to frame 'https://ims-na1.adobelogin.com/' because it violates the following Content Security Policy directive: "frame-src 'self' data: blob: dc-api.adobecontent.io *.echosign.com *.echocdn.com documents.adobe.com *.documents.adobe.com createpdf.acrobat.com/createpdf/api/ *.demdex.net l3.evidon.com www.google.com/recaptcha/ widget.uservoice.com".

The resource https://documentcloud.adobe.com/dc-web-app-dropin/1.7.0_1.10.0/translations-en-GB.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate as value and it is preloaded intentionally.

A few minutes later, it springs back into action again and correctly loads the Adobe Sign Manage screen.

I am using Chrome 69.0.3497.100 on Windows 10.

I met with a customer today who asked for an option, when generating a link to a file for Viewing or Review, that would require users to provide a password before getting access to the document. The customer has a workflow where they post the URL on a website, but want to restrict access to only those people who are furnished an access password. The user would create the password when generating the URL and distribute it independently of the Doc Cloud system.

If you have a similar workflow, please vote for this idea and provide additional information in the comments.

DESCRIPTION:

While not perfect, the free online tool PAVE (https://pave-pdf.org) demonstrates how this process could be lightyears more user-friendly than it is currently – in Acrobat, and other available tools.

It automates as many of the steps as possible, leads the user through the remaining steps that need fixing manually, and leaves out everything else.

Side menu tabs:

1. Tasks (main window)
2. Properties/edit
3. The "Reading Order", "Tags", and "Structure" menus from Acrobat have been simplified to a single "Reading Order" tab.

The workflow could be:

1. Upload file (or send direct from InDesign or Word)
2. Select "Make Accessible" from tools, or automatically prompt on upload (more below).
3. Checks and automatically fixes what it can.
4. "Tasks" dashboard highlights number of issues fixed automatically in green, list expands on click.
5. "Tasks" dashboard lists tasks needing manual fixing, highlighted red (e.g. doc title, language, untagged elements, reading order).
6. Lists items needing manual verifying (e.g. colour contrast)
7. Checked-off items turn green.
8. "Download PDF" button is yellow until all issues are fixed.
9. "Download PDF" pop-up warns about unfixed issues, and those that that have to be verified by a human.

Tagging process:

1. Untagged elements are highlighted with red overlays on a preview.
2. Click a red overlay (or drag a box to group several elements) to open the side "Properties" menu.
3. Set the tag from a single dropdown menu (or mark as "Ignored").
4. In properties: Add Alt text, if applicable.
5. In properties: Tag tables and lists visually, via a simple visual interface.
6. Tagged elements are added to a list in the "Reading Order" tab.

Reading Order process:

1. Open "Reading Order" tab.
2. Filter by tag (e.g. H1, body, artifact...), or text search.
3. Tags are arranged in a list, separated by page.
4. Drag and drop list items to rearrange reading order.
5. List items can be ticked, for bulk actions.
6. Tags can be expanded to view their contents (child elements).
7. Tags or child elements can be deleted, marked as "Ignore", or grouped under a new tag.

Additional features not available in PAVE example:

1. Filter Reading Order list by "Ignored/Artifact" or separate tab (to find elements mistakenly marked as "Ignored").
2. Toggle to highlight "Ignored/Artifact"elements, with its own colour (e.g. yellow).
3. Ability to "Undo" adding tags and rearranging reading order.

NORMALISE ACCESSIBILITY: – check automatically on upload, with an unintrusive alert:

1. "We found *** accessibility issues in this PDF. Would you like to fix them?"
2. Options: "Yes" / "No, this is a print file" / "More information"
3. If yes > opens tool
4. If no > hides alert, and stops showing alerts for that file.
5. If "More info" > displays something like: "Whether this PDF is distributed via your website, or within your business, these issues many limit your potential audience reach, and may expose you to to legal action, depending on local laws."

Also provide an option to turn the automatic checker on or off.

WHY IT IS NEEDED:

Accessibility is everyone's responsibility. In many countries, WCAG and PDF/UA compliance is a legal requirement.

There is a lack of tools that are free, easy to use, and widely-available on all platforms. I've been actively looking for a tool like PAVE for years, and have only recently come across it.

Adobe is an industry leader in content creation.

Acrobat's online document cloud is in a unique position to provide a fast and user-friendly way to make accessibility mainstream, and put a spotlight on the conversation.

Meanwhile, Acrobat Deskop's comprehensive accessibility tools can remain for experts and power-users, for inevitable edge cases.

Available third-party tools either:
- Hide in obscurity, found only by those that actively look for them;
- Remain locked behind prohibitively expensive subscription fees; or
- Require a steep learning curve to learn.

These are huge barriers to accessibility becoming an easy, normal and everyday part of creating digital documents.

Acrobat desktop has a powerful and comprehensive suite of accessibility tools. But even with the Accessibility wizard, Acrobat's accessibility tools are tedious to use, difficult and time-consuming to learn, and often unforgiving of mistakes.

Any steps not doable pre-emptively in InDesign or Word are intimidating and convoluted for beginners to fix.

• Many clients and stakeholders don't want to pay for the extra time accessibility steps currently take.
• Many businesses don't have the time or resources to teach Acrobat's accessibility tools to all their staff, pay subscriptions for expensive third-party tools, or hire external contractors.
• Many freelancers don't have time or resources either.

This learning curve dumps the burden for making everyone else's documents accessible, on the few staff and contractors that already understand its value – like designers, content creators, developers and accessibility experts. This is of course assuming we can convince management to invest in it at all – and not just dump it in the "too hard" pile.

Many more are completely unaware of the existence of accessible PDFs at all, let alone their importance.

For example – I have a university degree in Graphic Design, yet accessible PDFs were not mentioned once in three years of full-time study. I have worked in the design industry for over 10 years.

It was only through self-teaching html that I started learning about accessibility at all. How can I honestly call myself a specialist in communication, when I've been unknowingly ignoring a whole chunk of my target audiences for the last 8 years?

I've already spoken with someone in customer service via phone, but I just wanted to make it very clear that it is simply embarrassing for a company as large as Adobe to have shipped this completely broken update to Sign/Document Cloud. Clearly little to no QA was done with this product as anyone who uses this on a semi-regular basis would see that access to templates had been extremely limited (or simply removed entirely). I have never been this frustrated with Adobe, seriously, this was a MAJOR ***** up on the part of your engineering team, and if another issue this large arrises I will be cancelling my services.