Advice and answers from the Tribal Habits Team

How does Tribal Habits help meet Web Content Accessibility Guidelines (WCAG)?

Tribal Habits aims for WCAG 2.1 guidelines at Level AA. Meeting these guidelines requires a combination of our platform and your content.
Written by David King
Updated 8 months ago

Tribal Habits aim to allow all explorers/learners to fully interactive with the platform and knowledge which is captured and shared within it. As such, we have built the Tribal Habits platform so support Web Content Accessibility Guidelines (WCAG).  

Tribal Habits aims for WCAG 2.1 guidelines at Level AA. Meeting these guidelines requires a combination of our platform and your content. Outlined below we review each of the success criteria for Level A and Level AA under WCAG 2.1. We provide details on how Tribal Habits meets the requirements and we outline the steps you should take, where required, to meet those guidelines.

Tribal Habits is independently audited every 12 months to measure our success against Level A and Level AA criteria.

Are you finding something is not accessible?

Meeting accessibility guidelines is an on-going process. If you find an aspect of our platform which you feel does not meet WCAG 2.1 Level AA standards, please contact support@tribalhabits.com

While we are constantly reviewing our platform against these guidelines, there can be moments when browser technology changes (e.g. a new version of a web browser changes the interaction standards) or we inadvertently hinder accessibility in a new feature or code update and don’t pick up that issue in our testing.  

We are very responsive to these issues and can usually update the platform rapidly to address any useability or accessibility errors.

Level A Success Criteria

1.1.1 Non-text Content (Level A) - Supported

  • What we do: All controls and inputs have a name which describes their purpose. For time-based media such as Narrations and Video, both captions and transcripts are supported. We have make decorative non-text content as such so it can be ignored by assistive technology. All built-in images include descriptive identification. All user-created images have fields for descriptive identification
  • What you need to do: Ensure that any images you upload include a clear description in the descriptive field. Ensure that any text in any images (such as flow charts or graphs) is fully described in other text elements or the descriptive field. Ensure that you enable transcripts on Narrations, upload a transcript for Video and Audio elements, and request captions on any uploaded videos.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A) – Supported

  • What we do: For time-based media such as Narrations and Video, both captions and transcripts are supported. The File element may be used to upload transcripts for Video and audio elements.
  • What you need to do: Ensure that you enable transcripts on Narrations, upload a transcript for Video and Audio elements, and request captions on any uploaded videos

1.2.2 Captions (Prerecorded) (Level A) – Supported 

  • What we do: Narrations provided automatic captions. Videos support captions. 
  • What you need to do: Provide captions for your Video element to our Support team to sync with your video, or request that we create captions for your Videos.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) – Supported 

  • What we do: Narrations can provide automatic transcripts. Transcripts for Video elements can be added via text or the File element.
  • What you need to do: Enabled transcripts for Narration elements. Provide a transcript for Video elements in text or via an upload in the File element.

1.3.1 Info and Relationships (Level A) – Supported 

  • What we do: All elements and content in Tribal Habits are designed in a way that their information, structure and relationships can be programmatically determined. We have also added additional screen reader text with ‘how to’ instructions for each interactive element.
  • What you need to do: Ensure that your content is well labelled. If you use a table in a Text element, then use table headings. Provide meaningful titles to your Section elements. If you use the Hotspot element, ensure that the Hotspot text for each marker includes a heading.

1.3.2 Meaningful Sequence (Level A)– Supported 

  • What we do: All elements are presented in lists and announced as lists. Section Headers with automatic numbering can be enabled. Focus is given to all interactive elements.
  • What you need to do:  We recommend enabling Section Headers to improve the navigation experience for all users. 

1.3.3 Sensory Characteristics (Level A) – Supported

  • What we do: All interactive elements avoid using only shape, size, visual location, orientation or sound for instructions. All interactive elements contain additional screen-reader text with detailed instructions. 
  • What you need to do: Ensure your questions or instructions for interactive elements clearly outline what you want explorers to do or how you expect them to answer.

1.4.1 Use of Color (Level A) – Supported 

  • What we do: No important information or instructions are provided only with colour. All buttons include icons or text. Where colour changes are used, they are accompanied by changes in icons or text. All text contrast for all content generated in the platform is either 3:1 (large-scale text in some instances) or 4.5:1 (all other text).
  • What you need to do: Ensure that any uploaded images do not rely on colour alone to convey information (e.g. highlighting parts of an image with colour only). Use icons, text or patterns in uploaded images to highlight important information. Do not use light coloured text in any editable text element.

1.4.2 Audio Control (Level A) – Supported 

