Trust Center

PortalPilot

Last updated: .

PortalPilot, a full-screen request list for the Jira Service Management customer portal, runs only on Atlassian Forge. It also adds admin pages in Jira settings for Jira admins.

What it stores

PortalPilot keeps its settings and saved filters, never request content. Lists are read from Jira each time.

PortalPilot stores data only in Atlassian Forge hosted storage, which Atlassian provisions per site installation. It has no external database, file store or backup of its own. What it keeps there is configuration: settings, user scopes, field settings, filter permissions and saved filters. These hold account IDs and organization and group names, and saved filters hold their name and criteria.

Retention and deletion

Data kept by PortalPilot, where it lives and for how long
DataWhereRetention
Settings: visibility, export, banner and header link. Visibility lists hold account IDs and organization and group namesAtlassian Forge hosted storage (the customer’s installation)For as long as the app is installed, or until an admin changes it
User scopes, field settings and filter permissions. These hold account IDs and organization and group namesAtlassian Forge hosted storage (the customer’s installation)For as long as the app is installed, or until an admin changes it
Saved filters: name and criteria, kept under the owner’s account ID. Shared and global filters also hold the owner’s display nameAtlassian Forge hosted storage (the customer’s installation)Until the owner deletes the filter, a Jira admin deletes it in Filters management, or the app is uninstalled. When Atlassian reports the owner’s account closed, a private filter is deleted and a shared or global one is anonymised
Favourites and each person’s default viewAtlassian Forge hosted storage (the customer’s installation)Until the person changes them, Atlassian reports the account closed, or the app is uninstalled
The last screen a person left open (view, filters, columns and sort; never search text or custom field values)That person’s browser tab (session storage), for that person onlyAt most 12 hours, and cleared when the tab is closed
A person’s choice of compact or comfortable rowsThat person’s browserUntil the browser’s site data is cleared

PortalPilot keeps no backup or archive of Jira content outside Atlassian. Exports are files a person downloads, holding requests that person can already see in Jira.

Deleting data

  • Delete a saved filter. Its owner can delete it from the “…” menu. Jira admins can delete any saved filter in Filters management. Requests in Jira are never changed or deleted by PortalPilot.
  • Closed Atlassian accounts. A daily scheduled job reports the account IDs PortalPilot has stored to Atlassian’s personal data reporting API, in batches of 90, each account at most once every 7 days. For an account Atlassian reports as closed, PortalPilot deletes that person’s private filters, favourites and default view, removes the account from every user list in Visibility, scopes and filter permissions, and anonymises their shared and global filters to “Former user”. For an updated account it clears the stored owner name. The job logs counts only. See the privacy policy.
  • Uninstall the app. Uninstalling the app removes its access. Atlassian removes the app’s Forge storage under its platform lifecycle, on Atlassian’s schedule; Atlassian documents that hosted storage is retained for 28 days after uninstallation before it is deleted. After uninstall PortalPilot cannot read it. PortalPilot does not itself purge storage at uninstall; the platform does.
  • Data deletion requests. Contact us through the contact page. We will act on a verified request within 30 days. Data held by Atlassian follows Atlassian’s policy.
  • Site deletion. When a Jira site is deleted, Atlassian’s site retention applies to the site and the app’s data; app data is deleted when the site is permanently removed.

Data residency

According to Atlassian’s Forge documentation, Forge hosted storage is data-residency enabled: it is held in the location of the host Atlassian product and moves with it when an administrator migrates the product. PortalPilot sends no data to another location.

Architecture

PortalPilot runs only on the Atlassian Forge platform. There are no Limbus Lab servers or databases: no customer data is processed or stored outside Atlassian infrastructure by PortalPilot.

