VISUALS

WCAG 2.2

Checkpoint

Conformance Level

Remarks

1.1.1: Non-Text Content (A)
Provide text alternatives for non-text content (e.g. images)

While content is largely text-based, there are significant instances where non-text content – including meaningful icons and data visualizations – lacks appropriate text alternatives. In Reporting, data tables corresponding to “data stories” visualizations in charts are available on the same page and exportable in Excel spreadsheets or CSV.

Note: Controls containing non-text content such as icon buttons may lack names that describe their purpose – see SC 4.1.2 for instances of icon components missing accessible names (text labels for several components may only be available via title attribute).

Exceptions:

• Dashboard, Usage analytics: Charts – Chart <svg> elements may contain text elements (labels), yet may lack appropriate alternatives or descriptions in text
• Dashboard: "Layout" options in Settings – Thumbnail/icons (and thus link components) lack text alternatives
• Add/Edit Record: Locale icons – Icons of locales/countries appearing adjacent to various fields, implemented via CSS backgrounds, lack text alternatives
• Add/Edit Record: Required '*' icons – Asterisks appearing adjacent to various fields, implemented via CSS backgrounds, lack text alternatives beyond the title attribute
• Award Management: Icons in cell content – Icons, implemented via CSS backgrounds, denoting e.g. "Awards", "Project" by their appearance in cells lack appropriate text alternatives (icon components may also function as controls for various popovers)

1.3.3: Sensory Characteristics (A)
Do not rely on sensory characteristics of components such as shape, size, visual location, orientation, or sound

In almost all instances, instructions for operating or understanding content do not rely solely on sensory characteristics.

Exceptions:

• Editor, Master Data, REF2021, Award Management: Pin button for search results filters – Component's only available label (via title attribute), "Save filter settings and pin them to the left menu", only describes the visual location of the relevant menu
• Dashboard: "Add widget" modal – Instructions within tab panel refer ambiguously to the visible location of a set of components

1.4.1: Use of Color (A)
Color is not used as the only visual means of conveying info

In most instances, when color is used as a means of conveying information, another visual method is also used to convey the information without color.

Exceptions:

• Data Quality: Toggle expansion button in table – Focus state of button is only indicated via a change in color
• Editor, Master Data, REF2021, Award Management: Icons in search results/table – Meaningful states of certain icons, e.g. 'visibility' dot or 'favorite' star, may only be indicated via changes in color
• Add/Edit Record: Input fields – Error state of input fields may only be denoted via color difference (e.g. pink fill) and lack another visual means of indication (e.g. symbol)
• Editor, Master Data, REF2021, Award Management: Filter management components, search results – Visual indications of focus on various components may rely solely on changes in color (icon or background)

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 many areas.

Exceptions:

• Add/Edit Record: "Last saved" status – Text (light grey) lacks sufficient contrast against background (dark grey)
• Add/Edit Record: Various text elements, labels – Text (typically grey) lacks sufficient contrast against background (white or light grey)
• Add/Edit Record: Tab group heading – Text (grey) lacks sufficient contrast against background (light grey)
• Editor, Master Data, REF2021, Award Management: Various text elements, labels – Text (typically grey) lacks sufficient contrast against background (white or light grey)
• Dashboard: Empty dashboard message – Text (grey) lacks sufficient contrast against background (light grey)
• Editor, Master Data, REF2021, Award Management: Search field – Placeholder text (light grey) lacks sufficient contrast against its background (grey). The placeholder is the only visible label text for the field.
• Add/Edit Record: Error message – Field-adjacent error message text (red) may lack sufficient contrast against the background (white)

1.4.4: Resize Text (AA)

Text can be enlarged up to 200% without loss of functionality.

Text may be enlarged to 200% while preserving functionality of content in some instances. Interactive charts in Reporting (including constituent text labels) are not affected by browser text scaling settings.

Exceptions:

