Noteable - Accessibility Statement for the StatusPage of the Noteable service

⤺ accessibility

Application accessibility statement in line with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018

This accessibility statement applies to the external StatusPage section of the Noteable service hosted at (https://noteable.statuspage.io/). Parallel statements are available for the website, Moodle, and notebook components.

This application is hosted by Atlassian, on behalf of EDINA, for the University of Edinburgh. Our aim is for as many people as possible to be able to use this service. That means you should be able to:

• listen to most of the service using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
• understand the content of the application
• access and use the service without any time limits
• zoom in up to 500% without the text spilling off the screen
• change colours, contrast levels and fonts using your browser settings

Customising the application

AbilityNet has advice on making your device easier to use if you have a disability. This is an external site with suggestions to make your computer more accessible:

AbilityNet - My Computer My Way

With a few simple steps you can customise the appearance of our website using your browser settings to make it easier to read and navigate:

Additional information on how to customise our website appearance

How accessible this application is

We know some parts of this application are not fully accessible:

• some parts may not be fully compatible with screen readers
• sometimes it can be hard to tell where you have navigated to using only the keyboard
• some non-text content does not have text alternatives
• some service features include pop-up windows. User are notified through the cursor changing to a hand-click icon when hovering over links which will open a new tab or window
• there may be some use of All-Caps
• not all colour contrasts meet the recommended Web Content Accessibility Guidelines (WCAG) 2.2 AA standard
• some images may fail colour contrast guidelines if users redefine the colour palette in their browser

Feedback and contact information

If you need information on this website or the Noteable service in a different format such as an accessible PDF, large print, easy read, audio recording or braille:

• email edina@ed.ac.uk
• call us on 0131 650 3302
• British Sign Language (BSL) users can contact us via Contact SCOTLAND BSL, the on-line BSL interpreting service

We will consider your request and get back to you within 5 working days.

Reporting accessibility problems with this application

We are always looking to improve the accessibility of the Noteable service. If you find any problems not listed on this page, or think we're not meeting accessibility requirements:

• email us at edina@ed.ac.uk
• call us on 0131 650 3302
• British Sign Language (BSL) users can contact us via Contact SCOTLAND BSL, the online BSL interpreting service

We will consider your report and get back to you within 5 working days.

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 please contact the Equality Advisory and Support Service (EASS) directly.

Contact details for the Equality Advisory and Support Service (EASS)

The UK government has also produced information on how to report accessibility issues: Reporting an accessibility problem on a public sector website.

Contacting us by phone using British Sign Language

Contact SCOTLAND BSL runs a service for British Sign Language users and all of Scotland's public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates 24 hours a day, 7 days a week.

Technical information about this application's accessibility

EDINA is committed to making its Noteable service accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This application is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard, owing to the non-compliances listed below.

Non accessible content

This external service is known to have compliance issues.

In addition to the accessibility regulations non-compliance listed below, the service uses buttons where the text is in "all-caps"

Non-compliance with the accessibility regulations

The following items to not comply with the WCAG 2.2 AA success criteria:

• 1.1.1 - Non Text Content
  • None of the meaningful icons tested have alternative text
  • Most of the decorative images and icons are not hidden from screen readers
• 1.3.1 - Info and Relationships
  • There are no core landmark structures
  • Some related items are not marked up in lists
  • Some text is styled like a heading and used as a heading, without any identification of being a heading
  • Some data is styled like a table without a table element
  • Some form labels, instructions or hints are not associated to their inputs
  • The heading structure is not semantic or hierarchical
  • Some elements do not conform the the rules of the Role given to them
• 1.3.2 - Meaningful Sequence
  • An instruction is placed after an Update button
• 1.4.1 - Use of Color
  • Charts and calendar displays use colour [from Green "good" to Red "very bad"] to indicate the degree of availability
  • In menus, the "Current tab" is indicated by changing the background colour
• 1.4.3 - Contrast Minimum
  • Text across the service is frequently low contrast
• 1.4.10 - Reflow
  • The pages have a structure that creates a minumum width, thus content can not always be presented in full without requiring scrolling in two dimensions (loss of information or functionality) at extreme magifications or on particularly small displays
• 1.4.11 - Non Text Contrast
  • Icons and form inputs are frequently low contrast
• 1.4.13 - Content on Hover or Focus
  • The "Uptime Tooltip" content is only available on hover but is not hoverable itself or dismissable without moving the cursor
• 2.1.1 - Keyboard
  • Keyboard access ("tabbing") does not work in some administrator forms
  • The pop-up from the "Subscribe" button cannot be accessed using keyboard keys on either MacOS or Windows systems
  • The "Uptime Tooltip" data available for every bar on the graphs cannot be reached via the keyboard
• 2.2.1 - Timing Adjustable
  • Success messages, and some error messages, disappear automatically, and that timeout cannot be adjusted
  • The "Uptime Tooltip" pop-ups appear automatically on hover over a bar in the Operations, and disappear when the focus leaves that bar
• 2.4.1 - Bypass Blocks
  • There is no "Skip to Content" link
  • There is no Landmark structure to the document
  • There is no Heading structure to the document
• 2.4.2 - Page Titled
  • The Pages have Generic, or innacurate, Titles
• 2.4.3 - Focus Order
  • There are occasions where hidden content is included in the tabbing-order, meaning the focus becomes invisible or the user has to navigate a longer that expected path
• 2.4.5 - Multiple Ways
  • There is not complete site map or similar technique to provide alternative options for finding content within the service
• 2.4.7 - Focus Visible
  • Focus indicators are either missing or difficult to see across many pages in the service
• 3.3.1 - Error Identification
  • The admin pages do not inform the user when an error message is presented
• 3.3.2 - Labels or Instructions
  • Some inputs have no labels
  • Some inputs rely on text around the imput for labels and instructions
  • Some inputs do not identify instructions in the document
• 4.1.2 - Name, Role, Value
  • Several web forms are missing their name, role, or value
• 2.4.4 - Link Purpose (In Context)
  • (This Success Criterion asks that links to different places have different text. It is the flip-side to 3.2.4 - "Consistent Identification".)
  • There are two "Privacy Policy" links (same text) which go to different places

The areas that do not meet WCAG 2.2 AA standard are outwith our control and sit with the 3rd party application provided by Atlassian. These issues have been raised with the supplier.

Disproportionate burden

We are not currently claiming that any accessibility problems would be a disproportionate burden to fix.

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

We will continue to address the accessibility issues highlighted, working alongside Atlassian to deliver a solution or suitable workaround. We have shared our accessibility testing results with Atlassian and hope to have a complete solution or significant improvement in place by December 2025.

While we are in the process of resolving these accessibility issues, we will ensure reasonable adjustments are in place to make sure no user is disadvantaged. As changes are made, we will continue to review accessibility and retest the accessibility of this application.

What we're doing to improve accessibility

The Noteable service team will work with Atlassian to address the accessibility issues.

Preparation of this accessibility statement

This statement was prepared on 2nd November 2022. It was last reviewed in December 2024.

Testing

This service was last tested by the Noteable Service team within the Information Services Group directorate. The testing was carried out primarily using a combination of Firefox & Google Chrome browsers on a Linux system; with MacOS (and Safari) and Windows 10 (and Microsoft Edge) also used for comparative purposes, including screen reader compatibility. Lynx was used to test text-only navigation for the main website (but not the notebooks). In particular, the service was tested using Chrome on multiple platforms since it is by far the most popular browser when using a screen reader and the most popular browser when using the Noteable service. Current worldwide usage levels for different screen readers and browsers can be found in the May-June 2021 WebAIM annual survey.

Automated testing

We try to be consistent with automated testing across all components in the Noteable service.

We used a range of toolkits and services to check each page:

• The IBM Equal Access Accessibility Checker is an open source tool for web developers and auditors that utilizes IBM's accessibility rule engine, which detects accessibility issues for web pages and web applications
• The Google Chrome Lighthouse DevTool is an open-source, automated tool for improving the quality of web pages. It has audits for performance, accessibility, best practice, progressive web apps, SEO and more
• The WAVE® Web Accessibility Evaluation Tool from WebAIM is a suite of evaluation tools that helps authors make their web content more accessible to individuals with disabilities
• The Accessibility tree viewer from the Firefox Developer Tools extension

We recognise the limitations of automated testing and we supplemented this with manual testing.

Manual Testing

Basic manual testing is viewing in a variety of browser/Operating System.

Using Windows 10 [Home Edition], We

• visually compared using Firefox, Chrome, and Edge
• tested with NVDA screen reader in Chrome and Edge
• tested with the Windows magnifier tool

Using MacOS X [Big Sur], we

• visually compared with using Firefox, Chrome, and Safari
• tested using the built-in voiceOver screen reader

Using Linux [Linux Mint 22 LTS], we visually compared all pages using Firefox and Chrome, and used Polypane to compare rendering across multiple screen sized simultaniously.

We also tested for the following:

• spellcheck functionality
• scaling using different resolutions from –25% to +500%
• options to customise the interface (magnification, font, background colour et. cetera)
• notice of links to new window or tab when navigating the service
• information conveyed in colour or sound only
• flashing or scrolling text
• time limits

Our findings on these features are summarised above.

Changes since the previous statement

December 2024

Update all review and testing to WCAG 2.2