Tableau accessibility statement

This accessibility statement applies to Tableau.

Tableau (https://tableau.ucl.ac.uk/) is run by University College London (UCL).

Tableau is a third-party platform. Please see the third-party section of this statement for more information.

The Tableau Platform enables individuals to drive change in their organizations by leveraging the power of human visual perception to help people understand data. Once a Tableau author reaches understanding and insights via the cycle of visual analysis and is ready to communicate to a broad audience, they can publish the resulting dashboards or views to either Tableau Server, Tableau Online, or Tableau Public. This statement focuses on dashboards and views published to Tableau Server or Tableau Online and accessed by an account with Viewer permissions and that are embedded in an accessible web page (e.g., "embedded Dashboards and Views").

The content on this website is designed for everyone to find, read, and understand. Where we have identified issues with the website's accessibility or compatibility with assistive technologies they are listed in this statement.

View the site your way

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 provide 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 us, there is a process in place that will acknowledge your contact, tell you who is dealing with it and give you a timescale by which you can expect a reply.

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

Alternative formats

We've designed our content to be as accessible as possible. If you experience barriers, you can request alternative formats. For more information, please contact us.

Reporting accessibility problems with this website

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 to register your difficulty. This helps us improve our systems. 

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).

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 version (WCAG) 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG 2.2 AA standards.

Some parts of the website may not work for everyone. Below are known issues that we either need to fix, cannot fix, or do not need to fix right now. If you find something that we missed, please contact us.

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

Non-compliance with the accessibility regulations

This section covers issues that we need to fix and are working to do so.

Tableau Online and Server v2021.3 Viewer access of Dashboards and Views (Based on VPAT® Version 2.4)

Success Criterion	Conformance Level	Remarks
1.1.1 Non-text Content (Level A)	Partially Supports	Scenario 1: Sign in Tableau Logo's text alternative included more information than visually shown
1.3.2 Meaningful Sequence (Level A)	Partially Supports	Scenario 2: Search dropdown results will be very difficult or impossible for screen reader users Screen Reader users are notified of search results, but will have difficulty navigating to them Scenario 3: Custom Views dialog does not support a natural read order
1.4.1 Use of Colour (Level A)	Partially Supports	Scenario 3: Time zone and Manage Subscriptions aren't visually displayed as a link until it has mouse or keyboard focus Scenario 4: Buttons under Select your file format use colour alone to explain when the element can be clicked, on hover
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	Scenario 1: Reset Password and New Password (Tableau Online only process) footer text does not meet colour contrast requirements Reset Password and New Password (Tableau Online only process) Orange on white buttons do not meet colour contrast requirements Reset Password Green on light green message does not meet colour contrast requirements Login page footer does not meet colour contrast requirements Scenario 3: time zone keyboard focus state does not meet colour contrast requirements
1.4.10 Reflow (Level AA 2.1 only)	Partially Supports	Scenario 2: Tableau navigation bar and toolbar do not support reflow
1.4.11 Non-text Contrast (Level AA 2.1 only)	Partially Supports	Scenario 2: My Account & Settings Menu, Favourites menu and help menu hover and focus states do not meet colour contrast requirements Scenario 3: Weekday buttons active states do not meet colour contrast requirements Share With People keyboard focus state do not meet colour contrast requirements Scenario 4: Buttons under Select your file format do not meet colour contrast requirements, on hover Blue Download button hover state transition does not meet colour contrast requirements Scenario 5: Comment x delete button hover state does not meet colour contrast requirements
1.4.12 Text Spacing (Level AA 2.1 only)	Partially Supports	Scenario 3: Tableau Toolbar does not support the user's choice in text spacing
1.4.13 Content on Hover or Focus (Level AA 2.1 only)	Partially Supports	Scenario 2: Tooltips are not hoverable
2.1.1 Keyboard (Level A)	Partially Supports	Scenario 1: Reset Password and New Password (Tableau Online only process) Language control is not keyboard accessible Email input text delete X control is not accessible via keyboard Show Password (eyeball) button does not receive keyboard focus Scenario 2: Notifications Mark all as read and Settings do not get keyboard focus When using NVDA and typing the word access the focus jumps to the results immediately after typing in the letter a Scenario 3: Tabbing through top level but Tableau Toolbar being a single tab feels very inconsistent Scenario 5: Activating an Alert closes the Alert flyout Cancel / Delete of a comment has a non-traditional keyboard support
2.2.1 Timing Adjustable (Level A)	Partially Supports	Scenario 2: Alerts display only for a short time
2.4.1 Bypass Blocks (Level A)	Partially Supports	Scenario 2: Skip to content link does not appear to skip to the content with screen reader running
2.4.3 Focus Order (Level A)	Partially Supports	Scenario 2: Notifications menu does not announce expanded state Make this my start page confirmation dialog last in tab order When you activate Notifications keyboard focus moves off the page and recovers within the browser window Scenario 3: If a Tableau Toolbar dialog is open and focus is placed in the browser address bar focus does not return to the Dialog Keyboard focus returns to the Subscribe button instead of moving to alert confirmation message close button Scenario 4: Forcing focus to the Address bar does not reset the focus of the Tableau application
2.4.4 Link Purpose (In Context) (Level A)	Partially Supports	Scenario 1: Reset Password and New Password (Tableau Online only process) Tableau logos doesn't explain where the link will take the user
3.3.1 Error Identification (Level A)	Partially Supports	Scenario 1: Reset Password and New Password (Tableau Online only process) errors on edits are not associated with the control Error re password has previously been used not announced automatically by screen reader
3.3.2 Labels or Instructions (Level A)	Partially Supports	Scenario 1: Sign-in editboxes lack visual indication that they are required fields Scenario 2: Favourited state not announced clearly Scenario 3: Custom Views - Name this view clear element is unlabelled and unactionable for screen reader users Screen readers announce On daily controls as toggleable but does not announce that one is required
4.1.1 Parsing (Level A)	Partially Supports	Scenario 3: Share View - Share with people control doesn't have all required children
4.1.2 Name, Role, Value (Level A)	Partially Supports	Scenario 1: Reset password and New Password (Tableau Online only process) - menu doesn't follow aria roles for menu controls Reset Password and New Password (Tableau Online only process) edit boxes do not explain required or invalid - programmatically Reset Password and New Password (Tableau Online only process) Confirmation text isn't read by screen readers Scenario 2: Favourites menu results No Matching Results message not announced Scenario 3: Share View using an aria-placeholder which is not a valid ARIA attribute on a role="combobox" Subscribe dialog Schedule text updates without an announcement to screen readers users Subscribe dropdown lists have a stutter effect if modified without opening Share dialog Share with people as the user types the list of options is narrowed but not explained via the screen reader Scenario 4: Specific Sheet from this workbook options do not have proper labels so VoiceOver does not announce them properly Scenario 5: Add a Snapshot take a bit of time; visual indication of progress is not announced by screen readers