PortalPilot architecture: the customer’s browser, the customer portal, Atlassian Forge and JiraA customer signed in to the Jira Service Management customer portal opens PortalPilot, a Forge Custom UI page shown in the portal. Through the Forge bridge it asks PortalPilot’s Forge functions for its lists. Inside Atlassian infrastructure, the functions read Jira through the Jira REST API as the signed-in person, never as the app, and read and write PortalPilot’s settings and saved filters in Forge hosted storage. Request content is not stored. There is no server, database or storage operated by Limbus Lab, and no address outside Atlassian.Customer’s browsersigned in to the portalAtlassian infrastructureJSM customer portalPortalPilot (Custom UI)Atlassian ForgePortalPilot Forge functionsForge hosted storagesettings, saved filtersJira Cloudrequests, usersHTTPSForgebridgeJira REST API,as the userread, writeNo Limbus Lab server, database or storage, and no address outside AtlassianPortalPilot architecture: the customer’s browser, the customer portal, Atlassian Forge and JiraA customer signed in to the Jira Service Management customer portal opens PortalPilot, a Forge Custom UI page shown in the portal. Through the Forge bridge it asks PortalPilot’s Forge functions for its lists. Inside Atlassian infrastructure, the functions read Jira through the Jira REST API as the signed-in person, never as the app, and read and write PortalPilot’s settings and saved filters in Forge hosted storage. Request content is not stored. There is no server, database or storage operated by Limbus Lab, and no address outside Atlassian.Customer’s browsersigned in to the portalAtlassian infrastructureJSM customer portalPortalPilot (Custom UI)Atlassian ForgePortalPilot Forge functionsForge hosted storagesettings, saved filtersJira Cloudrequests, usersHTTPSForge bridgeread, writeJira REST API, as the userNo Limbus Lab server, database or storage,and no address outside Atlassian
Figure 1. PortalPilot between the customer’s browser, the customer portal, Atlassian Forge and Jira. A text description of the diagram follows below.

Data flow

  1. A customer signed in to the portal opens Requests and selects the banner button. Forge shows PortalPilot (a Custom UI page) full screen, in that person’s browser.
  2. PortalPilot asks its Forge functions for its lists, counts and settings through the Forge bridge.
  3. The functions read Jira through the Jira REST API as the signed-in person, never as the app. Jira’s permissions and work item security levels decide what comes back, so a customer sees the same requests Jira would show them anyway.
  4. The functions read and write PortalPilot’s own data (settings, user scopes, field settings, filter permissions and saved filters) in Forge hosted storage. Request content is not stored there: lists are read from Jira each time.
  5. Admin pages are for Jira admins only. The functions check this on every call, with the admin’s own permissions; when Jira does not confirm access, the app denies it.
  6. Raise a request opens Jira’s own create form. PortalPilot does not create the request itself, and has no permission to change Jira.

Network diagram

Network connections used by PortalPilot
FromToProtocolAuthenticationNotes
Customer’s browserThe Jira Service Management customer portal, with PortalPilot inside itHTTPSAtlassian user sessionPortalPilot is rendered by Forge inside the portal
PortalPilot pagePortalPilot Forge functionsForge bridge, HTTPSForge, with the signed-in person’s identityAtlassian-managed
PortalPilot Forge functionJira Cloud REST API of the same siteHTTPS, via Forge’s managed clientForge-managed, as the signed-in personNo credentials held by PortalPilot
PortalPilot Forge functionForge hosted storageAtlassian internal, Forge-managedForgePer-installation scope

PortalPilot makes no connection to any non-Atlassian host. Its app manifest lists no outside address (no egress), and there is no PortalPilot-operated server, load balancer, database, queue, analytics service or third-party API in the architecture.

Scopes

The app asks for these permissions and no others. None of them can change Jira.

Jira permissions (scopes) PortalPilot asks for
ScopeUsed for
read:servicedesk-requestReading portal requests, service desks and request types
read:jira-workChecking admin permission and listing fields for Fields configuration
read:organization:jira-service-managementReading organizations for filters and visibility
read:jira-userReading user names and groups
storage:appKeeping settings and saved filters
report:personal-dataAtlassian’s personal data reporting: reporting the account IDs the app stores, and erasing what it stores for closed accounts

Encryption and the browser

The text that applies to every app is in Encryption at Rest. What follows applies to this app only.

PortalPilot reads requests in Jira; it does not copy them. So that a refresh of the portal page opens PortalPilot where the person left it, the browser tab keeps the last screen they had open (view, filters, columns and sort) in session storage for at most 12 hours. Free-text search and custom field values are never kept, and session storage is cleared when the tab is closed. The browser also remembers the person’s choice of compact or comfortable rows. No request content is kept in the browser by PortalPilot. These copies are held on the person’s own device; they are not Forge storage and the platform encryption does not describe them.

PortalPilot stores no API key or other secret.

Logging

The text that applies to every app is in Data Logging and Retention. What follows applies to this app only.

PortalPilot collects no analytics. The Data collection tab in General settings says so; there is nothing to turn on or off. PortalPilot keeps Forge platform logs only.

What a log line contains: each call logs the function name, an outcome code and how long it took, nothing more. Logs hold no request content, names or email addresses, and PortalPilot holds no access tokens, API keys or secrets that could be logged.

Subprocessors

The text that applies to every app is in Subprocessors. What follows applies to this app only.