• Add/Edit Record: Form buttons – Component label text is partially obscured when text is scaled to 200% as container heights do not resize proportionally
• Editor, Master Data, REF2021, Award Management: Search/table summary – Summary components (e.g. tally of results) may be partially obscured when text is scaled to 200% as container heights do not increase proportionally
• Editor, Master Data, REF2021, Award Management, Add/Edit Record: Text, numbers in pills – Information may be partially obscured when text is scaled to 200% as containers may not resize proportionally
• Editor, Master Data, REF2021, Award Management: Headings in overview – Headings are partially obscured when text is scaled to 200%
• Usage analytics: Links, component labels – Various labels are partially obscured when text is scaled to 200% as containers do not resize proportionally

1.4.10: Reflow
(AA)
Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

• Vertical scrolling content at a width equivalent to 320 CSS pixels;
• Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Many pages and significant areas of content do not feature responsive views where content reflows into a single column. The global header menu collapses into a single-column hamburger menu at very high zoom states. Editor, Master Data, REF2021 support a limited degree of reflow at very high zoom states, where horizontal scrolling is not required in the search results section. Data tables within the similar interface in Award Management, however, require horizontal scrolling at higher zoom states. 

Exceptions:

• Login: Page content – Page content does not reflow – horizontal scrolling may be required to reach "Login" button at very high zoom states
• All pages: Main content – While global header menu collapses into a hamburger menu supporting single-column reflow at very high zoom states, main content area largely does not feature responsive design and may necessitate horizontal scrolling – or in some instances, content may be truncated/obscured.
• Add/Edit Record: Window contents – Horizontally tabbed/paned contents are do not feature responsive design and do not support reflow at very high zoom states – modals are centered in viewport and may be truncated/obscured.
• Add/Edit Record: Footer – Page content may be obscured at very high zoom states if sticky footer components (e.g. “Application approval route”) are present
• All pages: Dialogs via header – Modal dialogs initiated via components from the header's hamburger menu (e.g. "Notifications", "Tasks", etc.) may be partially truncated at very high zoom states.
• Reporting: Page sections – Sections, e.g. "Recent workspaces" & "My favourites", reflow into a single column at high zoom states – however, content within sections does not reflow and may be truncated (and may be impossible to reach even with horizontal scrolling)
• Data Quality: Page content – Paned content does not reflow at very high zoom states, and content in main panel on the right(e.g. "List of entities") may be impossible to reach even with horizontal scrolling

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).

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

Exceptions:

• Editor, Master Data, REF2021, Award Management: Sidebar expand/collapse control – Icon component (light grey) lacks sufficient contrast against background (white/light grey)
• Editor, Master Data, REF2021, Award Management: Filter management components for search results – Icon components (e.g. "Add filter" button, 'x' remove filter button) may lack sufficient contrast against the background (grey vs. light grey)
• Editor, Master Data, REF2021, Award Management: Search result action components – Icon components (e.g. star icon 'favorite', cog icon 'properties') lack sufficient contrast against the backgrounds (light grey vs. white)
• Editor, Master Data, REF2021, Award Management: "New" '+' icon button in sidebar navigation – Icon component (steel blue), visible on pointer hover while sidebar is expanded, lacks sufficient contrast against background (light blue)
• Dashboard: Widget controls & other components – Icon components may lack sufficient contrast against the background (grey vs. white)
• Add/Edit Record, Dashboard: Checkbox & radio controls – Styled custom checkboxes and radio buttons (grey) lack sufficient contrast against the background (white)
• Add/Edit Record, Dashboard: Input fields – Bounding boxes for text input fields (steel grey) may lack sufficient contrast against the background (white)
• Add/Edit Record: Error indication – Fields with invalid input may be indicated via a dashed outline (rose) that may lack sufficient contrast against the background (white)

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

Content that appears on hover or focus is uncommonly encountered, however in some instances such content is not dismissible, hoverable, or persistent according to the criteria. In Add/Edit Record, hint tooltips appear on pointer hover over ‘i’ icon components that may not be hoverable according to the criteria – however activating the component via pointer click toggles/locks the visibility of the tooltip.

