XClose

Accessibility

Menu

Jira accessibility statement

This accessibility statement applies to the Jira application.

Jira is a third-party application run by Atlassian. We want as many people as possible to be able to use this website, which means that you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate the website using just a keyboard
  • navigate the website using speech recognition software
  • listen to most of the website using a screen reader

Due to Jira being a third-party platform some aspects of its accessibility are outside of UCL's immediate control.

There are a number of customisation options for your browser and device that could help you use this website and other websites more effectively. AbilityNet has advice on making your device easier to use if you have a disability.

Feedback and contact information

Please contact us if you have an accessibility query including:

  • If you are experiencing issues with accessing information or using the website
  • If you find an accessibility problem not listed on this statement
  • If you have positive feedback on the accessibility considerations made. 

When you contact UCL's Jira Team, there is a process in place to acknowledge your contact, tell you who is dealing with your query and give you a timescale by which you can expect a reply.

We aim to respond to all contacts within 2 working days.

Reporting accessibility problems with this website

We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG (Web Content Accessibility Guidelines) 2.1 AA standards.

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact us.

Read tips on contacting organisation about inaccessible websites.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

If you are in Northern Ireland and are not happy with how we respond to your complaint, you can contact the Equalities Commission for Northern Ireland who are responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’) in Northern Ireland

Technical information about this website's accessibility 

University College London is committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance Status

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Images across many of the tested pages have no alternate text. They are also using CSS background-image and therefore are not visible in Windows High Contrast mode. Decorative images across the tested pages are not hidden from screen readers and Issue type icons do not have alternate text. This can make navigating the site using either High Contrast mode and/or screen readers tedious for users. The above points fail WCAG 1.1.1 Non-text content (A).

Jira Cloud fails WCAG in the following ways:

  • The information in the tooltips provide extra context for the visible but screen reader users can't access this information.
  • The filter function on the Assignee checkboxes on Agile Board is not made clear to screen readers.
  • Site-wide breadcrumbs are not marked up as a list.
  • Related items are not marked up as lists.
  • The group labels inside menus are not announced by screen readers
  • Some text elements should be marked up as headings
  • The existence of uploaded files, placeholder text and the contextual controls that appear on focus inside the rich text editor fields (such as ‘Description’) are not announced to screen readers.

The above points can make navigating and using the service complicated for users who rely on screen readers. All of the above points fail WCAG 1.3.1 Info and Relationships (A).

More formatting’ and ‘Insert’ sub-menu items in Project Settings – Issue Types and rich text editors do not sit directly below the respective menu items in the source order, and so are not sequential. This can cause users who rely upon screen readers to encounter problems navigating the project settings page.  This fails WCAG 1.3.2 Meaningful Sequence (A)

Links sitewide use colour alone to indicate that they are links. This fails WCAG 1.4.1 Use of Colour (A).

When the estimation feature is enabled in “Backlogs” the Story Points tooltip is distinguished by colour alone. This fails WCAG 1.4.1 Use of Colour (A).

Priority icons site-wide are distinguished by colour alone. This fails WCAG 1.4.1 Use of Colour (A).

A significant number of site-wide and page specific interactive features within Jira Software Cloud are not fully keyboard accessible such as:

  • Site-wide: Tooltips, window splitter, drag and drop
  • Agile Boards: Copy button, priority field combobox, create new version, epic link dropdown, backlog button, linked issues dropdown, add people combobox, roles dropdown, add epic combobox, issues, manage rules modal, board settings link
  • Project Settings: Role combobox, disabled toggle
  • Backlog: Break line click and drag

Additionally a significant number of interactive features within Jira Software Clouds rich text editor fields (such as the ‘Description’ field) toolbar are not fully keyboard accessible such as:

  • Submenu items
  • suggested links
  • emoji buttons and menu
  • contextual controls
  • upload sources
  • add file modal
  • annotate and delete buttons

All of the above can make navigating and using the site extremely difficult and cumbersome to use, if not blocking functionality entirely. All the above points fail WCAG 2.1.1 Keyboard (A).

Jira Software Cloud provides keyboard shortcuts without giving users a way to turn them off or the ability to remap a keystroke. This could cause accidental activation of keyboard shortcuts, impeding the navigation of the site, especially for speech input users. This fails WCAG 2.1.4 Character Key Shortcuts (A).

Whilst most time limits on the site can be extended, notifications are dismissed automatically on the Projects page. This can cause problems for users with disabilities as they aren’t given adequate time to react/interact with the page. This fails WCAG 2.2.1 Timing Adjustable (A).

There are no skip links across all Jira Software Cloud pages and Jira Software Cloud has no core landmark structure. This can make navigating the service slow and cumbersome for some users who rely on screen readers or other assistive technologies. This Fails WCAG 2.4.1 Bypass Blocks (A).