PortalPilot sends Jira data only to the Jira Cloud APIs of the site it is installed on, and to the browser of the signed-in person. Its only subprocessor is Atlassian (Forge hosting, storage and logs; Jira Cloud): Atlassian runs PortalPilot’s functions, storage and logging and hosts Jira Service Management.

Declared outbound (egress) domains: none. PortalPilot’s app manifest lists no outside address, so Forge does not let it call any host outside Atlassian. All its calls use Forge’s managed Jira clients and Forge storage, which need no declared domain. Forge reported the app as eligible for Runs on Atlassian when it was deployed.

Software dependencies: Atlassian Forge packages, Atlassian’s design system components and React, bundled into the app. CSV and XLSX files are written in the browser by the app’s own code. None is a hosted service and none receives data from PortalPilot over a network.

Security and safeguards

The text that applies to every app is in Security and Incident Response. What follows applies to this app only.

Besides the responsibilities every app has, PortalPilot is responsible for the permission checks in its functions. PortalPilot requests only the Jira permissions (scopes) listed in its Marketplace listing and at installation, declares no outside address, and makes no call to a non-Atlassian host. Fix targets are in Vulnerability Reporting.

Built-in safeguards

  • Reads as the signed-in person. Every list is read from Jira as that person, never as the app, so Jira’s permissions and work item security levels apply. There is no setting to show requests a customer could not otherwise see.
  • No changes to Jira. PortalPilot asks Jira only for permission to read requests, work items, organizations and users, plus its own storage. It has no permission to create, edit or delete requests. Raise a request opens Jira’s own create form.
  • Admin actions checked on the server. Only Jira admins can open the settings, and the server checks this on every call. If Jira cannot confirm access, the app denies it.
  • Fails closed on visibility. When Visibility is limited to selected users and Jira cannot confirm whether a person belongs to an organization or group, access is denied.
  • Hidden fields stay hidden. Fields an admin hides are not listed, their values are not read, and filters on them are dropped.
  • Safe spreadsheets. In CSV exports, cells that start like a spreadsheet formula are made harmless, and XLSX exports hold every cell as text, so opening the file cannot run anything.
  • Limits stated up front. Lists show up to 1,000 matching requests and exports at most 1,000 requests, within the limit an admin sets.

Incidents

PortalPilot follows the incident response plan. For PortalPilot, an incident is any event that degrades or interrupts PortalPilot’s service (PortalPilot or its admin pages fail to load, lists or counts wrong or not shown, export failing), or that puts customer data at risk (suspected unauthorized access, a customer shown requests Jira would not let them see, cross-tenant exposure, data corruption).

PortalPilot severity examples
SeverityExamples
SEV1 CriticalA customer shown requests Jira does not let them see; cross-tenant data exposure; PortalPilot fails to open everywhere
SEV2 MajorExport fails; one view or filter fails to load
SEV3 MinorOne column not sorted as chosen; wrong label in the UI

A fix is verified on a real customer portal and PortalPilot admin page before the incident is closed.

Accessibility

The company statement is in Accessibility Statement. This is PortalPilot’s first review of how accessible its screens are, against WCAG 2.2 Level A and AA, made on 15 November 2026 on the build that became PortalPilot 2.2.0 (commit 3c5a3a8). It is a self-assessment by the PortalPilot team, not an independent audit and not a certification. Of the 55 criteria, 32 are rated Supports, 14 Partially Supports and 9 Not Applicable. No screen reader has been used yet.

The fixes below are in production: PortalPilot 2.2.0, released on 15 November 2026, is built from the evaluated commit 3c5a3a8.

Problems found during this review and fixed

  • Text on brand-coloured buttons, filter chips and the selected segment was too faint in places; it now meets 4.5:1 for text and 3:1 for controls, in light and dark (1.4.3, 1.4.11).
  • Messages are announced. Errors stay until they are dismissed; other messages last 20 seconds and have a Dismiss button (4.1.3, 2.2.1).
  • The search shortcut is Alt+/ instead of the single key /, so it cannot be set off by accident (2.1.4).
  • Dialogs, popovers and the mobile sidebar hold focus while open, close with Escape and return focus to where it was; they close on release, not on press (2.4.3, 2.1.2, 2.5.2).
  • Columns can be reordered with Move left and Move right buttons, without dragging (2.5.7).
  • The full-screen view reflows at 320 px: one column of figures, dialogs that scroll, popovers that stay on screen (1.4.10).
  • Names and states for controls that had none: Views, the sidebar toggle, rows per page, the Starred mark, radio groups and member pickers on the admin pages (4.1.2, 1.1.1).
  • Small targets on the admin pages, such as member remove buttons and sort headers, are now 24 px (2.5.8).
  • The scope name error on the admin pages is now stated in words (3.3.1).