Exceptions:

• Dashboard: Tooltips in charts – Tooltips on pointer hover are not hoverable nor dismissible according to the criteria
• Usage analytics: Tooltips in charts – Tooltips on pointer hover are not dismissible according to the criteria

KEYBOARD

WCAG 2.2

Checkpoint

Conformance Level

Remarks

1.3.2: Meaningful Sequence (A)

The correct reading sequence can be programmatically determined

The correct reading sequence is typically logical and programmatically determinable, with the DOM order according with the visual order in most areas.

Exceptions:

• Login: Form labels & fields – "Username" & "Password" labels occur together in the sequential reading order – before the set of visually adjacent input elements
• Editor, Master Data, REF2021, Award Management: "Add filter" menu button for search results – Drop-down menu options do not follow the activating control in the DOM/sequential reading order
• Award Management: "Table settings" & table header menu components – Drop-down menu options do not follow the respective activating control in the DOM/sequential reading order

2.1.1: Keyboard (A)

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

Standard web page content and functionality is keyboard operable to a moderate extent, although there are significant instances where interactive components are not keyboard focusable/operable.

Exceptions:

• Editor, Master Data, REF2021, Award Management: Search result action components – Icon components (e.g. star icon 'favorite', cog icon 'properties', caret icon expand) are not in the tabindex (i.e. not keyboard focusable/operable)
• Editor, Master Data, REF2021, Award Management: "Page size" & "Sort by" options for search results – Components are implemented as generic <span> elements and are not in the tabindex (i.e. not keyboard focusable)
• Data Quality: "Synchronized" icon button – Tooltip with information on synchronized state only appears on pointer hover – component is not keyboard focusable
• Dashboard: Widget controls & other components – Various components (e.g. icon buttons for widget controls, chart interactives/tooltips) are not keyboard focusable/operable
• Dashboard: "Add widget" modal – Components within modal container are largely not keyboard operable
• Add/Edit Record: "View possible duplicates" button – Component that appears next to title field under specific circumstances is not keyboard focusable/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.

Exceptions:

• Various pages: Popover buttons in header – Focus may unexpectedly shift to an unrelated text input (e.g. search field) upon popover (e.g. "My favorites") dismissal – if such an input element is present within the main content area. (Focus normally returns to the respective button in the global header when its popover is dismissed via Esc key.)
• Editor, Master Data, REF2021, Award Management: "Add filter" menu button for search results – Drop-down menu is not immediately situated next to the activating control in the tab order
• Award Management: "Table settings" & table header menu components – Drop-down menu is not immediately situated next to the respective activating control in the tab order
• All pages: Global search – Dialog lacks proper focus management: components in the activated container are not immediately situated next in the tab order after conducting a search
• Add/Edit Record: Modal dialog – Container lacks proper focus management for a modal: focus is not trapped inside the activated container

2.4.7: Focus Visible (AA)

The page element with the current keyboard focus has a visible focus indicator

Some elements across the site feature visible indications of focus, although there are significant instances where interactive components lack adequate focus indicators. The browser default focus indicator is occasionally present – while in other instances an underline, container background color change, or outline style (particularly prominent in the global header and pages with the “refreshed appearance”) is utilized.

Exceptions:

• Dashboard: Top menu bar – Components lack visible focus indicators
• Editor, Master Data, REF2021, Award Management: Links & components in overview, search results – Links & other components may lack visible indications of focus
• Administrator: Links in tab panels – Links (e.g. in Overview) may lack visible indications of focus

2.4.11: Focus Not Obscured (Minimum) (AA)

When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

Components are typically not obscured by other content at the point when they receive focus, although there may be suboptimal focus management behavior with non-modal dialogs (see also SC 2.4.3) that may unexpectedly obscure components in focus. In Add/Edit Record, visible keyboard focus is generally not obscured by sticky footer components (e.g. “Application approval route”).

