Accessibility evaluation report 25-09-2024

Result: Passed

Observations:

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

Images have ALT text as does the main logo.

Result: Not present

Observations:

The system does not have audio or video content.

Result: Not present

Observations:

The system does not have audio or video content.

Result: Not present

Observations:

The system does not have audio or video content.

Result: Not present

Observations:

The system does not have audio or video content.

Result: Not present

Observations:

The system does not have audio or video content.

Result: Passed

Observations:

Relationships are defined programmatically and semantic markup has been appropriately used to designate headings, regions/landmarks, lists, emphasized or special text.

Tables are used for tabular data and data cells are associated with their headers.

Text labels are associated with form inputs. ARIA labelling is used when standard HTML is insufficient.

Result: Passed

Observations:

The reading and navigation order (determined by code order) is logical and intuitive.

Result: Passed

Observations:

Some items are presented using visual cues, however these have text or ARIA alternatives where applicable. Instructions do not rely upon sound, shape, size, or visual location

Result: Passed

Observations:

System is responsive and works well on different screen sizes and orientations, unless a specific orientation is necessary.

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. Input fields that collect certain types of user information have an appropriate autocomplete attribute defined. For example, autocomplete is used for the login aspects, and for the first delegate when making a booking where it is assumed the 'booker' will be the first delegate.

Result: Passed

Observations:

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

Result: Not present

Observations:

The system does not have audio or video content.

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 system 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 is used almost exclusively, and images of text are not used. Where they are, for example in iconography, the aria version is used for AT and is read out in place of the image

Result: Passed

Observations:

Content was scalable to a width of 320px. There were some instances of tables with many headings where content had to scroll both horizontally and vertically but content that requires horizontal scrolling, such as data tables, complex images (such as maps and charts), toolbars, etc. are exempted.

Result: Passed

Observations:

All icons and graphics had suitable contrast ratios and at least 3:1 contrast is maintained in the various states (focus, hover, active, etc.) of author-customized interactive components.

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 ensure no loss of content or functionality occurs 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 that can be opened by keyboard control and the hover is dismissed as focus is lost. Modals are focussed automaticlaly 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 <modal> 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: Passed

Observations:

A user is warned before logout and given instruction on how to refresh their session. There are no other timed elements.

Result: Not present

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:

Skip' link presented and 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: Passed

Observations:

Where <a> tags are used and are part of large lists of links e.g. in a data table, these are re-written to make them contextually distinguishable.

Result: Passed

Observations:

Many pages are part of a 'content flow' and therefore can only be accessed by utilising the UI as part of the required steps / processes. All major site features are accessible via a consistent main navigation and sub-navigation.

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: Passed

Observations:

When elements have keyboard focus, they are not entirely covered or hidden by page content.

Result: Not present

Result: Not present

Result: Passed

Observations:

Where the system rewrites aria links for <a> or <button> or <input> tags, it always includes the original visible text.

Result: Not present

Result: Not present

Result: Passed

Observations:

Pointer input target sizes are at least 24 by 24 pixels, or a 24 pixel diameter circle centred on the target element does not intersect with any other target or a 24 pixel circle centred on an adjacent target i.e. there are not two adjacent pointer targets adjacent that could be clicked / activated by mistake.

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:

When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.

Result: Passed

Observations:

Although some elements change content, context is not changed. Where that is not true, for example where changing a dropdown value requires further information to be entered, the user is told of this via live region announcement.

Result: Passed

Observations:

There are additional navigations present on some pages albeit these are consistent in context of that page / section. Main navigation elements are consistent everywhere they are presented.

Result: Passed

Observations:

Shared components are always identified consistently.

Result: Passed

Observations:

Help and instructions are presented at the top of each page, as one of the first elements of the main page content.

Result: Passed

Observations:

Visually errors are highlighted, but all errors appear in a modal with a description of the error and its context. Input validation can occur oninput to assist the user in entering the correct data, and some screens presented errors in a summary area with a clickable link to each error. In most cases that were tested, the first error was also given focus.

Result: Passed

Observations:

Instructions are provided on each screen, with properly positioned input labels, or fieldsets/legends.

Result: Passed

Observations:

Incomplete or missing data has suggested fixes, particularly where validation requires two or more fields to be in complimentary states, or where data has a specfifc format such as an input accepting only text data.

Result: Passed

Observations:

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

All actions have a confirmation element, in particular delete actions.

Result: Passed

Observations:

When encountering an error, the user data is re-shown in forms except where that data is invalid. For example, adding a new booking would show all entered data again.

Result: Passed

Observations:

Login does not require a cognitive function test as the main 'booker' for a booking recives a secure link serving as thier login.

In the event a user loses this email, or for non-booker users, they can log in using their email address with the appropriate autocompelete used, and receive an authentication code.

Result: Passed

Observations:

Strong use of HTML specifications for all elements. For example, all forms have names, aria-labels, can be keyboard controlled, use sematic labels for required elements, respect focus states, have logical tab orders.

Aria is used only where the HTML is not sufficient / appropriate. The system uses HTML first and does not 'clutter' the experience with unnecessary ARIA.

Result: Passed

Observations:

Status messages are used consistently and appropriately. For example, after a user presses a Search button, the page content is updated to include the results of the search, which are displayed in a section below the Search button. The change to content also includes the same message near the top of this new content. There is also a status message that is presented for assistive technology users.