What we do: All Narration, Video and Audio elements have built-in controls for play/pause and volume controls.

2.1.1 Keyboard (Level A) – Supported

What we do: All aspects of the explorer/learner experience are keyboard-accessible. This includes all interactive elements.

2.1.2 No Keyboard Trap  (Level A) – Supported

What we do: All aspects of the explorer/learner experience don’t trap keyboard focus in subsections of content. You can use the keyboard navigation without getting stuck.

2.1.4 Character Key Shortcuts (Level A) – Not Applicable 

Keyboard shortcuts are not used in Tribal Habits.

2.2.1 Timing Adjustable (Level A) – Supported

What we do: There are no time limited activities or interactions in Tribal Habits.

2.2.2 Pause, Stop, Hide (Level A) – Supported

What we do: All Narration, Video and Audio elements have built-in controls for play/pause.

2.3.1 Three Flashes or Below Threshold (Level A) – Supported

  • What we do: There are no elements in Tribal Habits which blink or flash more than three times per second.
  • What you need to do: Ensure that any uploaded Video (or animated-gif) does not contain content which blinks or flashes more than three times per second.

2.4.1 Bypass Blocks (Level A) – Supported

What we do: Explorers/learners can tab between interactive elements and Section Headers (when enabled), plus various other focus elements, to move quickly through a topic when using a screen reader to avoid any repetitive information. Explorers/learners will be held at checkpoints when an interactive element has not been completed for the first time, but this is not repeated content and is required to be completed as the explorer/learner progresses.

2.4.2 Page Titled (Level A) – Supported

What we do: Each screen is Tribal Habits is automatically titled with a relevant title and is the first object in the tab order.

2.4.3 Focus Order (Level A) – Supported

  • What we do: Content within a topic is presented in a linear order with use of numbered Section Headers which can be tabbed to (when enabled). 
  • What you need to do: Enable Section Headers in your topic.

2.4.4 Link Purpose (In Context) (Level A) – Supported

  • What we do: All built-in buttons contain screen reader text to clarify their use. All elements which allow hyperlinked text have a dedicated Link button to allow an embedded URL.
  • What you need to do: Explain any hyperlinks you create in text elements. Either use the Link button to paste the URL onto text which clearly explains the purpose of that text OR paste in the URL and then provide a clear text explanation of that link.

2.5.1 Pointer Gestures (Level A) – Supported 

What we do: Tribal Habits supports touchscreen gestures, although explorers/learners are not required to use them.

2.5.2 Pointer Cancellation (Level A) – Supported

What we do: Click events happen when learners release the mouse button, not when they press the mouse button down. This helps learners recover if they accidentally click the wrong target. They can move the mouse away from the target before releasing the button if they don’t want to activate the target.

2.5.3 Label in Name (Level A) – Supported

What we do: All alternative text for screen readers matches on-screen labels.

2.5.4 Motion Actuation  (Level A 2.1 only) – Not applicable

Tribal Habits does not support motion controls.

3.1.1 Language of Page (Level A) – Supported

What we do: A language identifier (English) it automatically added to the published output for screen readers.

3.2.1 On Focus (Level A) – Supported

What we do: Tribal Habits topics do not change context when an explorer/learner changes focus.

3.2.2 On Input (Level A) – Supported

What we do: All ‘submit’ buttons in interactive content clearly explain what will happen before an action that changes context. Button labels are dynamic to reflect chosen settings for interactive elements.

3.3.1 Error Identification (Level A) – Supported

What we do: Tribal Habits automatically warns explorers/learners when they fail to complete an interaction and attempt to continue.

3.3.2 Labels or Instructions (Level A) – Supported

What we do: Interactive elements provide instructions to explain the interaction. Data-entry fields contain prompts to explain the data required.
What you need to do: When using the Q&A element, clearly explain what you require from the explorer/learner in the Question field.

4.1.1 Parsing (Level A) – Supported

What we do: Tribal Habits generated well-formatted HTML output. All custom Javascript is properly formatted.

4.1.2 Name, Role, Value (Level A) – Supported

  • What we do: All objects are labelled correctly. For interactive elements, additional screen reader instructions are provided in the header for each element which can be tabbed to (focus point). All images in all elements have fields for alternative descriptive text.
  • What you need to do: Ensure all images you upload in any element have clear descriptive text for screen readers.

Level AA Success Criteria

1.2.4 Captions (Live) (Level AA) – Not applicable

Tribal Habits does not use real-time broadcasts.