The page <title> settings are the same for the Details, Access, Issue types and Features pages within Project Settings. They are not unique and don't adequately describe the page subject and as such can cause navigating using assistive technologies confusing to users. This fails WCAG 2.4.2 Page Titled (A).

Jira Cloud has the below Focus Order issues:

  •  Focus is not managed properly when opening, while open, and after closing modals.
  •  “Next Gen” graphic is focusable in left sidebar navigation.
  •  Focus of submenus of “Project Settings – Issue Types” page is not managed.
  •  Agile Board Pages: Some buttons and links receive focus twice, show more fields button focus order is not logical, non-interactive share button appears in the focus order, duplicate buttons perform same function.
  •  Backlog page: Focus is not managed on Type filter.
  •  Create project page: Focus is set on an input field when the page loads.
  •  Contextual controls receive focus out of sequence.
  •  Insert menu options are not announced by the screen reader.
  •  Add text colour graphic is focusable.
  •  Focus of submenus are not managed.

This can cause users to encounter information in an inconsistent order, hindering site navigation. The above list fails WCAG 2.4.3 Focus Order (A).

The Agile Board page: the visible label is sufficiently different from the in-code label for the following elements that speech interface users can’t interreact with them directly: “Edit Assignee” button, Preview issue, Create new issue, Issue Type & Description text fields on Project Settings page, Backlog “Create story”. The above hinders site functionality for users who require speech enabled assistive technologies. This fails WCAG 2.5.3 Label in name (A).

Jira Cloud does not announce Errors in the following areas:

  • Create project: Errors displayed on blur are not announced by the screen reader on Invite your team email field.
  • Agile board: Error message is not programmatically associated with its field on Enter name, team or email field validation
  • Project Settings (Issue types): Error generated on Issue Type text field does not have visible error text

This can cause site navigation and functionality to be hindered for users of screen reader technologies. The above points fail WCAG fails WCAG 3.3.1 Error Identification (A).

There are a significant number of instances across Jira Software Cloud of elements without clear labels:

  • Many of the form fields across all tested pages do not have programmatically associated labels
  • Placeholder text is used as a label across many of the tested pages
  • Rich text editors do not have a programmatically associated label
  • Placeholder text is used as a label on the Emoji search field and Paste link/Text to display Input fields

The above can lead to undue confusion or navigation for users accessing the site with the aid of screen readers and/or other assistive technologies. The above points fail WCAG 3.3.2 Labels or Instructions (A).

The name, role and value used in Jira Software Cloud user interface elements are frequently unavailable to assistive technologies via HTML or WAI-ARIA which describe the identity, operation, and state:

  • Aria-label is placed on non-interactive elements site-wide
  • Many buttons and links do not communicate their current state (e.g. sidebar navigation)
  • Incorrect roles are assigned to many interactive elements
  • Many buttons do not have programmatically associated labels
  • Many buttons do not communicate their current state
  • Aria-label is placed on non-interactive elements

All points above will significantly hinder site navigation and functionality for anyone who works with a screen reader and/or other assistive technologies. The above points fail WCAG 4.1.2 Name, Role, Value (A).

The following text elements do not meet minimum contrast requirements:

  • Placeholder text
  • Breadcrumb hover text
  • Light grey text across most pages
  • Set up a customer service desk card text and focus state on Projects page
  • Code snippet numbers
  • Ctrl + Shift + E shortcut
  • Ctrl + Shift + 0 shortcut hover state

These faults can significantly hinder the readability of the site for anyone who suffers from a visual disability. This fails WCAG 1.4.3 Contrast Minimum (AA).

Jira Cloud fails Resize text in the following ways:

  • Text doesn’t resize or respect browser settings.
  • Content overruns, truncates or disappears on many pages when zoomed to 200%

This can hinder the readability of the site for any users with visual impairments. This fails WCAG 1.4.4 Resize text (AA).

Jira Cloud fails Reflow in the following areas:

  • Horizontal scroll bar displayed when content is resized to 400% on some pages
  • The sticky header and footer obscure the main content area when the page is zoomed to 400% on some pages
  • There is loss of content and functionality within rich text editors (such as the ‘Description’ field) when zoom is increased to 400%.

Losing content and its readability at increased zoom values can hinder the use of the service for those with visual impairments or other disabilities where increased screen size is required. This fails WCAG 1.4.10 Reflow (AA).

There is a significant amount of non-text elements that fail minimum contrast across the whole site such as:

  • Icons
  • Focus indicators
  • Form field borders (search fields, checkboxes, buttons)
  • Checkboxes and hover state
  • Next/Previous buttons and pagination in “Choose a template” carousel
  • Drop down options hover / focus state in ”Backlog” page
  • Star buttons and states in “Projects” page
  • Task and Issue Type icons and states in “Agile Board (NG)” page
  • Table sort icon in “Project Settings (People)” page
  • Emoji buttons and hover states
  • Icons and focus states
  • Remove indicator
  • Cell highlighter

