The short answer
Atlassian Enterprise Certified (AEC) rule 4.1 needs a publicly available VPAT for each app, and the document has to indicate the app’s key. Atlassian sets no minimum accessibility score, and testing can be manual. Title the document like this:
VPAT - Acme Checklists for Jira (com.acme.jira.checklists)What Atlassian’s rule says
Rule 4.1, from the AEC requirements page:
“The app has a Voluntary Product Accessibility Template (VPAT) publicly available.”
“Accessibility testing can be automated or performed manually.”
“No mandatory accessibility level is required.”
Atlassian Enterprise Certified Program, requirement 4.1
The required document is listed as “VPAT …”, marked “Must indicate applicable app key”. The same page explains what that means:
“Documents which indicate "Must indicate applicable app key" may do so by including the verbatim app key in the document name after the required substring, optionally wrapped in parentheses. For example, for VPATs,
Atlassian Enterprise Certified Program, Required DocumentationVPAT - for (com.contoso.app1)would be accepted as an app-specific title.”
Atlassian checks this automatically. Its trust center scan pattern-matches document titles, card titles and custom control titles, so the wording of the title matters more than you might expect.
Deadline
Atlassian’s announcement on October 1, 2026:
“Cloud Fortified is no longer accepting new submissions.”
“Existing Cloud Fortified badges will remain active and visible on the Marketplace through December 31, 2026.”
Introducing Atlassian Enterprise Certified (AEC), Atlassian Developer Community
If you want to keep a trust badge on your listing in 2027, the VPAT is one of the documents to have ready.
Exact title format, and the mistakes that fail the scan
- Start with “VPAT”. The scan looks for the required word at the start of the title.
- Copy the app key verbatim. Same case, same dots, exactly as on your Marketplace listing.
- Put the key in the title, not only the description. In the developer community thread, an app maker reported that “app keys in the entry’s description are not recognised”. Atlassian staff later said an update should handle descriptions, but the title is the safe choice.
- One document per app. It is the format that is certain to match.
Where to publish it
AEC rule 3.1 asks for a public trust center linked from your Marketplace listing. Atlassian lists these supported providers: Vanta, Safebase, Drata, Sprinto, TrustShare, Comp AI, Conveyor, Delve, Scrut Automation, SecureFrame, TrustCloud, UpGuard, AuditBoard, OneTrust, Thoropass, Whistic. Trust centers not on the list can request a manual review by Atlassian.
- Upload the VPAT to your trust center and use the exact title as the document or card title.
- Make sure the trust center link is filled in on your Marketplace listing.
- The file can sit behind an NDA or request button. Atlassian’s note on rule 4.1 says “This can be protected by an NDA or a password.” The titled entry should still be visible.
How to make it
- Open VPAT Draft Desk and answer Yes to “Is this VPAT for an Atlassian Marketplace app applying for Atlassian Enterprise Certified (AEC)?”
- Enter your app name and app key. The key is checked as you type, and wrapping parentheses are removed for you.
- Answer the plain-language questions for each WCAG success criterion honestly, with short remarks where something is only partly supported.
- Download the PDF and Word files, already named
VPAT - App Name (app.key), and upload the PDF to your trust center.
Your report is titled and named the way Atlassian’s rule 4.1 example shows, from your own answers.
Start your AEC VPATSelling several apps?
Make one VPAT per app. After your first one, your download page shows a code for 30% off each additional app.
Honest limits
- The report is self-reported: it is built from your answers, not from a third-party audit, and VPAT Draft Desk does not test your app.
- It covers rule 4.1 only. AEC has other requirements, such as security testing, certifications and a trust center, that this doesn’t address.
- Atlassian decides whether your app is approved for the badge.
Questions app makers ask
Does Atlassian require a particular VPAT version or score?
No. Rule 4.1 says no mandatory accessibility level is required, and testing can be automated or performed manually. Atlassian’s page doesn’t name a VPAT edition, so use the current ITI template (VPAT 2.5, WCAG edition).
What exactly should the document title be?
Start with VPAT, then the app name, then the verbatim app key in parentheses: VPAT - App Name (app.key). For example: VPAT - Acme Checklists for Jira (com.acme.jira.checklists).
Where do I find my app key?
In your app’s Marketplace listing management page, or in manifest.yml (app.connect.key) for apps that moved over from Connect. App keys use letters, numbers, dots, hyphens and underscores, up to 64 characters.
Can one VPAT cover several apps?
Atlassian says a document may specify multiple app keys, but doesn’t show how to separate them. One VPAT per app is the safest choice, and it keeps customer-facing titles readable.
Can the VPAT be behind an NDA or password?
Yes. Atlassian’s validation note for rule 4.1 says: “This can be protected by an NDA or a password.” The titled entry should still be visible in your trust center.
My scan still fails 4.1. What should I check?
Check that the title begins with VPAT, the app key is copied verbatim (same case and dots), the key is in the title rather than only the description, and the document is visible on the trust center linked from your listing. If it still fails, leave a comment on your ECOHELP onboarding request, as Atlassian staff suggested in the developer community thread.
Do I need an accessibility audit firm?
Not for rule 4.1 itself. Atlassian sets no minimum level and accepts manual testing, so an honest self-assessment meets the rule. Some enterprise customers may still ask for a third-party audit.
When does Cloud Fortified end?
Existing Cloud Fortified badges stay active and visible on the Marketplace through December 31, 2026.
Is the AEC program open to Connect apps?
Atlassian says the program is open to all Forge cloud apps, and rule 1.4 requires that the app does not use any Connect modules.
Last checked 10 October 2026 against the Atlassian Enterprise Certified Program page (last updated October 1, 2026, version 1.04) and the AEC announcement thread. VPAT Draft Desk is not affiliated with Atlassian.
New to VPATs? Start with What is a VPAT?
Selling on Salesforce too? See the accessibility report for Salesforce AppExchange apps.