After these fixes the automated scan reports no problem on the 16 customer screens, in light and dark. On the admin pages it still reports the radio inputs and the search box inside a select, listed below.

Known gaps

  • Below 768 px the Columns button is not offered, so columns cannot be chosen on a phone or at 400 % zoom (1.4.10).
  • Some chart colours are under 3:1 against the card. Every slice and bar also shows its label, count and percentage as text (1.4.11).
  • Help and error text on the admin pages, and the filter name hint, are next to their field but not linked to it in the code (1.3.1).
  • The radio inputs on the admin pages are 15 px; their 24 px labels select them (2.5.8).
  • In the admin dialogs, Close comes last in the tab order, and delete confirmations open with focus on Close (2.4.3).
  • Opening a filter popover by keyboard leaves focus on the button that opened it (2.4.3).
  • Plain messages end after 20 seconds and cannot be extended; errors stay (2.2.1).
  • Some long names are cut with an ellipsis; only request summaries show the full text in a tooltip (1.4.12).
  • Tooltips on icon buttons do not show on keyboard focus; the buttons have written names.

If something is hard to use, tell us through the contact page, with the subject “PortalPilot accessibility”. Please name the screen (customer view or an admin page), what you use (for example a screen reader, keyboard only or zoom) and what happened. We reply within 3 business days.

Accessibility Conformance Report (VPAT 2.5, WCAG edition)

Product information
ItemValue
Name of productPortalPilot: Request Filters & Export for JSM, by Limbus Lab
Product version evaluatedPortalPilot 2.2.0 (commit 3c5a3a8, evaluated on a development install before release); first review
Report date15 November 2026
Product descriptionAn Atlassian Forge app for Jira Service Management Cloud. PortalPilot adds a full-screen request list to the customer portal, with filters, saved filters and export, and admin pages for Jira admins.
Contact informationLimbus Lab, through the contact page (limbuslab.com/contact/)
EvaluatorPortalPilot team, self-assessment (automated scan, keyboard walks, measurements, code review, checks inside Jira Service Management by keyboard and by eye; no screen reader)
Applicable standardWCAG 2.2 Level A and Level AA. WCAG 2.1 Level A and AA criteria are a subset of these tables. 4.1.1 Parsing is obsolete in WCAG 2.2 and is not listed. Level AAA, Revised Section 508 and EN 301 549 tables are not included.
VPAT templateVPAT 2.5 (WCAG edition), ITI terminology

Evaluation methods used

This report is a self-assessment that combines the following. It is not an independent audit.

  1. An automated scan with axe-core 4.10.2 (rules for WCAG 2.0, 2.1 and 2.2 Level A and AA) in Chromium, on local previews built from the same source with made-up data: 16 customer screens (Pivot, My requests, All requests, every filter popup, the column picker, View size, More actions, the filter settings drawer, Export, Browse filters, Raise a request and a saved filter) and every admin page, tab and dialog, in light and dark, at 1280 px and 320 px.
  2. Keyboard walks of the customer screens and the admin pages on the same previews: tab order, visible focus, Escape and where focus returns.
  3. Measurements: target size, text and non-text contrast (including the chart colours), reflow at 320 px, text spacing, and a 640 px wide view in place of 200 % zoom.
  4. Checks inside Jira Service Management on a development site, by keyboard and by eye: the banner, the full-screen view, Pivot, the popups, the More actions menu, Raise a request, Export, the filter settings drawer and the column picker.
  5. A review of the portal and admin code, criterion by criterion, for what the tests above do not cover.
  6. The problems found were fixed and the same checks run again on the fixed build, in two rounds.

Not evaluated yet

  • No screen reader (NVDA, JAWS or VoiceOver) has been used on any part of PortalPilot.
  • The scan could not run inside Jira, because the app sits in a frame from another origin. Inside Jira the checks were by keyboard and by eye.
  • The admin pages were not walked inside Jira after the fixes; their results come from the local previews.
  • True browser zoom (200 % and 400 %) was not used; 640 px and 320 px wide views stand in for it.
  • Only Chromium was used; Firefox, Safari, phones and speech input were not tested.

Scope: everything PortalPilot draws, in the customer portal and on its admin pages. Jira’s page chrome, the customer portal itself, navigation, sign-in and the frames that host PortalPilot are provided by Atlassian and are outside PortalPilot’s control.