Exceptions:

• All pages: Global search dialog – Components behind global search dialog may be completely obscured yet receive focus

HEADINGS AND STRUCTURE

WCAG 2.2

Checkpoint

Conformance Level

Remarks

1.3.1: Information and Relationships (A)

Info, structure, and relationships can be programmatically determined

Content is distinguishable via semantic structure and relationships to a moderate extent. A logical heading order reflecting page organization and content, although generally sparse, is programmatically determinable on some pages. Table and list markup are used appropriately in various instances. HTML sectioning elements/landmark roles demarcate content regions.

Exceptions:

• Login: Input fields – Login form's "Username" & "Password" inputs are not programmatically associated with adjacent visible labels
• Login: Page structure – Table is utilized for layout without presentation role
• Various pages: Main heading – Pages may lack first heading level <h1> – several pages may lack any programmatically determinable headings.
• Editor, Master Data, REF2021, Award Management, Data Quality: Headings – Items within lists may utilize heading markup, leading to a heading order not reflective of page organization (e.g. excessive number of <h2> elements in an otherwise sparse heading order)
• Editor, Master Data, REF2021, Award Management: Section headings – Section headings on Overview contexts are visually distinguished but lack heading markup
• Administrator: Headings – Section headings, including hierarchical organization, may not be properly represented in semantic markup (e.g. lack of headings, or all headings defined as <h2> despite some being nested)
• Data Quality: Tables – Column header cells in the first row contain <h3> heading elements; several header cells are empty. Row headers are not defined, and header lack scope attributes.
• Add/Edit Record, Dashboard: Input fields – Sets of related inputs such as radio buttons or checkboxes are not grouped (e.g. within a fieldset) – while a visible group label/legend may be present, input options are implemented as <a> link elements rather than <input> elements
• Add/Edit Record, Dashboard: Input fields – Inputs lack programmatically determinable labels (adjacent visible labels are not programmatically associated with inputs)
• Add/Edit Record: Input fields – Required fields are largely visually indicated but not programmatically determinable
• Reporting: Input fields – Various inputs lack a programmatically determinable label (field placeholder text does not suffice)

2.4.1: Bypass Blocks (A)

Users can bypass repeated blocks of content.

On most pages, landmarks demarcating various content regions – and the presence of programmatically determinable headings – allow AT users to conveniently jump to different areas of content.

Exceptions:

• All pages: Methods to skip repeated blocks of content – Many pages lack skip links to main content and have a sparse heading structure, although global header navigation and main content area bear the appropriate landmarks

3.1.1: Language of Page (A)

The language of the page is specified

The default page language is usually appropriately defined as lang="en-GB".

Exceptions:

• Add/Edit Record: Page language is not defined
• Login: The default page language is not defined

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. Functionality to specify localization of various terms and text exists in Add/Edit Record, but the difference in language for passages of text in saved records is typically not programmatically determinable across the site.

Exceptions:

• Various pages: Various terms (e.g. research output titles) are not programmatically specified as differing from the default language of the page, although the difference in language may be contextualized via record information (e.g. "Original language: Russian")

LABELING

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.

The only page featuring applicable form elements that collect such information about the user is Login (which an external method of authentication, if configured, would supplant).

Exceptions:

• Login: Input fields – Relevant personal information fields lack autocomplete attributes

2.4.2: Page Titled (A)

The page has a title describing its topic or purpose

Many pages feature a descriptive page title that identifies content or purpose. For instance, sub-page titles are appended to the main Pure platform title in a logical and consistent manner where appropriate (e.g. “Pure – Organisational Units – Editable”).

Exceptions:

• Reporting, Data Quality, Usage analytics: Pages lack descriptive/informative title; page title is the generic main Pure platform title

2.4.4: Link Purpose (In Context) (A)

The purpose of each link can be determined from the link text or surrounding context.

An identifiable purpose may be deduced for many links from the link text or surrounding context.

