WCAG 2.2

Checkpoint

Conformance Level

Remarks

1.4.3: Color Contrast (Minimum) (AA)
Text has enough contrast with the background (4.5:1 for small text and 3:1 for large text)

Text has sufficient contrast with its corresponding background in most areas.

Exceptions:

• Home, Profile Details, Research Unit Details: Text within images of “UN Sustainable Development Goals” menu buttons (white) may lack sufficient contrast against their backgrounds (various colours)
• Research Output, Research Output Details, Profile Details: Text in the PlumX tooltip (e.g. orange, green, purple) may lack sufficient contrast against the background (white)  

1.4.5: Images of Text (AA)
Text is used rather than images of text, except where the presentation of text is essential, such as logos

No images of text are used other than for logos or essential presentation in most areas.

Exceptions:

• Home, Profile Details, Research Unit Details: “UN Sustainable Development Goals” menu buttons utilize images of text

1.4.11: Non-Text Contrast (AA)

User interact components and graphical objects have a contrast ratio of at least 3:1 against adjacent color(s).

Almost all non-text UI components and graphical objects have at least a 3:1 contrast ratio against surrounding colors.

Exceptions:

• Various pages: “Fingerprint” donut chart icons may lack sufficient contrast between slices (grey vs. green)
• Home, Profile Details, Research Unit Details: Pindrop icon (orange) on the world map may lack sufficient contrast against continents (grey)

1.4.13: Content on Hover or Focus (AA)

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

• Dismissible
• Hoverable
• Persistent

Some instances of content that appears on hover or focus are not dismissible, hoverable, or persistent according to the criteria.

Exceptions:

• Profile Details: “Per year” expanded bar graphs feature tooltips on pointer hover, but the pointer may not be moved over the additional content without disappearing
• Find Profiles, Profile Details: Tooltips on “Research activity per year” bar graphs are hoverable, but are not always positioned exactly adjacent to or overlapping their triggers (which have small targets)
• Advanced Search: Help/information ‘i’ tooltips are not dismissible (e.g. via Esc key)
• Search: PlumX & Altmetric tooltips may occasionally overlay citation text or citation count but are not dismissible (e.g. via Esc key)

WCAG 2.2

Checkpoint

Conformance Level

Remarks

2.1.1: Keyboard (A)

All functionality is available from a keyboard, except for tasks such as drawing

Most standard web page content and functionality is keyboard operable across pages. Keyboard-operable functional equivalents to pointer interactivity on world maps are available via the “Dive into details” modal.

Exceptions:

• Research Output, Research Output Details, Profile Details: PlumX and Altmetric tooltips are only triggered by pointer hover and not keyboard focus – although the links to external pages with similar/additional information are keyboard operable
• Find Profiles, Profile Details: Email address link is excluded from the tabindex (i.e. not keyboard focusable)
• Profile Details, Research Unit Details: Interactive functionality within Network “Visualization” diagrams (e.g. repositioning nodes, activating details) is largely not keyboard operable

2.4.3: Focus Order (A)

Users can tab through the elements of a page in a logical order

Tab order is largely logical across the site and preserves the meaning and operability of content in most instances. Note: using the Esc key on Profile Details (e.g. to dismiss a tooltip) may unexpectedly reset keyboard focus to the “Contact expert” button.

Exceptions:

• Home: Topic/concept components do not manage focus in a logical manner when child popover menus are dismissed – focus does not return to the parent menuitem
• Home: (Optional) slideshows feature tablist controls operated via left/right arrow key navigation, yet focus does not follow the active tab/slide marker even if navigation is user-initiated

WCAG 2.2

Checkpoint

Conformance Level

Remarks

1.3.1: Information and Relationships (A)

Info, structure, and relationships can be programmatically determined

Most content is distinguishable via semantic structure and relationships. A logical heading order reflecting page organization and content is programmatically determinable on most pages. Most input elements have programmatically determinable labels. HTML sectioning elements/landmark roles demarcate content regions.

Exceptions:

• Profile Details: Copyright tooltips may share an id value, leading to erroneous descriptions for copyright buttons (the buttons reference tooltip text via aria-describedby attributes)
• Profile Details, Research Unit Details: “Per year” expanded bar graphs have visually hidden alternatives available for AT users in table markup – although table cells may have erroneous/deprecated scope attributes

3.1.2: Language of Parts (AA)

Specify the language of text passages that are in a different language than the default language of the page.

Sections or phrases of text may occasionally not match the default (i.e. selected) page language.

Exceptions:

• Various pages: Various terms (e.g. research output titles, research unit or institutional names) are not programmatically specified as differing from the default language of the page

WCAG 2.2

Checkpoint

Conformance Level

Remarks

1.3.5: Identify Input Purpose (AA)

The purpose of each input field collecting information about the user can be programmatically determined when:

• The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
• The content is implemented using technologies with support for identifying the expected meaning for form input data.

Applicable form elements that collect such information about the user are very uncommonly encountered.

Exceptions:

• Profile Details: “Your name” & “Your email” fields in the “Contact expert” modal lack appropriate autocomplete attributes.

4.1.2: Name, Role, Value (A)

For all UI components, the name, value, and role can be programmatically determined.

Most UI components communicate their state programmatically, and many have accessible names that are appropriately defined.

Exceptions:

• Profile Details: “Contact expert” modal bears a dialog role but lacks an accessible name (e.g. via aria-labelledby attribute) and aria-modal="true"
• Profile Details, Research Unit Details: Entire Network “Visualization” section (including keyboard-operable forms and controls) is rendered unavailable to AT via aria-hidden="true". A brief message about the inaccessibility of the “Visualization” to screen readers is announced on page load.
• Find Profiles, Profile Details: Tooltip containers on “Research activity per year” bar graphs erroneously bear aria-expanded attributes

WCAG 2.2

Checkpoint

Conformance Level

Remarks

2.2.2: Pause, Stop, Hide (A)

Users can stop, pause, or hide moving, blinking, scrolling, or auto-updating information.

There is no moving, scrolling, or auto-updating information for which the criterion is applicable on almost all pages.

Exceptions:

• Home: (Optional) slideshow starts automatically and lacks a pause, stop, or hide mechanism

WCAG 2.2

Checkpoint

Conformance Level

Remarks

2.5.7: Dragging Movements (AA)

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.

Functionality that utilizes dragging movements is very uncommonly encountered

Exceptions: 

• Profile Details, Research Unit Details: Repositioning view and nodes within the “Force” diagram of the Network “Visualization” is not possible without dragging, although repositioning is largely cosmetic/temporary

2.5.8: Target Size (Minimum) (AA)

The size of the target for pointer inputs is at least 24 by 24 CSS pixels, with certain exceptions involving:

• Spacing
• Equivalent
• Inline
• User agent control
• Essential

Targets for pointer inputs usually exceed the minimum size defined by the criterion. Note: equivalent functionality to potentially overlapping components on the Map (where targets may not meet the minimum size requirements) is provided via the “Dive into details” modal. Various “per year” bar graphs associated with profiles may feature tooltips on pointer hover with small/narrow triggers.

Exceptions: 

• Profiles: Supplementary profile links organized within lists (e.g. email, organizations) may lack targets of sufficient size