Terms

  • Supports: the functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: some functionality of the product does not meet the criterion. In this report it is also used where only part of the product was checked; the remarks say which part.
  • Does Not Support: the majority of product functionality does not meet the criterion.
  • Not Applicable: the criterion is not relevant to the product.
  • Not Evaluated: the product has not been evaluated against the criterion.

Table 1: Success criteria, Level A

Success criteria, Level A
CriterionConformance levelRemarks and explanations
1.1.1 Non-text ContentPartially SupportsIcon buttons have written names, decorative icons are hidden from assistive technology, the donut chart is an image with a text summary, and every chart has a data table hidden from sight but available to assistive technology. Fixed during this review: the Starred mark in the sidebar and the loading counts had labels that assistive technology ignores; they now have text (commit fd4255a). Automated scan (axe-core 4.10.2) found no violation on 16 customer screens in light and dark. No screen reader has been used to hear these alternatives.
1.2.1 Audio-only and Video-only (Prerecorded)Not ApplicablePortalPilot contains no audio or video content (from a review of the code).
1.2.2 Captions (Prerecorded)Not ApplicableNo audio or video content.
1.2.3 Audio Description or Media Alternative (Prerecorded)Not ApplicableNo audio or video content.
1.3.1 Info and RelationshipsPartially SupportsTables have header cells and sort state, lists are lists, labels are bound to fields, and the Filter settings choices are a group with a legend. Fixed during this review: the radio groups on the admin pages had no name (commit eb70027); the member pickers had no label (commit eb70027); the Pivot bar list lost its list role (commit 7c81736); the Owner group had a label that was ignored (commits fd4255a and eb70027). After the fixes the scan found no structure or label violation on the customer screens or the admin pages. Still open: help and error text is not linked to its field with aria-describedby on the Atlaskit fields in the admin pages, and the portal name field hint (maximum 36 characters) is not linked either. The admin General settings blocks use a third-level heading directly under the page heading. Not confirmed: how a screen reader reads the tables and groups.
1.3.2 Meaningful SequenceSupportsThe order in the page matches the visual order: sidebar, toggle, main content (header, filters, results, footer), then dialogs and messages. Admin pages follow their visual order. From a review of the code; the keyboard walks on local previews followed the same order.
1.3.3 Sensory CharacteristicsSupportsInstructions name the control or the keys, for example the column hint gives the arrow keys as well as dragging. Fixed during this review: the save bar said to fix the highlighted fields; it now says to fix the fields marked with an error (commit eb70027). No instruction relies on shape, position or sound alone.
1.4.1 Use of ColorPartially SupportsStatus labels always carry text, the current page number and current menu item have a bar or bold text as well as a tint, and an active filter chip shows a clear button. Fixed during this review: the scope name error was shown only by a red border; it now has text (commit eb70027). The selected segment of the Time range and Group by controls now has a solid fill and is also bold and marked as pressed (commit 5b08888). Chart series are told apart by colour; every slice and bar has its label, count and percentage as text, but matching a donut slice to its legend row relies on colour. Not checked by a person who cannot see colour.
1.4.2 Audio ControlNot ApplicableNo audio plays.
2.1.1 KeyboardPartially SupportsNative buttons, links and inputs are used throughout. The More actions menu, the segmented controls and the column chips take arrow keys, and every clickable chart part has a matching legend button. Fixed during this review: the search box in Raise a request took the Left and Right arrows, so the caret could not move (commit fd4255a); columns could be reordered only by dragging or arrow keys, and now have Move left and Move right buttons (commit 2bd91cc). Walked by keyboard on local previews: every popup, dialog and menu on the customer screens, and every admin page (4 to 30 tab stops per page). Not tested: the customer table was not walked by Tab inside Jira, the admin pages were not walked inside Jira, and the Raise a request search fix was checked in code only.
2.1.2 No Keyboard TrapSupportsNo trap was found. Dialogs hold Tab on purpose and close with Escape; popovers and menus close with Escape and return focus to the control that opened them; the full-screen view closes with Escape from inside the frame (commit c9f579a). Checked live inside Jira on a development site: Escape from a popup, the More actions menu, Raise a request, Export, the Filter settings drawer and the full-screen view. Admin dialogs were checked by keyboard on a local preview, not inside Jira.
2.1.4 Character Key ShortcutsSupportsThe only shortcut is Alt+/ , which moves focus to the search box. Fixed during this review: it used to be the single key / , which could not be turned off; it now needs Alt, and the key hint and aria-keyshortcuts say so (commit 76e6194). The change has a unit test; it was not tried inside Jira.
2.2.1 Timing AdjustablePartially SupportsFixed during this review: messages used to close after 4.5 seconds, including errors. Error messages now stay until dismissed, other messages last 20 seconds and have a Dismiss button, and export progress stays until it finishes or is cancelled (commit 4833790). Seen inside Jira: the Link copied message had a Dismiss button and was still showing after 10 seconds. The error message was checked in code only. Rated Partially Supports because plain messages still end after 20 seconds with no way to extend them. No time limit applies to any task.
2.2.2 Pause, Stop, HideSupportsThe only repeating motion is the loading shimmer and the export progress bar, both shown only while something loads or exports; Cancel export is available, and both stop under the reduced-motion setting. From a review of the code; a long export was not timed.
2.3.1 Three Flashes or Below ThresholdSupportsNothing flashes. The animations are short fades and slides and a slow shimmer, and all stop under the reduced-motion setting.
2.4.1 Bypass BlocksSupportsThe customer view has landmarks (navigation, main, search, pagination) and the admin pages have a main region. Jira supplies the page navigation and skip links around the app. From a review of the code.
2.4.2 Page TitledSupportsPortalPilot's frames are titled PortalPilot, and the full-screen view has the same title. The page title that people see in the browser is set by Jira.
2.4.3 Focus OrderPartially SupportsTab order follows the visual order on the customer screens and the admin pages (local keyboard walks), and dialogs move focus in and return it on close. Fixed during this review: focus was lost to the page when a filter chip was cleared, a criterion removed, a Pivot tile chosen or a filter saved (commit fd4255a, and for column chips commit 2bd91cc); the closed mobile sidebar was reachable by Tab and the open one did not manage focus (commit c48b4aa); Escape in the search box dropped focus (commit 76e6194); the page behind a dialog is now inert (commit 52b653a). Still open: in the Atlaskit modals on the admin pages the Close button is last in the tab order and the delete confirmations open with focus on it; opening a non-modal popover by keyboard leaves focus on the opener. Not tested: the admin pages inside Jira.
2.4.4 Link Purpose (In Context)SupportsRequest links read as the request summary or key; the oldest-open tile link reads the key and summary. Request links open in a new tab without a warning, which is advice rather than a requirement. From a review of the code.
2.5.1 Pointer GesturesSupportsNo function needs a multipoint or path-based gesture. Reordering columns by dragging is covered under 2.5.7.
2.5.2 Pointer CancellationSupportsActions run on click. Fixed during this review: pressing the backdrop closed a dialog on the down event, and pressing outside a popover closed it and dropped an unapplied filter draft; both now close only when the press also ends outside (commit 52b653a). Checked by unit tests and code review; not tried inside Jira.
2.5.3 Label in NameSupportsControls with visible text use that text in their name, for example Raise a request, legend and bar rows named with the visible label, and Delete and Rename buttons on the admin pages. No mismatch was found in the code reviewed; speech input was not used.
2.5.4 Motion ActuationNot ApplicableNo motion- or device-sensor-based input.
3.1.1 Language of PageSupportsBoth documents declare their language as English.
3.2.1 On FocusSupportsNo control opens anything or moves focus when it receives focus. Popovers open on click. From a review of the code.
3.2.2 On InputSupportsFilter panels apply only on Update, search runs on Enter, and admin settings change only a preview until Save. Choosing a segment or a select changes the data shown, not the page. From a review of the code.
3.2.6 Consistent HelpSupportsThe optional Help Center link is always at the bottom of the sidebar, in both the list view and Pivot. The admin pages have no help of their own; help for them is on the Jira side.
3.3.1 Error IdentificationSupportsErrors are described in text next to what caused them and marked as alerts. Fixed during this review: a scope name that was too long was shown only by a red border and a disabled button; it now says what is wrong (commit eb70027). Checked by code review and the local preview; the admin pages were not used inside Jira, and no screen reader has been used. Linking the error text to the field is listed under 1.3.1.
3.3.2 Labels or InstructionsSupportsFields have visible labels and limits (for example the filter name allows 1 to 36 characters). The search boxes have a name and the word Search as placeholder, with a search icon. From a review of the code.
3.3.7 Redundant EntrySupportsNo step asks for the same information twice. Raise a request hands over to Jira's own form, and the last screen is restored. From a review of the code.
4.1.2 Name, Role, ValuePartially SupportsFixed during this review: Save filter had no name below 768 px (commit f0b7d8a); admin radio groups and member pickers had no name (commit eb70027); the rows-per-page menu claimed a listbox it did not behave as and is now plain pressed buttons (commit fd4255a); a column chip claimed to be a button and did nothing (commit 2bd91cc); the Views button, sidebar toggle and group titles now say whether they are expanded (commit c48b4aa); the star toggle has one fixed name (commit fd4255a). After the fixes the scan found no name, role or value violation on the customer screens, and none on the admin pages other than the following, which the scan still reports: the small inner search input of the Atlaskit select (a 2.8 by 16 px input inside a 260 by 40 px control). Not confirmed: anything with a screen reader.