1.2.5 Audio Description (Prerecorded) (Level AA) – Supported

  • What we do: Narrations can include automatic transcriptions. The File element can be used to upload a transcript for Video and Audio elements.
  • What you need to do: Enable transcripts in Narrations. Upload suitable transcripts for Video and Audio elements.

1.3.4 Orientation (Level AA) – Supported

What we do: Tribal Habits is fully responsive to any screen size or device. It works in both landscape and portrait mode. On very small devices such as mobiles, we recommend landscape viewing for the best experience. 

1.3.5 Identify Input Purpose (Level AA) – Supported

  • What we do: Tribal Habits does not utilise multi-field forms. Information about the user may be collected as part of exploring a topic in a Poll (list based selection) or Q&A (single field response) element. In both cases, the purpose of the element and any input fields is clearly explained to the user.
  • What you need to do: When using the Poll and Q&A elements, ensure your question is clear and so that the learner/explorer can understand the context of their answer.

1.4.3 Contrast (Minimum) (Level AA) – Supported

  • What we do: All text and elements in Tribal Habits is presented in at least 4.5:1 or higher contrast, or 3:1 or higher contrast for large-scale text.
  • What you need to do: Your organisation’s primary and secondary colours in Tribal Habits must be at least 3:1 colour contrast. Tribal Habits will automatically adjust your organisation’s colour to required contrast ratios from there.

1.4.4 Resize text (Level AA) – Supported 

What we do: Tribal Habits is fully responsive. Explorers/learners can use the browser zoom to scale any topic. We test this against a 400% zoom ratio on a horizontal viewport of 1280 CSS pixels and confirm that all text and functionality is readable and usable, and scrolling is only required in one dimension. 

1.4.5 Images of Text (Level AA) – Supported

  • What we do: All images in any element have a descriptive text field.
  • What you need to do: Avoid uploading images of text. Use Text, Narration or Hotspot elements instead, to present text ‘as text’. If uploading an image with text, clearly explain the text in the descriptive text field.

1.4.10 Reflow (Level AA) – Supported 

What we do: All content in Tribal Habits is presented in a two-dimensional layout which doesn’t require scrolling in either direction. 

1.4.11 Non-text Contrast (Level AA) – Supported

What we do: All buttons and icons in Tribal Habits (and all non-text images created in the platform) are presented in a ratio of at least 3:1 or high.
What you need to do: If uploading an image, ensure that any icons or important information is displayed with a 3:1 contrast ratio against adjacent colours.

1.4.12 Text Spacing (Level AA) – Not applicable 

Tribal Habits topics are not implemented using a mark up language which allows altering of text style properties.

1.4.13 Content on Hover or Focus (Level AA) – Supported

What we do: Tribal Habits does not provide any content in hover only focus. When content is provided in a ‘popup’ (such as in the Hotspot element), that content can be dismissed by a keypress. ‘Popup’ content is persistent until it is dismissed by the explorer/learner. 

2.4.5 Multiple Ways (Level AA) – Supported

What we do: Where appropriate, more than one way is available to locate a web page. Note that most of the content in Tribal Habits is presented for learning and therefore is presented as part of a step or process, which is an allowed exception to this requirement. In such cases, explorers/learners will need to follow the prescribe way.

2.4.6 Headings and Labels (Level AA) – Supported

  • What we do: Tribal Habits uses a variety of built-in headings and labels through-out topics and ensures they are in a meaningful order and can be tabbed to for keyboard navigation and screen readers.
  • What you need to do: Enable Section Headers. When creating Section element, write meaningful titles which explain the purpose of the upcoming section.

2.4.7 Focus Visible (Level AA) – Supported 

What we do: For all elements which can have focus, a rectangle will highlight the object that currently has focus when the explorer/learner uses keyboard navigation (using the browser’s built-in formatting).

3.1.2 Language of Parts (Level AA) – Not applicable

Tribal Habits does not support different languages within a single topic.

3.2.3 Consistent Navigation (Level AA) – Supported

What we do: Tribal Habits is a template based platform. As such, each time the same item or element appears, it always has the same navigation and interaction process. 

3.2.4 Consistent Identification (Level AA) – Supported

What we do: Tribal Habits is a template based platform. As such, each time the same item or element appears, it always has the same identification. 

3.3.3 Error Suggestion (Level AA) – Supported

What we do: When explorers/learners respond incorrectly, we provide feedback so they know what is expected of them.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) – Supported

What we do: Changes to Legal, Financial or Personal Data can be reversed and/or checked and/or confirmed by the user.

4.1.3 Status Messages (Level AA) - Supported

What we do: Status messages do not appear without a change in context.
 

Did this answer your question?