GladstoneGo Accessibility Statement

At Gladstone, we believe that exercise and activity should be made available to, and enjoyed by everyone, everywhere. As we evolve our digital maturity, a large proportion of the leisure industry still relies on outdated legacy software which makes it difficult for operators to be inclusive of all users of technology. We focused our initial development of GladstoneGo to provide focus on the consumer user experience. Whilst we acknowledge that there’s still a lot of work to be done in making it accessible to everyone, regardless of disability, this is our priority for 2023. We’re committed to improving the inclusiveness of our software to ensure that GladstoneGo is accessible to the widest possible audience. 

Accessibility Statement for Gladstone Go

This is an accessibility statement from Gladstone Software Ltd.

Measures to support accessibility

Gladstone Software Ltd takes the following measures to ensure accessibility of Gladstone Go:

  • Provide continual accessibility training for our staff.
  • Assign clear accessibility goals and responsibilities.
  • Employ formal accessibility quality assurance methods.
  • Procured an independent review of the Web App
  • Procured independent training for internal staff including Product Owners, Quality Assurance Testers & Front-End Developers
  • Undertaking a full review of our processes, practices & tools to bake in accessibility requirements and methods

Conformance status

Whilst we are not currently compliant to AA standard; Gladstone are actively working towards full compliance.

Additional Accessibility Considerations

This web app is run by Gladstone Software Ltd. We want as many people as possible to be able to use this web app. For example, that means you should be able to:

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

AbilityNet has advice on making your device easier to use if you have a disability.

Feedback

We welcome your feedback on the accessibility of Gladstone Go. Please let us know if you encounter accessibility barriers on Gladstone Go:

We try to respond to feedback within 10 business days.

Technical Specifications

Accessibility of Gladstone Go relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • CSS

These technologies are relied upon for conformance with the accessibility standards used.

Limitations and Alternatives

Despite our best efforts to ensure accessibility of Gladstone Go, there are some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.

Known limitations for Gladstone Go:

  1. Duplicate Link ID's: Not every id attribute is unique which is required for the Assistive Technology to interact properly. This fails the following WCAG 2.1 success criterion: 4.1.1 Parsing (Level A). We plan to update all links so that they indicate their purpose throughout 2023.

  2. Links: Some links fail to indicate their purpose, usually because either they contain no link text or are not programmatically determined. This fails the following WCAG 2.1 success criterion: 1.1.1 Non-text Content (Level A); 1.3.1 Info and Relationships (Level A); 4.1.2 Name, Role, Value (Level A); 2.4.4 Link Purpose (In Context) (Level A). We plan to update all links so that they programmatically determined and indicate their purpose throughout 2023.

  3. Page structure, Navigation & Focus Points: Some parts of the app do not convey the logical structure of pages in a way that makes it easy for users of assistive technologies to navigate those pages. This fails the WCAG 2.1 success criterion: 2.4.2 Page Titled (Level A); 2.4.3 Focus Order (Level A). We plan to ensure all parts of the app fully convey to assistive technologies the logical structure of pages.

  4. The use of headings throughout the site is inconsistent: some pages skip heading levels and other headings are empty. This fails the WCAG 2.1 success criterion: Success Criteria 2.4.1 Bypass Blocks (Level A). We plan to correct the heading structure throughout 2023.

  5. Bleed through & Tabs: Content which is not visibly present on the screen is receiving focus; this makes it difficult for users who navigate with the keyboard to determine where their focus is, and may be disorienting, particularly for users who rely on audio feedback to navigate. This fails the WCAG 2.1 success criterion: 1.3.1 Info and Relationships (Level A); 2.4.3 Focus Order (Level A); 4.1.2 Name, Role, Value (Level A). We will review the use of AIRIA design patterns and make suitable changes throughout 2023.

  6. The use of buttons across the app is inconsistent some are unlabelled others expand content or are non-descriptive: An unlabelled button is present on the map, which is still detectable to screen reading software, and can be focused by users that navigate solely using the keyboard. This fails the WCAG 2.1 success criterion: 3.3.2 Labels or Instructions – Level A; 4.1.2    Name, Role, Value (Level A); 2.4.6 Headings and Labels (Level AA). We will ensure that all components that are meant to be accessed have a clear label     which indicates its purpose throughout 2023.

  7. Some parts of the website cannot be accessed via the keyboard. This fails the WCAG 2.1 success criterion: 2.1.1 Keyboard (Level A); 2.4.3 Focus Order (Level A). We will work to ensure that all functionality is operable through a keyboard interface throughout 2023.

  8. The date selector user interface components have labels that include text; however, the accessible name does not match the text that is presented visually within the label. This fails the WCAG 2.1 success criterion: 2.5.3 Label in Name (Level A). We plan to correct the label use throughout 2023.

  9. Status & Error Messages: Status and error messages are not conveyed to screen reader users. This fails the WCAG 2.1 success criterion: 4.1.3 Status Messages (Level AA). All error & status messages will be corrected to work with screen readers throughout 2023.

  10. Date Input: The date input was problematic for users that rely on audio feedback to navigate. This fails the WCAG 2.1 success criterion: 1.3.1 Info and Relationships (Level A); 4.1.2 Name, Role, Value (Level A); 2.4.3 Focus Order (Level A). We will correct the date picker throughout 2023.

  11. Some form fields have the same text label and attributes. Making navigation for screen reader difficult. This fails the WCAG 2.1 success criterion: 2.4.6 Headings and Labels (Level AA). Labels will have the correct class and attributes applied throughout 2023.

  12. Content can get truncated when the page is magnified to 200% or the reflow technique is implemented. This fails the WCAG 2.1 success criterion: 1.4.4 Resize text (Level AA); 1.4.10 Reflow (Level AA). Throughout 2023 we will make changes that allow magnification to the required levels to ensure compliance.

 Assessment Approach

Gladstone Software Ltd assessed the accessibility of Gladstone Go by the following approaches:

  • External evaluation

Date

This statement was created on 16 November 2022 

Colorfull-Logo-with-black-text