Apwide Golive runs inside Jira Cloud and follows Jira's light and dark themes. We test it against WCAG 2.2 level AA and publish an Accessibility Conformance Report (VPAT® 2.5 INT) on our Trust Center.
This first evaluation (November 2026) found barriers that we are working on; they are listed below with ways to work around them.
Accessibility features
-
Light and dark themes. Golive follows the theme you choose in Jira (Personal settings > Theme) and uses the Atlassian colour tokens. Text meets 4.5:1 contrast in both themes, except placeholder text in some fields.
-
Text and names. Statuses and categories show their name next to their colour. Most buttons and icons have names that screen readers announce.
-
Zoom and text spacing. All content and functions are available at 200% zoom, and with larger line, letter and word spacing.
-
Errors. Form errors are written in text and say how to correct the input, for example "Name cannot be empty".
-
Confirmations. Deleting an environment, application, status or view asks for confirmation.
-
No time limits. Golive sets no time limit on reading or input.
Compatibility
-
Browsers: the browsers supported by Jira Cloud. Tested with Chrome and Firefox.
-
Assistive technologies: not yet tested with screen readers, speech recognition or switch access.
Known limitations and alternatives
-
Keyboard focus is hard to see on buttons. Links and fields show where the keyboard focus is; buttons do not yet.
-
Some menus need a mouse. The layout menu of a view (List, Matrix, Detail) and the action menu of an environment (Clone, Delete, permission scheme) cannot yet be used with the keyboard.
-
The timeline needs a mouse. Creating, opening and moving events on the timeline is not yet possible with the keyboard. Event dates can be changed in the event dialog instead of by dragging.
-
Selection fields. Fields where you pick a value from a list (application, category, version, status, colour) are not yet announced by name and may lose keyboard focus when you choose a value. Pick the value with the mouse, or check the value shown after choosing.
-
Dialogs. When a dialog opens, keyboard focus may stay on the page behind it. Press Tab or Shift+Tab until you reach the dialog; screen reader users find the dialog's content at the end of the page.
-
Messages are not announced. Errors and success messages are shown as text but not announced by screen readers. After saving, read the form again to find them.
-
Small screens. At a width of 320 px, page headers need horizontal scrolling.
Feedback
Tell us about accessibility problems or ask for help through the Apwide Customer Portal.