Accessibility evaluation report 29-08-2024

Result: Passed

Observations:

Image use is limited, with CSS predominantly used for layout.

Images have ALT text as does the main logo.

Other informative images have ALT text.

Result: Failed

Observations:

The podcasts are hosted with a 3rd part podcast hosting specialist. They have no text-based alternative.

The tutorial video has text captions to describe the equivalent steps shown in the tutorial video.

Result: Passed

Observations:

The tutorial video has synchronised text captions to describe the equivalent steps shown in the tutorial video.

Result: Failed

Observations:

The tutorial video has text captions to describe the equivalent steps shown in the tutorial video but does not have a full audio description or descriptive transcript.

Result: Not present

Observations:

The system does not have live audio or video content.

Result: Failed

Observations:

Video content has captions but no audio description.

Result: Passed

Observations:

Relationships are defined programmatically. Semantic markup is appropriately used to designate headings, regions/landmarks, lists etc. ARIA has been used where HTML is not sufficient.

Result: Passed

Observations:

All data is presented in a meaningful and logical sequence as determined by code order.

Result: Passed

Observations:

Instructions do not rely upon shape, size, or visual location and nor do they rely on sound.

Result: Passed

Observations:

System is responsive and works well on different screen sizes and orientations and is not restricted to only portrait or landscape.

Result: Passed

Observations:

Forms have descriptions and labels and input fields that collect certain types of user information have an appropriate autocomplete attribute defined.

Result: Passed

Observations:

Where colour is used, text alternatives and descriptions are used. Colour is not used as the sole method of conveying content or distinguishing visual elements.

Result: Not present

Observations:

The system does not have audio that plays automatically.

Result: Passed

Observations:

Content appeared to have a minimum contrast level of 4.5:1 and in most cases was AAA, with contrast levels of 7.0:1 and above.

Result: Passed

Observations:

The website could be resized as it is delivered using a technology that has commonly-available user agents that support zoom e.g. Google Chrome and the page is readable and functional when the page is zoomed to 200%.

Result: Passed

Observations:

There are no instances where the same visual presentation can be made using text alone, and an image is used to present that text.

Result: Passed

Observations:

No loss of content or functionality occurs, and horizontal scrolling is avoided, when content is presented at a width of 320 pixels.

Result: Passed

Observations:

All icons and graphics had suitable contrast ratios where system controlled with the remainder being determined by the user agent default state, for example, some focus states.

Result: Passed

Observations:

Checked by increasing font size in Chrome and Edge. Used a web-developer toolbar plugin (http://chrispederick.com/work/web-developer/chrome/) to modify text and line heights to simulate when the user adapts paragraph spacing to 2 times the font size, text line height/spacing to 1.5 times the font size, word spacing to .16 times the font size, and letter spacing to .12 times the font size.

Result: Passed

Observations:

Hovers are identified as ARIA tooltips and dismiss as focus is lost. Modals are focussed and can be closed using navigation buttons.

Result: Passed

Observations:

Tab control works well and is in logical order. The HTML5 <modal> tag has been used, and where there are extra context menus that can be accessed by keyboard for what appears as 'hover' text, the context menu expands these into a readable layer.

Result: Passed

Observations:

Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements using only a keyboard.

Result: Not present

Observations:

No keyboard shortcuts are used.

Result: Not present

Observations:

No content has a time limit.

Result: Passed

Observations:

The slide shows have appropriate controls to stop and start them. These are themselves accessible.

Result: Passed

Observations:

'Loading' animations do not animate more than three times in a one second period, and the animation plays through a limited number (3) times.

Result: Passed

Observations:

No 'Skip' link presented but pages do have ARIA regions used to identify regions of a page and proper use of headings or regions/landmarks is sufficient to meet this success criterion.

Result: Passed

Observations:

Titles have the key page content / topic listed before the system name and are clear and informative.

Result: Passed

Observations:

Focus order works well and the navigation order of links, form controls, etc. is logical and intuitive, even extending to the modal layers.

Result: Failed

Observations:

The purpose of each link can be determined from the link text alone. As the website is mostly delivered on single page, on that page there are links to "Find out more" and "Arrange a demo". As there is only one contact form, these links go to the same place and are adjacent but the purpose of the link, made clear in the text, is different (when read in context) and therefore need to lead to the same form where different contact options can be selected.

Result: Passed

Observations:

All major site features are accessible via a consistent main navigation and sub-navigation and the site is essentially one distinct page, but multiple links to content are provided.

Result: Passed

Observations:

Headings are present and clear. Labels are provided for forms and tables and all relevant form items.

Result: Passed

Observations:

There is a visible indicator for page elements when they receive keyboard focus which appeared to be handled by user agent.

Result: Not present

Result: Not present

Result: Passed

Observations:

Where links and buttons present with ARIA names, the text in the link is also presented in the ARIA version and is expanded upon or clarified to make sense even out of context.

Result: Not present

Result: Passed

Observations:

The language attribute has been added to each page.

Result: Not present

Observations:

All page content is in the default language ("en") defined in the page language attribute.

Result: Passed

Observations:

Although some elements change content, context is not changed and it does not result in a substantial change to the page that could confuse or disorient the user.

Result: Passed

Observations:

When a user inputs information or interacts with a control, it does not result in a substantial change to the page. Some form elements sanitise 'on-the-fly' and some elements, such as choosing certain options on the contact form, make other elements required - these are announced to the user either via modal, or by a status announcement.

Result: Passed

Observations:

The navigation is presented consistently. Tab navigation is correctly marked-up.

Result: Passed

Observations:

Naming is consistent for elements visible on multiple pages.

Result: Passed

Observations:

Visually errors are highlighted, but all errors appear in a modal with a description of the error and its context.

Result: Passed

Observations:

Instructions are provided on each screen and labels identify each input.

Result: Passed

Observations:

Incomplete or missing data has suggested fixes, particularly where validation requires two or more fields to be in complimentary states.

Result: Not present

Observations:

There is no data of this type on the site and the user is not permitted to edit or delete any data.

Result: Not checked

Observations:

NOTE: This success criterion is no longer useful and as of 2023 has been removed from WCAG. It previously required that significant HTML validation/parsing errors be avoided.

Result: Passed

Observations:

Markup is used in a way that facilitates accessibility. This includes following the HTML specifications. Strong use of aria-labelledby and aria-label (where HTML element does not have a specific label that it could be associated with).

Result: Passed

Observations:

The contact form uses a live region announcement where the choosing of an option causes another field to become mandatory.