Exceptions:

• All pages: Various links – Numerous links open in a new window/tab (e.g. Add/Edit Record data entry process), yet do not indicate this behavior via link label or other method
• All pages: "New" '+' icon button in sidebar navigation – Links lack descriptive specificity – they are generically labelled "New" (and only via title attribute)

2.5.3: Label in Name (A)

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

Most user interface components that have visible text contain that text consistently within the accessible name.

Exceptions:

• All pages: "+ Add content" button – Button's accessible name is defined by aria-label attribute, i.e. "false", which does not accord with the visible label. (Button has appropriate aria-label while responsively resized to icon-only at higher zoom states.)
• Reporting: "Search for Workspaces" combobox – Field placeholder "Search for workspaces" does not accord with its accessible name (via aria-label attribute), "Searchable list"

3.3.1: Error Identification (A)

Input errors are clearly marked and described to the user.

Errors are generally identified visually and may be validated before (dynamically) or after form submission. Error messages that offer specific feedback are occasionally presented either in (modal) dialogs, or adjacently and visually distinguished via different text color (red). However, error states are largely not programmatically determinable. Focus management is occasionally utilized to direct users to the message or relevant fields.

Exceptions:

• Add/Edit Record: Input fields, form components – Dynamic validation may indicate erroneous input (e.g. when input is not in required data format) only while the field is in focus – and potentially only via a change in color. Certain sections of the form may only indicate error states visually (e.g. with outline after validation). Neither required fields nor fields with invalid input are programmatically indicated.

3.3.3: Error Suggestion (AA)

When the user makes an input error, give suggestions for valid input.

Relevant helpful suggestions are occasionally provided in text via various mechanisms – e.g. “View possible duplicates” for title input in Add/Edit Record, or messages in error notification dialogs such as “Contributors - persons: 0 is less than the lowest allowed value 1”.

Exceptions:

• Add/Edit Record: Input fields – Inputs that require specific data formats, e.g. numerical input for number of pages, may be dynamically validated – however there may be no indication that input falls outside the required format nor suggestions for correction beyond a change in field background color (pink) while in focus

4.1.2: Name, Role, Value (A)

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

Some UI components communicate their state programmatically and have accessible names that are appropriately defined – however there are numerous significant exceptions involving the lack of accessible names or appropriate roles/ARIA attributes.

Exceptions:

• All pages: Navigation menu buttons in header – Icon buttons "⌄" lack descriptive accessible names – accessible names are defined by aria-label attributes but are generic icon asset names, i.e. "navigate-down"
• Editor, Master Data, REF2021, Award Management: Pin button for search results filters – Component lacks an accessible name and is implemented as a <a> link element sans label text, rather than a button – the title attribute on a containing <span> provides the only available label
• Editor, Master Data, REF2021, Award Management: Filter management components for search results – Components are implemented as <a> link elements rather than buttons, and several icon buttons lack accessible names (with title attribute as only available label). Several components lack appropriate attributes to communicate state and the availability/type of interaction (e.g. aria-expanded, aria-haspopup).
• Editor, Master Data, REF2021, Award Management: Search result action components – Icon components (e.g. star icon 'favorite', cog icon 'properties', caret icon expand) are implemented as <a> link elements rather than buttons, lack accessible names. Several components lack appropriate attributes to communicate state and the availability/type of interaction (e.g. aria-expanded, aria-haspopup).
• Master Data, Award Management: "Table settings" gear icon button – Component is implemented as <a> link element rather than button, and lacks an accessible name (title attribute is the only available label). Components lack appropriate attributes to communicate state and the availability/type of interaction (e.g. aria-haspopup).
• Editor, Master Data, REF2021, Award Management: "Page size" & "Sort by" options for search results – Components are implemented as generic <span> elements rather than buttons or <select> menu controls.
• Data Quality: Toggle expansion button in table – Icon buttons' accessible names are generic & not descriptive ("toggle"), and lack appropriate attributes to communicate expanded/collapse state (i.e. aria-expanded)
• Data Quality: Dialogs – Dialogs, e.g. for Related Content or Match Score, lack accessible names
• Data Quality: Options within table – Set of options, implemented as (ungrouped) checkboxes, lack appropriate accessible names – multiple components are identified generically as "toggle" via aria-label attributes
• Data Quality: Expandable controls – Components bear generic accessible names via aria-label ("toggle"), and do not communicate state via aria-expanded attributes
• Data Quality: "Duplicate groups" tooltip icon button – Component lacks an accessible name and is implemented as a generic <div> rather than a button. (While component may receive focus and trigger the tooltip, tooltip content is not available or announced to AT.)
• Editor, Master Data, REF2021, Award Management: Sidebar expand/collapse control – Component is implemented as <a> link element rather than button, and lacks an accessible names (title attribute is the only available label).
• Dashboard: Top menu bar – Component are implemented as <a> link elements rather than buttons, and lack appropriate attributes to communicate state and the availability/type of interaction (e.g. aria-haspopup).
• Add/Edit Record, Dashboard: Checkbox & radio inputs – Inputs are implemented as <a> link elements rather than <input> elements – while each control is typically adjacent to a respective visible label, an appropriate role or name/label is not programmatically determinable
• Add/Edit Record: Modal dialog – Containers that should exhibit modal behavior lack dialog roles and aria-modal="true" attributes

