Accessibility evaluation report 28-07-2023

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: 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: 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: 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. Where this has not been possible, for example in showing fields that are mandatory for data entry, then text has been provided as part of the label to indicate if the data is optional or required.

Result: Passed

Observations:

All data is presented in a meaningful sequence, with correct heading levels and table and form definitions.

Result: Passed

Observations:

All items have multiple means to be understood. The slideshows are text-based and accessible to screen readers.

Result: Passed

Observations:

System is responsive and works well on different screen sizes and orientations.

Result: Passed

Observations:

Forms have descriptions and labels. Form fields are clearly marked and ARIA labels provided where the form field cannot be labelled clearly by one label or a label cannot be present.

Result: Passed

Observations:

Where colour is used, text alternatives and descriptions are used.

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

Result: Passed

Observations:

Text font size is proportional so that user agents can scale content effectively. A font-size is specified for the body element, all other elements inherit that value, unless overridden by a more specific selector.

Result: Passed

Observations:

Most content in pages and modals reflowed without any loss to functionality.

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.

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

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:

All areas had good keyboard focus and focus / tab order was logical. Layers are built using the HTML5 tag and the tab order remains logical and the user is always able to return to the correct part of the screen.

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.

Result: Passed

Observations:

Titles have the key page content / topic listed before the system name

Result: Passed

Observations:

Focus order works even when using modal layers

Result: Failed

Observations:

The website comprises of a main, 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. Whilst this could be combined to one link, this would reduce the opportunities for a user to see that the site is offering options for contacting them.

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.

Result: Passed

Observations:

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

Result: Passed

Observations:

Handled by user agent.

Result: Not present

Result: Not present

Result: Passed

Observations:

Where two strings cannot be grammatically or seamlessly combined using aria-labelledby, aria-label has been used to make a new name which includes the visible label.

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.

Result: Passed

Observations:

For the validation feature that validates numeric input, the user is warned where there have been non-numeric chars entered, and returned back to the 'sanitised' field i.e. content changed, but not context.

Result: Passed

Observations:

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

Result: Passed

Observations:

Naming is consistent.

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

Result: Passed

Observations:

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

Result: Passed

Observations:

All data entry is checked and save is not possible unless data is correct. Users are asked to correct any errors before any changes can be made.

Result: Passed

Observations:

HTML, JS, and CSS are valid. All elements have correct start and end tags.

Result: Passed

Observations:

Strong use of aria-labelledby and aria-label (where HTML element does not have a specific label that it could be associated with).

State changes are noted via modals, or via aria select states (for example in the tab selections).

Result: Not present

Observations:

There are no appropriate places where a status message would be needed.