Accessibility Conformance Report WCAG Edition
(Based on VPAT® Version 2.4Rev)
Name of Product/Version: Humap Platform
Report Date:
Product Description: Interactive map platform Contact Information: team@humap.me Notes:
The Humap platform includes significant quantities of User-generated (third-party) content which are not in scope for this assessment.
Evaluation Methods Used:
This review of the Humap platform has been undertaken by the Humap team in collaboration with external consulting parties, and users in a controlled test environment. The review has been conducted on desktop devices with and without assistive technologies. The Humap platform supports mobile devices with the same degree of functionality, and it is anticipated that this conformance report will be applicable to that scenario.
The scope of this review includes all pieces of functionality which are core to the Humap platform experience, but does not include reference to content which Humap’s clients have produced (“user-generated content”).
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
|
Standard/Guideline |
Included In Report |
|
Level A Level AA Level AAA |
|
|
Level A Level AA Level AAA |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the
- Does Not Support: The majority of product functionality does not meet the
- Not Applicable: The criterion is not relevant to the
- Not Evaluated: The product has not been evaluated against the This can be used only in WCAG 2.0 Level AAA.
Additional terms used in this document include:
- User generated content (or UGC): this is content which is created by an administrator or end-user of the Humap platform
- Instance: a website and map hosted on the Humap platform. Humap is a multi-tenant environment which uses the same code to provide multiple websites.
- The map: the portion of the application which is presented as a digital map, which can be moved and zoomed
- The tray: the portion of the application which is presented as a web page, showing text, images, links, forms and calls-to-action
- The gallery: the portion of the application which presents images, videos, audio, deep-zoom and other rich media content
Table 1: Success Criteria, Level A
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.1.1 Non-text Content (Level A) |
Supports |
Non-text content is routinely supplemented with alt and ARIA attributes. User-generated content has the facility to annotate any non-text content.
Most of the relevant images on Humap have alt-text or indications of purpose in the mark. |
|
|
Support |
The Humap platform does not require the use of audio or video. User-generated content may include these, and users are encouraged to provide alternatives. |
|
1.2.2 Captions (Prerecorded) (Level A) |
Supports |
There is no live audio or video content required on the platform. User-generated content may include these, and users are encouraged to provide captions as appropriate. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) |
Supports |
The platform has alternatives for every piece of media required by the application. User-generated content is encouraged to have alternatives. |
|
1.3.1 Info and Relationships (Level A) |
Supports |
Content is presented in a visual hierarchy which also conforms to meaningful HTML elements which can be inferred using assistive technologies. |
|
1.3.2 Meaningful Sequence (Level A) |
Supports |
The sequence of content on the page is represented in order in the markup, and will be read appropriately by assistive technology. |
|
1.3.3 Sensory Characteristics (Level A) |
Supports |
All content is accessible using multiple sensory characteristics. Where functionality such as colour is used as the primary characteristic, the platform makes use of alternatives such as graphic icons and patterns to complement this. No primary navigational components or user actions rely on the use of a single sensory characteristic. |
|
1.4.1 Use of Color (Level A) |
Supports |
Where colour is used as the dominant mode of differentiation, alternatives such as assistive tags or patterns are also applied. |
|
1.4.2 Audio Control (Level A) |
N/A |
No audio on Humap plays automatically. |
|
2.1.1 Keyboard (Level A) |
Partially |
For text-centric and form-centric content, keyboard tab order is supported. For the map, providing correct keyboard tab order is work-in-progress.
There will be some activities on the map which will be difficult to accomplish with only keyboard access, but where this is the case, content is also available in a traditional form in the tray.
An end-user cannot move the map with just the cursor without clicking on it first. All content on the map can be accessed from the information tray via keyboard shortcuts. |
|
2.1.2 No Keyboard Trap (Level A) |
Partially |
Where the user is navigating content in the tray, there is no Keyboard trap. Tab order for the map is a work in progress - see 2.1.1. |
|
2.1.4 Character Key Shortcuts (Level A 2.1 only) |
Partially |
The tray is fully accessible via keyboard shortcuts, but the map is not. |
|
2.2.1 Timing Adjustable (Level A) |
Supports |
There are no time limits on Humap |
|
2.2.2 Pause, Stop, Hide (Level A) |
Supports |
Scrolling is controlled entirely by the end-user. This includes auto-updating; the information tray returns results with an infinite scroll, but the user is in full control of the scroll action. |
|
2.3.1 Three Flashes or Below Threshold (Level A) |
Supports |
Nothing in the Humap design flashes. |
|
2.4.1 Bypass Blocks (Level A) |
N/A |
Tab order is used to allow end-users the ability to bypass blocks of repeated content. See 2.1.1. |
|
2.4.2 Page Titled (Level A) |
Supports |
Pages have titles which confer their use and position in the information hierarchy |
|
2.4.3 Focus Order (Level A) |
Partially |
The cursor is clear, icons light up when selected, the box around content that appears when the tab key is being used is visible. |
|
2.4.4 Link Purpose (In Context) (Level A) |
Supports |
Most links in the application convey their meaning through text. |
|
2.5.1 Pointer Gestures (Level A 2.1 only) |
Supports |
No functionality requires the use of multi-point or specific pointer gestures. Where multi-point gestures are supported (zooming and panning on the map) there are dedicated keyboard-accessible controls to accompany them. |
|
2.5.2 Pointer Cancellation (Level A 2.1 only) |
Supports |
Where actions are tied to a click, the onClick event is used, which supports pointer cancellation. |
|
2.5.3 Label in Name (Level A 2.1 only) |
Partially supports |
The majority of actions are labelled appropriately |
|
2.5.4 Motion Actuation (Level A 2.1 only) |
N/A |
There is no motion-activated functionality |
|
3.1.1 Language of Page (Level A) |
Partially |
The platform supports internationalised content and will automatically switch to the user’s browser locale if this feature is enabled. |
|
3.2.1 On Focus (Level A) |
Supports |
Events which trigger on a focus change don’t happen in the application - a click (or equivalent) is needed. |
|
3.2.2 On Input (Level A) |
Supports |
No changes are triggered as the result of content input, except for browser-side validation which is indicated in advance. |
|
3.3.1 Error Identification (Level A) |
Supports |
Errors are presented appropriately in all cases. |
|
3.3.2 Labels or Instructions (Level A) |
Supports |
All inputs have an associated label which explains their purpose. In some cases this is extended with exemplar placeholder content. |
|
4.1.1 Parsing (Level A) |
Supports |
Markup is only parsed for security purposes, and ensures the end content is free of duplicate IDs and similar. |
|
4.1.2 Name, Role, Value (Level A) |
Partially |
The majority of controls are native and so naturally have their name, role and value associated. Where custom controls have been developed, they largely support this. |
Table 2: Success Criteria, Level AA
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.2.4 Captions (Live) (Level AA) |
N/A |
No live content is used on Humap |
|
1.2.5 Audio Description (Prerecorded) (Level AA) |
Supports |
Where videos are uploaded as user generated content, there is provision for a transcript, and supporting information for users suggests the use of audio description. |
|
1.3.4 Orientation (Level AA 2.1 only) |
Supports |
The application scales and changes shape to fit either a wide or tall orientation, across mobile and desktop. |
|
1.3.5 Identify Input Purpose (Level AA 2.1 only) |
Partially supports |
In almost all cases, inputs conform to their standard uses (e.g. select elements for selection). Where special uses of standard inputs are used, we accompany them with ARIA labels. |
|
1.4.3 Contrast (Minimum) (Level AA) |
Partially supports |
The core design of Humap includes attention to minimum contrast. |
|
1.4.4 Resize text (Level AA) |
Partially supports |
The application supports changing the size of text |
|
1.4.5 Images of Text (Level AA) |
Supports |
There are no images of text in the application |
|
1.4.10 Reflow (Level AA 2.1 only) |
Partially supports |
Most content is accessible without scrolling in 2 dimensions with the exception of images in the gallery. The map requires scrolling in 2 dimensions for the purposes of finding a new location. |
|
1.4.11 Non-text Contrast (Level AA 2.1 only) |
Partially supports |
The application does not use low-contrast non-text elements. User-generated content may include this. |
|
1.4.12 Text Spacing (Level AA 2.1 only) |
Supports |
Text spacing is commensurate with the size of the text. |
|
1.4.13 Content on Hover or Focus (Level AA 2.1 only) |
Supports |
No Humap content is accessible only on hover - where hover states are used they are supplementary to a click or other means of access. |
|
2.4.5 Multiple Ways (Level AA) |
Supports |
With the exception of the wizard, which is a linear process, there are multiple ways to access all content. |
|
2.4.6 Headings and Labels (Level AA) |
Partially supports |
Headings and labels confer their use throughout the application. Some user generated content may not conform to this. |
|
2.4.7 Focus Visible (Level AA) |
Partially supports |
A cursor or a highlight is visible in most of the application. |
|
3.1.2 Language of Parts (Level AA) |
Supports |
The application supports internationalisation, and a given page will indicate its human language using metadata. |
|
3.2.3 Consistent Navigation (Level AA) |
Supports |
Navigation is standardised for a given part of the application. |
|
3.2.4 Consistent Identification (Level AA) |
Supports |
Content throughout the site is consistently identified - records, collections, wizard etc. |
|
3.3.3 Error Suggestion (Level AA) |
Supports |
Errors in creating content via UGC and through the content management system are returned via text |
|
N/A |
Not relevant |
|
|
4.1.3 Status Messages (Level AA 2.1 only) |
Partially supports |
Largely the user is provided with a status message when they complete an activity or interaction, through page elements which identify themselves as showing status. |
Table 3: Success Criteria, Level AAA
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.2.6 Sign Language (Prerecorded) (Level AAA) |
N/A |
The application includes no elements which require sign language, although it is possible for user generated content to include it if necessary. |
|
1.2.7 Extended Audio Description (Prerecorded) (Level AAA) |
N/A |
The application includes no elements which require extended audio description. |
|
1.2.8 Media Alternative (Prerecorded) (Level AAA) |
N/A |
The application includes no media which requires alternatives; user generated content on the site may well require alternatives, which are encouraged but not enforced. |
|
1.2.9 Audio-only (Live) (Level AAA) |
N/A |
The application includes no media which requires alternatives; user generated content on the site may well require alternatives, which are encouraged but not enforced. |
|
1.3.6 Identify Purpose (Level AAA 2.1 only) |
Partially supports |
Most interactive elements are self-identifying because they use browser primitives (e.g. form elements). Where higher-level components have been constructed, some have ARIA identification or similar. |
|
1.4.6 Contrast (Enhanced) (Level AAA) |
Partially supports |
A specific ‘high contrast’ mode is not available in the platform, but text and most actions have a contrast approaching 7:1. UGC may have lower contrast. |
|
1.4.7 Low or No Background Audio (Level AAA) |
N/A |
There is no background audio on Humap |
|
1.4.8 Visual Presentation (Level AAA) |
Partially supports |
Text can be zoomed, but background and foreground elements cannot be selected independently |
|
1.4.9 Images of Text (No Exception) (Level AAA) |
Partially supports |
There are no images of text on the platform. UGC may contain images of text. |
|
2.1.3 Keyboard (No Exception) (Level AAA) |
Partially supports |
Everything in the tray and wizards can be accessed using a keyboard. The map has areas which are not accessible by keyboard alone. |
|
2.2.3 No Timing (Level AAA) |
Supports |
Only nonessential visual effects have a timed component - for example the opening of a page element. All timed events end with the item of reference being in view. |
|
2.2.4 Interruptions (Level AAA) |
Supports |
Interruptions can be postponed or suppressed by the user, except interruptions involving an urgent message. |
|
2.2.5 Re-authenticating (Level AAA) |
Partially supports |
Only applicable to UGC. The wizard supports saving as draft, however should a session timeout occur the user will lose the data on the page they were on. |
|
2.2.6 Timeouts (Level AAA 2.1 only) |
Does not support |
Users are not currently warned of timeouts |
|
2.3.2 Three Flashes (Level AAA) |
Supports |
Nothing on Humap flashes three times in a second unless it has been uploaded by a client or user |
|
2.3.3 Animation from Interactions (Level AAA 2.1 only) |
Does not support |
Motion animation, while subtle, cannot be disabled. |
|
2.4.8 Location (Level AAA) |
Supports |
Titles, navigational components and visual cues identify the location of the user within the application. |
|
2.4.9 Link Purpose (Link Only) (Level AAA) |
Partially supports |
Links are usually understandable by their inner content. |
|
2.4.10 Section Headings (Level AAA) |
Partially supports |
A clear hierarchy of section headings is in effect, but are sometimes inconsistent |
|
2.5.5 Target Size (Level AAA 2.1 only) |
Partially supports |
Most targets are larger than 44x44px but there are some exceptions. |
|
2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 only) |
Partially supports |
User-generated content, the wizard and the majority of the tray support multiple input modalities. The map sometimes requires the use of a mouse. |
|
3.1.3 Unusual Words (Level AAA) |
Partially supports |
Supporting content aims to use common language for explanatory and interactive content. Some presentational language is not explained (e.g. ‘taxonomy’) |
|
3.1.4 Abbreviations (Level AAA) |
Supports |
The platform does not use acronyms or abbreviations. |
|
3.1.5 Reading Level (Level AAA) |
Partially supports |
The platform itself aims at a reading level of 10 years old (validated by user testing). User-generated content will not adhere to this. |
|
3.1.6 Pronunciation (Level AAA) |
Does not support |
There is no mechanism to guide pronunciation |
|
3.2.5 Change on Request (Level AAA) |
Supports |
There are no parts of the platform which change without user input. |
|
3.3.5 Help (Level AAA) |
Partially supports |
The wizard includes context-sensitive help on-screen; there are areas of the application which do not provide contextual help. |
|
3.3.6 Error Prevention (All) (Level AAA) |
Partially supports |
All user-generated content is subject to basic validation checks, and opportunities for correction are provided. It is possible to input nonsensical but valid data, which would not be identified. |
Legal Disclaimer
This report is a good-faith, best-effort representation of the Humap platform’s accessibility conformance at the date of testing. It does not imply future support for any features or functionalities, and must not be relied upon as part of any contract.
Accessibility Conformance Report WCAG Edition
(Based on VPAT® Version 2.4Rev)
Name of Product/Version: Humap Platform
Report Date:
Product Description: Interactive map platform Contact Information: team@humap.me Notes:
The Humap platform includes significant quantities of User-generated (third-party) content which are not in scope for this assessment.
Evaluation Methods Used:
This review of the Humap platform has been undertaken by the Humap team in collaboration with external consulting parties, and users in a controlled test environment. The review has been conducted on desktop devices with and without assistive technologies. The Humap platform supports mobile devices with the same degree of functionality, and it is anticipated that this conformance report will be applicable to that scenario.
The scope of this review includes all pieces of functionality which are core to the Humap platform experience, but does not include reference to content which Humap’s clients have produced (“user-generated content”).
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
|
Standard/Guideline |
Included In Report |
|
Level A Level AA Level AAA |
|
|
Level A Level AA Level AAA |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the
- Does Not Support: The majority of product functionality does not meet the
- Not Applicable: The criterion is not relevant to the
- Not Evaluated: The product has not been evaluated against the This can be used only in WCAG 2.0 Level AAA.
Additional terms used in this document include:
- User generated content (or UGC): this is content which is created by an administrator or end-user of the Humap platform
- Instance: a website and map hosted on the Humap platform. Humap is a multi-tenant environment which uses the same code to provide multiple websites.
- The map: the portion of the application which is presented as a digital map, which can be moved and zoomed
- The tray: the portion of the application which is presented as a web page, showing text, images, links, forms and calls-to-action
- The gallery: the portion of the application which presents images, videos, audio, deep-zoom and other rich media content
Table 1: Success Criteria, Level A
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.1.1 Non-text Content (Level A) |
Supports |
Non-text content is routinely supplemented with alt and ARIA attributes. User-generated content has the facility to annotate any non-text content.
Most of the relevant images on Humap have alt-text or indications of purpose in the mark. |
|
|
Support |
The Humap platform does not require the use of audio or video. User-generated content may include these, and users are encouraged to provide alternatives. |
|
1.2.2 Captions (Prerecorded) (Level A) |
Supports |
There is no live audio or video content required on the platform. User-generated content may include these, and users are encouraged to provide captions as appropriate. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) |
Supports |
The platform has alternatives for every piece of media required by the application. User-generated content is encouraged to have alternatives. |
|
1.3.1 Info and Relationships (Level A) |
Supports |
Content is presented in a visual hierarchy which also conforms to meaningful HTML elements which can be inferred using assistive technologies. |
|
1.3.2 Meaningful Sequence (Level A) |
Supports |
The sequence of content on the page is represented in order in the markup, and will be read appropriately by assistive technology. |
|
1.3.3 Sensory Characteristics (Level A) |
Supports |
All content is accessible using multiple sensory characteristics. Where functionality such as colour is used as the primary characteristic, the platform makes use of alternatives such as graphic icons and patterns to complement this. No primary navigational components or user actions rely on the use of a single sensory characteristic. |
|
1.4.1 Use of Color (Level A) |
Supports |
Where colour is used as the dominant mode of differentiation, alternatives such as assistive tags or patterns are also applied. |
|
1.4.2 Audio Control (Level A) |
N/A |
No audio on Humap plays automatically. |
|
2.1.1 Keyboard (Level A) |
Partially |
For text-centric and form-centric content, keyboard tab order is supported. For the map, providing correct keyboard tab order is work-in-progress.
There will be some activities on the map which will be difficult to accomplish with only keyboard access, but where this is the case, content is also available in a traditional form in the tray.
An end-user cannot move the map with just the cursor without clicking on it first. All content on the map can be accessed from the information tray via keyboard shortcuts. |
|
2.1.2 No Keyboard Trap (Level A) |
Partially |
Where the user is navigating content in the tray, there is no Keyboard trap. Tab order for the map is a work in progress - see 2.1.1. |
|
2.1.4 Character Key Shortcuts (Level A 2.1 only) |
Partially |
The tray is fully accessible via keyboard shortcuts, but the map is not. |
|
2.2.1 Timing Adjustable (Level A) |
Supports |
There are no time limits on Humap |
|
2.2.2 Pause, Stop, Hide (Level A) |
Supports |
Scrolling is controlled entirely by the end-user. This includes auto-updating; the information tray returns results with an infinite scroll, but the user is in full control of the scroll action. |
|
2.3.1 Three Flashes or Below Threshold (Level A) |
Supports |
Nothing in the Humap design flashes. |
|
2.4.1 Bypass Blocks (Level A) |
N/A |
Tab order is used to allow end-users the ability to bypass blocks of repeated content. See 2.1.1. |
|
2.4.2 Page Titled (Level A) |
Supports |
Pages have titles which confer their use and position in the information hierarchy |
|
2.4.3 Focus Order (Level A) |
Partially |
The cursor is clear, icons light up when selected, the box around content that appears when the tab key is being used is visible. |
|
2.4.4 Link Purpose (In Context) (Level A) |
Supports |
Most links in the application convey their meaning through text. |
|
2.5.1 Pointer Gestures (Level A 2.1 only) |
Supports |
No functionality requires the use of multi-point or specific pointer gestures. Where multi-point gestures are supported (zooming and panning on the map) there are dedicated keyboard-accessible controls to accompany them. |
|
2.5.2 Pointer Cancellation (Level A 2.1 only) |
Supports |
Where actions are tied to a click, the onClick event is used, which supports pointer cancellation. |
|
2.5.3 Label in Name (Level A 2.1 only) |
Partially supports |
The majority of actions are labelled appropriately |
|
2.5.4 Motion Actuation (Level A 2.1 only) |
N/A |
There is no motion-activated functionality |
|
3.1.1 Language of Page (Level A) |
Partially |
The platform supports internationalised content and will automatically switch to the user’s browser locale if this feature is enabled. |
|
3.2.1 On Focus (Level A) |
Supports |
Events which trigger on a focus change don’t happen in the application - a click (or equivalent) is needed. |
|
3.2.2 On Input (Level A) |
Supports |
No changes are triggered as the result of content input, except for browser-side validation which is indicated in advance. |
|
3.3.1 Error Identification (Level A) |
Supports |
Errors are presented appropriately in all cases. |
|
3.3.2 Labels or Instructions (Level A) |
Supports |
All inputs have an associated label which explains their purpose. In some cases this is extended with exemplar placeholder content. |
|
4.1.1 Parsing (Level A) |
Supports |
Markup is only parsed for security purposes, and ensures the end content is free of duplicate IDs and similar. |
|
4.1.2 Name, Role, Value (Level A) |
Partially |
The majority of controls are native and so naturally have their name, role and value associated. Where custom controls have been developed, they largely support this. |
Table 2: Success Criteria, Level AA
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.2.4 Captions (Live) (Level AA) |
N/A |
No live content is used on Humap |
|
1.2.5 Audio Description (Prerecorded) (Level AA) |
Supports |
Where videos are uploaded as user generated content, there is provision for a transcript, and supporting information for users suggests the use of audio description. |
|
1.3.4 Orientation (Level AA 2.1 only) |
Supports |
The application scales and changes shape to fit either a wide or tall orientation, across mobile and desktop. |
|
1.3.5 Identify Input Purpose (Level AA 2.1 only) |
Partially supports |
In almost all cases, inputs conform to their standard uses (e.g. select elements for selection). Where special uses of standard inputs are used, we accompany them with ARIA labels. |
|
1.4.3 Contrast (Minimum) (Level AA) |
Partially supports |
The core design of Humap includes attention to minimum contrast. |
|
1.4.4 Resize text (Level AA) |
Partially supports |
The application supports changing the size of text |
|
1.4.5 Images of Text (Level AA) |
Supports |
There are no images of text in the application |
|
1.4.10 Reflow (Level AA 2.1 only) |
Partially supports |
Most content is accessible without scrolling in 2 dimensions with the exception of images in the gallery. The map requires scrolling in 2 dimensions for the purposes of finding a new location. |
|
1.4.11 Non-text Contrast (Level AA 2.1 only) |
Partially supports |
The application does not use low-contrast non-text elements. User-generated content may include this. |
|
1.4.12 Text Spacing (Level AA 2.1 only) |
Supports |
Text spacing is commensurate with the size of the text. |
|
1.4.13 Content on Hover or Focus (Level AA 2.1 only) |
Supports |
No Humap content is accessible only on hover - where hover states are used they are supplementary to a click or other means of access. |
|
2.4.5 Multiple Ways (Level AA) |
Supports |
With the exception of the wizard, which is a linear process, there are multiple ways to access all content. |
|
2.4.6 Headings and Labels (Level AA) |
Partially supports |
Headings and labels confer their use throughout the application. Some user generated content may not conform to this. |
|
2.4.7 Focus Visible (Level AA) |
Partially supports |
A cursor or a highlight is visible in most of the application. |
|
3.1.2 Language of Parts (Level AA) |
Supports |
The application supports internationalisation, and a given page will indicate its human language using metadata. |
|
3.2.3 Consistent Navigation (Level AA) |
Supports |
Navigation is standardised for a given part of the application. |
|
3.2.4 Consistent Identification (Level AA) |
Supports |
Content throughout the site is consistently identified - records, collections, wizard etc. |
|
3.3.3 Error Suggestion (Level AA) |
Supports |
Errors in creating content via UGC and through the content management system are returned via text |
|
N/A |
Not relevant |
|
|
4.1.3 Status Messages (Level AA 2.1 only) |
Partially supports |
Largely the user is provided with a status message when they complete an activity or interaction, through page elements which identify themselves as showing status. |
Table 3: Success Criteria, Level AAA
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.2.6 Sign Language (Prerecorded) (Level AAA) |
N/A |
The application includes no elements which require sign language, although it is possible for user generated content to include it if necessary. |
|
1.2.7 Extended Audio Description (Prerecorded) (Level AAA) |
N/A |
The application includes no elements which require extended audio description. |
|
1.2.8 Media Alternative (Prerecorded) (Level AAA) |
N/A |
The application includes no media which requires alternatives; user generated content on the site may well require alternatives, which are encouraged but not enforced. |
|
1.2.9 Audio-only (Live) (Level AAA) |
N/A |
The application includes no media which requires alternatives; user generated content on the site may well require alternatives, which are encouraged but not enforced. |
|
1.3.6 Identify Purpose (Level AAA 2.1 only) |
Partially supports |
Most interactive elements are self-identifying because they use browser primitives (e.g. form elements). Where higher-level components have been constructed, some have ARIA identification or similar. |
|
1.4.6 Contrast (Enhanced) (Level AAA) |
Partially supports |
A specific ‘high contrast’ mode is not available in the platform, but text and most actions have a contrast approaching 7:1. UGC may have lower contrast. |
|
1.4.7 Low or No Background Audio (Level AAA) |
N/A |
There is no background audio on Humap |
|
1.4.8 Visual Presentation (Level AAA) |
Partially supports |
Text can be zoomed, but background and foreground elements cannot be selected independently |
|
1.4.9 Images of Text (No Exception) (Level AAA) |
Partially supports |
There are no images of text on the platform. UGC may contain images of text. |
|
2.1.3 Keyboard (No Exception) (Level AAA) |
Partially supports |
Everything in the tray and wizards can be accessed using a keyboard. The map has areas which are not accessible by keyboard alone. |
|
2.2.3 No Timing (Level AAA) |
Supports |
Only nonessential visual effects have a timed component - for example the opening of a page element. All timed events end with the item of reference being in view. |
|
2.2.4 Interruptions (Level AAA) |
Supports |
Interruptions can be postponed or suppressed by the user, except interruptions involving an urgent message. |
|
2.2.5 Re-authenticating (Level AAA) |
Partially supports |
Only applicable to UGC. The wizard supports saving as draft, however should a session timeout occur the user will lose the data on the page they were on. |
|
2.2.6 Timeouts (Level AAA 2.1 only) |
Does not support |
Users are not currently warned of timeouts |
|
2.3.2 Three Flashes (Level AAA) |
Supports |
Nothing on Humap flashes three times in a second unless it has been uploaded by a client or user |
|
2.3.3 Animation from Interactions (Level AAA 2.1 only) |
Does not support |
Motion animation, while subtle, cannot be disabled. |
|
2.4.8 Location (Level AAA) |
Supports |
Titles, navigational components and visual cues identify the location of the user within the application. |
|
2.4.9 Link Purpose (Link Only) (Level AAA) |
Partially supports |
Links are usually understandable by their inner content. |
|
2.4.10 Section Headings (Level AAA) |
Partially supports |
A clear hierarchy of section headings is in effect, but are sometimes inconsistent |
|
2.5.5 Target Size (Level AAA 2.1 only) |
Partially supports |
Most targets are larger than 44x44px but there are some exceptions. |
|
2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 only) |
Partially supports |
User-generated content, the wizard and the majority of the tray support multiple input modalities. The map sometimes requires the use of a mouse. |
|
3.1.3 Unusual Words (Level AAA) |
Partially supports |
Supporting content aims to use common language for explanatory and interactive content. Some presentational language is not explained (e.g. ‘taxonomy’) |
|
3.1.4 Abbreviations (Level AAA) |
Supports |
The platform does not use acronyms or abbreviations. |
|
3.1.5 Reading Level (Level AAA) |
Partially supports |
The platform itself aims at a reading level of 10 years old (validated by user testing). User-generated content will not adhere to this. |
|
3.1.6 Pronunciation (Level AAA) |
Does not support |
There is no mechanism to guide pronunciation |
|
3.2.5 Change on Request (Level AAA) |
Supports |
There are no parts of the platform which change without user input. |
|
3.3.5 Help (Level AAA) |
Partially supports |
The wizard includes context-sensitive help on-screen; there are areas of the application which do not provide contextual help. |
|
3.3.6 Error Prevention (All) (Level AAA) |
Partially supports |
All user-generated content is subject to basic validation checks, and opportunities for correction are provided. It is possible to input nonsensical but valid data, which would not be identified. |
Legal Disclaimer
This report is a good-faith, best-effort representation of the Humap platform’s accessibility conformance at the date of testing. It does not imply future support for any features or functionalities, and must not be relied upon as part of any contract.