Tableau Server, Tableau Online and Tableau Public v2021.3 Embedded Dashboards and Views (Based on VPAT® Version 2.4)

Success Criterion	Conformance Level	Remarks
1.3.1 Info and Relationships (Level A)	Partially Supports	Scenario 1: View Data Window data table has good column headers but does not support row headers Scenario 6: Parameter controls table is not formatted to match others on the page - uses some rows as visual headers
1.3.2 Meaningful Sequence (Level A)	Partially Supports	Scenario 1: Screen reader order does not match visual flow Scenario 8: Single and Multiple Value Dropdown over communicate as the user wraps within the list of options Scenario 9: Data Highlighter options are unreadable by a screen reader
1.4.1 Use of Colour (Level A)	Partially Supports	Scenario 5: Buttons under Select your file format use colour alone to explain when the element can be clicked, on hover
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	Scenario 6: Tableau's use of orange text on a white background does not meet colour contrast requirements
1.4.10 Reflow (Level AA 2.1 only)	Partially Supports	Scenario 5: Tableau Toolbar removes Redo and Full Screen when compressed
1.4.11 Non-text Contrast (Level AA 2.1 only)	Partially Supports	Scenario 2: Filter Context Menu options focus state has insufficient colour contrast Show Quick Filter Context Menu and Only Relevant Values Menu hover state does not meet colour contrast requirements Scenario 3: Legends' selection highlight colour does not meet colour contrast requirements for UI Scenario 5: Close buttons for Toolbar dialogs focus state does not have enough contrast Share edit boxes keyboard focus state don't have enough contrast Download dialog buttons keyboard focus state doesn't have enough contrast Download dialog buttons hover state doesn't have enough contrast Download button hover state doesn't have enough contrast Download PDF dropdown hover state doesn't have enough contrast Scenario 7: Type-In string input field's visible focus does not meet colour contrast requirements for UI
1.4.12 Text Spacing (Level AA 2.1 only)	Partially Supports	Scenario 1: Embed does not respect user's choice in text spacing
1.4.13 Content on Hover or Focus (Level AA 2.1 only)	Partially Supports	Scenario 2: All Values in Database / Only Relevant Values tooltip is not hoverable
2.1.1 Keyboard (Level A)	Partially Supports	Scenario 2: Cannot ESC to close Select Academic Division if the list has no items Scenario 4: Select Academic Division combo box list does not loop/wrap from bottom back to top with search results Scenario 5: Combo boxes in Download PDF do not loop/wrap Scenario 6: Orange back to top arrow jump links, that appear when zoomed past 150%, are not accessible via keyboard Responsive UI, orange back to top arrows don't have a keyboard equivalent No Documented Keyboard help for Relative Date Filter Scenario 7: Compact List Parameter Controls has a slightly different keyboard behaviour than Single/Multiple Value Filters/Set Controls Scenario 8: Single and Multiple Value List, with Search or Cancel/Apply activated, do not retain focus Scenario 9: Data Highlighter has 2 tab stops Data Highlighter is the only Tableau control tested that doesn't wrap focus within its list Scenario 10: Relative Date Filter visually shows a tab control but are individual actionable elements Relative Date Filter - Esc is not equal to cancel
2.4.2 Page Titled (Level A)	Partially Supports	Scenario 8: Unable to create unique programmatic iframe titles when multiple Tableau Dashboards are embedded on a single page
2.4.3 Focus Order (Level A)	Partially Supports	Scenario 5: Cancelling a Download sub-dialog does not return focus to the Download dialog Scenario 6: Back to Top feature does not place screen reader focus at the top of the page Scenario 8: Focus is not managed after All Set Values is activated Scenario 9: Data Highlighter has 2 visible focuses Scenario 10: Relative Date Filter does not always trap focus for a selection
2.4.7 Focus Visible (Level AA)	Partially Supports	Scenario 1: No visual focus on the Help image link No visual focus on text button Show Instructions for Using This Dashboard or Return to Dashboard
2.5.3 Label in Name (Level A 2.1 only) Does not apply	Partially Supports	Scenario 2: Filter's programmatic names start with "Filter" rather than their visual label
3.2.1 On Focus (Level A)	Partially Supports	Scenario 5: Tableau Public button does not indicate it will launch a new browser window Scenario 9: Text is cleared by Tabbing out of input field without activating delete x button
3.2.4 Consistent Identification (Level AA)	Supports	Components that have similar functionality are visually and functionally consistent
3.3.1 Error Identification (Level A)	Partially Supports	Scenario 7: Parameter controls detect data entry errors, but does not provide error message
3.3.2 Labels or Instructions (Level A)	Partially Supports	Scenario 2: Show Quick Filter Context Menu, All Values in Database, and Select All buttons do not explain which Filter they are associated to Single & Multi Value Filter names are not always announced Labels for controls shouldn't change based on value Filter and List Set controls options lack labels Scenario 7: Type-In Parameter (Date and Time) Control relies on visuals to explain days of the week Revert button is unlabelled Parameter Slider Control sub-elements lack textual programmatic name (-/+ rather than decrease/increase) Accessibility Test Dashboard has an alert without an accessible name Scenario 8: Show Quick Set Context Menu, Click to Include All Set Values, and Search buttons do not explain which Set Control they are associated to Single and Multiple Value Dropdown edit is unlabelled Single Value Dropdown Set controls aria roles aren't correct
4.1.1 Parsing (Level A)	Partially Supports	Scenario 2: Filter and Set controls required ARIA child role not present Scenario 4: When open Filter and Set controls dropdown have listbox controls without names
4.1.2 Name, Role, Value (Level A)	Partially Supports	Scenario 2: Strikethrough state should be communicated to screen reader users Empty visual should be described to screen reader users Filter and Set Controls are seen as individual application Scenario 3: Highlighting Selected Items is not announced via the screen reader Scenario 4: Select Academic Division checkbox use input element but do not have label element Scenario 7: Parameter Slider Control announce a value that is off by one Parameter Slider Control decrease/increase buttons don't announce the change in value when activated Type-In Parameter Controls that auto correct do not announce their change Type-In Parameter Controls with Min/Max values rely on authors to explain Screen readers do not announce set values after pressing Enter for Type-In inputs Tableau processing should be exposed through more than just the mouse cursor Scenario 8: Single and Multiple Value Dropdown incorrectly announced its prior value before announcing the current selection When (All) has keyboard focus Filters do not announce their programmatic names Set controls announced as Filters Scenario 9: Data Highlighter expanded/collapsed state is not explained to screen readers Data Highlighter Search results are not announced by screen readers Scenario 10: Relative Date Filter - Years/Quarters/Months/Weeks/Days incorrectly described as toggle buttons

Disproportionate burden

This section covers issues that we cannot fix right now. We've assessed the cost of fixing these issues but believe that doing so would be a disproportionate burden within the meaning of the law.

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 website contains 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.

For further information please see Tableau accessibility page.

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. 

What we're doing to improve accessibility

We are working with the Tableau to ensure full compliance with accessibility regulations.

Equal Entry LLC, a third-party accessibility consultant, worked with Tableau to define a set of User Scenarios to assess Tableau Online and Server v2021.3 Viewer access of Dashboards and Views.

Tableau has created a Community Forum FAQ: Accessibility to gather all accessibility authoring best practices. This assessment was done against a dashboard published to Tableau Online that had been specifically created using these best practices. Results are reflective of a dashboard or view published to Tableau Server.

Tableau reviewed the detailed issue list, prioritized, and fix several items.

Preparation of this accessibility statement

This statement was prepared on 25 February 2022. It was last reviewed on 25 February 2022. This website was last tested on 14 September 2021. The test was carried out by Equal Entry LLC (www.equalentry.com) on behalf of Tableau.