All of the above can hinder the readability of the site for anyone with a visual impairment. The above points fail WCAG 1.4.11 Non-text Contrast (AA).

The following areas suffer from poor text spacing:

  • The text inside the Recents project cards is cut off when text spacing is increased on “Projects” page.
  • Content is truncated when text spacing is increased on “Project Settings (People)” page

This is another example of readability being impacted, which can cause navigation/functioning issues for users. This fails WCAG 1.4.12 Text Spacing (AA).

Jira Cloud fails Content on hover or focus in the following areas:

  • Agile board (Classic): The tooltips content that displays when the mouse cursor hovers over the “Time spent” and “Time remaining” disappears when the pointer is moved away from the trigger.
  • On the “Create project” page, the project key popup can't be dismissed without moving the pointer or keyboard focus.
  • On the “Project Settings (Issue Types)” page, the ‘What’s this?’ tooltip can't be dismissed without moving the pointer or keyboard focus.
  • Menu button overlaps content on hover and focus on the “Agile Board (NG)” page
  • Member tooltip remains open and obscures content when focus moves away from the tooltip on “Project Settings (People)” page.
  • Text describing why feature is disabled is only available on hover on “Project Settings (Features)” page.

Lack of control over pop ups can lead to a confusing or unclear user journey when accessing the service. This fails WCAG 1.4.13 Content on Hover or Focus (AA).

There are button labels that are not informative or descriptive, such as:

  • Watchers, Status, Description and Environment buttons on Agile Board (NG & Classic) pages
  • Menu, Group by and Edit board heading buttons on Agile Board (NG) page
  • Star button on “Projects” page

These can lead to confusing user experiences for those who rely on screen readers to navigate sites. This fails WCAG 2.4.6 Headings and Labels (AA).

Jira Cloud does not have visible Focus in the following areas:

  • Focus indicators are not visible in Windows High Contrast mode
  • Child issue interactive element on Agile board (Next Gen) page has no visible focus indicator
  • The files under Recent uploads in the “Add files” modal have no visible focus indicator.

Focus indicators help those who rely on keyboards to navigate sites to visually identify where they are on the page. This fails WCAG 2.4.7 Focus Visible (Level AA).

On the “Invite your team” and “Create a project” pages, when invalid or incomplete data is entered into a text input that has validation, an error is displayed but not announced by the screen reader. The error text also disappears when focus moves away from the field. This will hinder any user relying on a screen reader to help them detect errors. This fails WCAG 3.3.3 Error Suggestion (Level AA)

Jira Cloud fails to announce status messages in the following areas:

  • Loading screens site-wide are not announced by the screen reader
  • Next and previous carousel buttons don't provide feedback to a screen reader on the “What's in this modal: Choose a classic template” page
  • Status messages are either not announced by screen reader or incorrect on the “Agile Boards” page
  • Auto suggestions are not announced by the screen reader on the “Add link” popup in the Rich Text Editor

The above failures can hinder any user who relies on a screen reader from performing work on the service. This fails WCAG 4.1.3 Status Messages (Level AA).

If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Reporting accessibility problems with this website’ section of this statement.

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

Content that’s not within the scope of the accessibility regulations

This section covers issues that we do not need to fix right now. The law calls these exemptions.

Third-party content

Our websites contain third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours to work with the third-party to improve its accessibility. This may include:

  • links to non-UCL websites
  • content/functionality on our website
  • content hosted on other websites, such as social media sites.

To help accessibility compliance across the sector, University College London supports searchBOX , a centralised, independent directory of third-party accessibility information. 

searchBOX catalogues the contact information and accessibility statements of third-party suppliers, enables the sharing of community-generated accessibility statements, and allows users to map their supplier ecosystem. 

Users can access third-party accessibility statements using the free searchBOX Finder service. 

University College London encourages all our partners and suppliers to support this effort by ensuring that their accessibility information is included in the searchBOX directory. 

Our testing processes

We tested the website using a combination of manual and automated checks alongside reference to the existing conformance reports provided by OpenText. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the website owner who will review the issue, make sure it is included in our plan to fix issues and add it into the accessibility statement when it is next updated.

Preparation of this accessibility statement

This statement was prepared on 27th January 2023. It was last reviewed on 17th December 2022.

This website was last tested in April 2020. The test was carried out by Atlassian.

For more information from Atlassian you can find a section on accessibility for their services at the following link Atlassian accessibility

What we’re doing to improve accessibility

UCL are working with Atlassian to fix or provide alternatives for all issues that we are made aware of and as identified by our periodic internal testing and auditing processes. Atlassian are currently working on an updated VPAT for Jira which is expected to published early February 2023.