Table 2: Success criteria, Level AA

Success criteria, Level AA
CriterionConformance levelRemarks and explanations
1.2.4 Captions (Live)Not ApplicableNo audio or video content.
1.2.5 Audio Description (Prerecorded)Not ApplicableNo audio or video content.
1.3.4 OrientationSupportsNo orientation lock; the layout changes with width only.
1.3.5 Identify Input PurposeNot ApplicableNo field collects information about the user. Fields take filter names, searches and admin settings.
1.4.3 Contrast (Minimum)Partially SupportsFixed during this review: text on brand-coloured buttons was dark on indigo at 2.62:1 in dark mode (commit f0b7d8a); the field name on a set filter chip was 3.60:1 in light mode (commits f0b7d8a and e41e9a4); on an open or hovered chip it was 3.92:1 and is now 5.02:1 in light mode and 4.61:1 in dark. Measured on the local previews of the final build: the scan found no contrast violation on 16 customer screens in light and dark, including every open popup, dialog and drawer. Rows now dim to 80 percent while loading instead of 55 (commit 7c81736). Not decided: the scan could not decide the contrast of some text on the admin pages (6 to 7 items per page, reported as incomplete) and of table cells under open popups. The Atlaskit components were not recomputed.
1.4.4 Resize TextPartially SupportsText sizes are in pixels in the style sheets and the layout reflows, and a 640 px wide viewport (standing in for 200 percent zoom on a 1280 px screen) showed no horizontal page scroll and no clipped text on the customer or admin screens. True browser zoom and text-only zoom were not tested; the browser tool used here rejects zoom.
1.4.5 Images of TextSupportsAll text is real text. The only images are request type icons and the app icon.
1.4.10 ReflowPartially SupportsFixed during this review: the Pivot page scrolled sideways at 320 px (341 px wide) and cut the KPI tile text; it now has one column below 480 px and measures 320 px wide, with no sideways scroll (commit 7c81736). The Raise a request grid, dialogs and bottom-sheet panels now fit and scroll (commit 7c81736). Admin General settings tabs now wrap in two rows instead of cutting their labels (commit eb70027). The popover that ran off the right edge of the full-screen view now shifts inside it (commit 5b08888). Measured at 320 px and 640 px on local previews. Still open: the column picker is hidden below 768 px, so column choice is not offered there while the chosen columns still decide the export; the filter chip row scrolls sideways inside its own bar. At 320 px the Browse filters dialog, saved filters and the column picker were not scanned (the sidebar is a drawer there).
1.4.11 Non-text ContrastPartially SupportsMeasured: input, checkbox and chip borders 3.24:1 in light and 4.2:1 in dark; focus ring 3.5:1 on white and 3.1:1 on a tinted chip. Fixed during this review: a checked checkbox or radio was 2.22:1 in dark mode (commit f0b7d8a); the selected segment was 1.2:1 in light and 1.0:1 in dark and now has a solid fill at 4.31:1 and 5.53:1 (commit 5b08888). Still open: in light mode some chart series are under 3:1 against the card (for example the yellow Waiting series at 1.57:1 and the light blue and light green bar shades), and the dark New series is 2.55:1. Each slice and bar is labelled with text and value, so the information is not lost, but a strict reading of this criterion is not met. Adjacent slices have low contrast with each other (gaps and the legend separate them).
1.4.12 Text SpacingPartially SupportsThe WCAG text-spacing values were applied on local previews and the screens were checked: no clipped or overlapping text on My requests, the column picker, the Export dialog, Pivot or any admin page. Not applied: the other dialogs and popups. The code also truncates some text with an ellipsis or a fixed width (filter names in the sidebar, chip values, request type descriptions, chart labels); only request summaries carry the full text in a tooltip.
1.4.13 Content on Hover or FocusSupportsThere are no custom hover or focus popups. Popovers open on click, close with Escape and stay open while hovered. Icon buttons use the browser's own title tooltip.
2.4.5 Multiple WaysSupportsThe customer view is one screen reached from the banner or a shared link. The admin pages are reachable from Jira's app sidebar, from Get started and from links between pages.
2.4.6 Headings and LabelsSupportsEach view has a heading and dialogs and cards have subheadings. Fixed during this review: the rows-per-page button said only View 25; it now says rows per page (commit fd4255a). From a review of the code.
2.4.7 Focus VisibleSupportsA 2px outline is drawn on every tab stop, measured at 3.5:1 on white. Controls that reset their style add it back; inputs use a 2px blue border. Every stop in the local keyboard walks of the customer and admin screens showed a ring, and it was seen inside Jira on the full-screen view, the dialogs and the column picker.
2.4.11 Focus Not Obscured (Minimum)Partially SupportsDialogs make the page behind them inert, so focus cannot move behind them. Not measured: the messages at the bottom right over the pager, the sticky filter bar and footer below 768 px, and the admin save bar over focused fields. No case of a covered focus ring was seen in the keyboard walks, but that was not tested for.
2.5.7 Dragging MovementsSupportsColumns can be reordered with Move left and Move right buttons on each chip, with arrow keys, or by dragging (commit 2bd91cc). The buttons were seen in the column picker inside Jira. The admin pages have no dragging.
2.5.8 Target Size (Minimum)SupportsMeasured: buttons and icon buttons are 24 px or more. Fixed during this review: the remove buttons on column chips were 18 px and are now 24 px (commit 2bd91cc); the sort headers were 20 px tall and are 24 px (commit eb70027); the member remove buttons on the admin pages were 16 px and the first fix did not take effect, so the rule was changed to match the Atlaskit Tag button (commits 4de39d0 and 3c5a3a8). Measured after the last fix: all member remove buttons are 24 by 24 px and the scan no longer reports them. The scan still reports two kinds of small input, both inside a larger target that does the same thing: the admin radio inputs are 15 px, but each label is a 24 px high target and a click on it selects the radio; the text input inside the select controls is 2.8 by 16 px, but the whole control (260 by 40 px) is the target. A few small targets pass by the spacing exception.
3.1.2 Language of PartsSupportsAll interface text is English. Request summaries and field values come from Jira and are shown as entered.
3.2.3 Consistent NavigationSupportsOne sidebar component is used for the list view and Pivot. Admin navigation is Jira's.
3.2.4 Consistent IdentificationSupportsFixed during this review: the star toggle had two different names in the toolbar and in Browse filters; it is now Favorite followed by the filter name in both (commit fd4255a). Refresh is named Refresh results in the list and Refresh in Pivot, which are different screens.
3.3.3 Error SuggestionSupportsMessages say how to correct the input, for example Use 1 to 36 characters and Enter a link that starts with https://. The scope name error now says what is wrong (commit eb70027).
3.3.4 Error Prevention (Legal, Financial, Data)SupportsDeleting a saved filter or a scope asks first, in a confirmation dialog. Admin drafts stay unsaved until Save and have Discard.
3.3.8 Accessible Authentication (Minimum)Not ApplicablePortalPilot has no sign-in step; people are signed in by Atlassian.
4.1.3 Status MessagesPartially SupportsFixed during this review: each message used to be a new live region that arrived with its content already inside; messages now go into two always-present regions, one status and one alert (commit 4833790). Result counts and the unsaved changes status are kept in permanent live regions (commit fd4255a), and the column reorder says when a chip is already first or last (commit 2bd91cc). Not checked: whether every searchable list (Browse filters, Filtering criteria, Select columns, Raise a request) announces its count. Not heard with a screen reader; the error message was checked in code only.

Table 3: Success criteria, Level AAA

Not evaluated.

Summary of ratings

Number of criteria per conformance level
Conformance levelLevel A (31 criteria)Level AA (24 criteria)
Supports1913
Partially Supports77
Does Not Support00
Not Applicable54
Not Evaluated00

Legal disclaimer: this report describes the version named above as reviewed on the report date. It is a self-assessment; no third-party audit and no screen-reader testing has been performed. The testing is the scan, keyboard walks, measurements and checks inside Jira described under evaluation methods; everything else rests on a review of the code.

AI

PortalPilot’s documents describe no AI feature, and no AI usage statement has been published for it. Its only subprocessor is Atlassian (Forge hosting, storage and logs; Jira Cloud), and its app manifest lists no outside address. The company rules are in the AI Usage Policy.