4.1.3: Status Messages (AA)

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Status messages are uncommonly encountered (many content changes initiate a page refresh). Toast messages on pages with the “refreshed appearance” are typically announced by assistive technology.

Exceptions:

• Editor, Master Data, REF2021, Award Management: Search result tally – Filter modification may initiate dynamic page content updates (i.e. updated results of search); the tally of search results (and potentially other aggregate statistics in Award management) is also updated yet not announced to AT
• All pages: Global search dialog – Search is dynamically initiated after input of at least three characters; the message "Here are the top 50 results..." that appears at the beginning of the search results is not announced to AT

MOBILE USER EXPERIENCE

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 uncommonly encountered. In Add/Edit Record, file browse dialogs are typically available as alternatives to drag-and-drop functionality for uploading files.

Exceptions:

• Editor, Master Data, REF2021, Award Management: Table headers – Repositioning of table headers (e.g. in Award management applications or Organization unit roles) relies on dragging movements and lacks a single pointer method

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

Many targets for pointer inputs either exceed the minimum size defined by the criterion or qualify under the spacing exception. Note: Various charts (e.g. bar graphs) in Reporting & Usage analytics may feature tooltips on pointer hover with small/narrow triggers.

Exceptions:

• All pages: Sidebar expand/collapse control – Target is not sufficiently sized / horizontally spaced from adjacent targets (sidebar components)
• Various pages: Drop-down menu options – Each option is not sufficiently sized / vertically spaced from adjacent options
• Editor, Master Data, REF2021, Award Management: Pagination – Targets for page links may not be sufficiently sized / horizontally spaced from adjacent links
• Editor, Master Data, REF2021, Award Management: Links & components in search results, table – Interactive elements (e.g. edit author links) may not be sufficiently sized / horizontally spaced from adjacent targets
• Add/Edit Record: Localization selection – Icon components are not sufficiently sized / horizontally spaced from adjacent links
• Dashboard: Links in table widgets – Targets for links may not be sufficiently sized / vertically spaced from adjacent links
• Add/Edit Record: Add/remove '+/-' icon components – Target is not sufficiently sized / horizontally spaced from adjacent targets
• Editor, Master Data, REF2021, Award Management: Remove filter 'x' buttons – Icon components may not be not sufficiently sized / horizontally spaced from adjacent links

Page

Last score

New score

CDF config

96

100

Data Quality

97

100

Metrics config

96

100

Open access config

96

100

OrgResolver config

96

100

PUX

97

100

Image licensing config

96

100