Showbie strives to foster a caring and inclusive community that builds to the needs of all our users. We recognize that we have work to do in order to improve. There are still barriers within our applications that prevent users with disabilities from experiencing all of the features we offer.
To improve the accessibility of our applications, the team at Showbie is taking the following steps:
- We are working with a third-party accessibility firm, Level Access, to provide our team with an official audit of our system and assist our team with prioritization of the highest impact issues for our team to fix.
- We have dedicated resources and focus towards accessibility so that we are able to meet a higher level of compliance sooner.
- We are educating our team and adjusting our processes so that we can maintain accessibility compliance indefinitely even as our products and the requirements change.
- We have conducted a self-assessment of our current level of compliance (see below). We will update this assessment as we receive the official audit results from Level Access, and as we make progress towards compliance.
Feedback is always welcome. We all live different experiences, and our team would appreciate it if you would be willing to share your experiences with us.
If you have questions, concerns, suggestions, or general comments that you would like to share about the accessibility of Showbie, please fill out our accessibility contact form.
Uutilsynet Excel Templates
_WCAG-sjekkliste for utfylling av tilgjengelighetserklæring – Showbie 25.01.23
WCAG-sjekkliste for utfylling av tilgjengelighetserklæring – Showbie.Socrative 30.01.23
WCAG-sjekkliste for utfylling av tilgjengelighetserklæring – Socrative 30.01.23
Accessibility Requirements
The accessibility declaration is an overview over a service’s current assessment of its accessibility. It is based on 47 criteria from the WCAG 2.1 standard.
| Name | Description | Showbie iOS | Showbie Web | Showbie Comment |
| 1.1.1: Non-text Content | Provide text alternatives for non-text content that serves the same purpose. | Yes | Yes | |
| 1.2.1: Audio-only and Video-only (Prerecorded) | Provide an alternative to pre-recorded video-only and audio-only content. | Yes | Not Relevant | No pre-recorded video or audio in product (excludes user generated content) |
| 1.2.2: Captions (Prerecorded) | Provide captions for pre-recorded videos with audio. | Yes | Not Relevant | No pre-recorded video or audio in product (excludes user generated content) |
| 1.3.1: Info and Relationships | Content, structure and relationships can be programmatically determined. | No | No | Throughout most of the application, we do comply however we have work to do in order to meet compliance everywhere in our application. |
| 1.3.2: Meaningful Sequence | Present content in a meaningful order. | Yes | Yes | |
| 1.3.3: Sensory Characteristics | Instructions don’t rely solely on sensory characteristics. | Yes | Yes | |
| 1.3.4: Orientation | Your website adapts to portrait and landscape views. | Yes | Yes | |
| 1.3.5: Identify Input Purpose | The purpose of input fields must be programmatically determinable. | Yes | Yes | |
| 1.4.1: Use of Color | Don’t use presentation that relies solely on color. | No | No | There are a few areas of the application that rely solely on colour, including folder colours, pinned posts, shared vs individual responses. We are looking into a solution for these areas that is apparent through alternative means other than colours. These are minor areas of the application and should not prevent its use. |
| 1.4.2: Audio Control | Don’t play audio automatically. | Not Relevant | Not Relevant | We do not have any areas in the application that play audio. This excludes user generated content, which does not play automatically. |
| 1.4.3: Contrast (Minimum) | Contrast ratio between text and background is at least 4.5:1. | No | No | This is a known issue that we are looking into a holistic design solution to meet this criteria and increase the contrast throughout the application. |
| 1.4.4: Resize text | Text can be resized to 200% without loss of content or function. | No | No | Currently we have not found an effective way to increase the text size or spacing without losing content or function, so increasing text size is not available. This is an area we would like to fix. |
| 1.4.5: Images of Text | Don’t use images of text. | Yes | Yes | |
| 1.4.10: Reflow | Content retains meaning and function without scrolling in two dimensions. | Yes | Yes | |
| 1.4.11: Non-text Contrast | The contrast between user interface components, graphics and adjacent colours is at least 3:1. | No | No | This is a known issue that we are looking into a holistic design solution to meet this criteria and increase the contrast throughout the application. |
| 1.4.12: Text Spacing | Content and function retain meaning when users change elements of text spacing. | Not Relevant | No | Currently we have not found an effective way to increase the text size or spacing without losing content or function, so increasing text size or spacing is not available. This is an area we would like to fix. |
| 1.4.13: Content on Hover or Focus | When hover or focus triggers content to appear, it is dismissible, hoverable and persistent. | Not Relevant | Yes | This functionality is not relevant to iOS applications. |
| 2.1.1: Keyboard | All functionality is accessible by keyboard with no specific timings. | Not Relevant | No | The majority of our application is accessible by keyboard, however our entire application is not. The main area that may suffer loss of functionality is the document previewer. There may be other areas that in the application that do not perform as well. As we make updates to the application, we strive to update and add this functionality wherever possible. |
| 2.1.2: No Keyboard Trap | Users can navigate to and from all content using a keyboard. | Not Relevant | Yes | This functionality is not relevant to iOS applications. |
| 2.1.4: Character Key Shortcuts | Allow users to turn off or remap single-key character shortcuts. | Not Relevant | Not Relevant | We do not have any keyboard shortcuts available. |
| 2.2.1: Timing Adjustable | Provide user controls to turn off, adjust or extend time limits. | Not Relevant | Not Relevant | There is no functionality in the application that is restricted by time. |
| 2.2.2: Pause, Stop, Hide | Provide user controls to pause, stop and hide moving and auto-updating content. | Not Relevant | Not Relevant | We do not have any auto-updating content in our application. |
| 2.3.1: Three Flashes or Below Threshold | No content flashes more than three times per second. | Not Relevant | Not Relevant | We do not have any content flashes in our application. |
| 2.4.1: Bypass Blocks | Provide a way for users to skip repeated blocks of content. | Yes | No | This is not available in all areas of our application, however this functionality is available in our iOS application. |
| 2.4.2: Page Titled | Use helpful and clear page titles. | Yes | Yes | |
| 2.4.3: Focus Order | Components receive focus in a logical sequence. | Yes | Yes | |
| 2.4.4: Link Purpose (In Context) | Every link’s purpose is clear from its text or context. | Yes | Yes | |
| 2.4.5: Multiple Ways | Offer at least two ways to find pages on your website. | Yes | Yes | |
| 2.4.6: Headings and Labels | Headings and labels describe topic or purpose. | Yes | Yes | |
| 2.4.7: Focus Visible | Keyboard focus is visible when used. | Yes | No | This functionality exists throughout most of our application, however we are working towards consistency throughout the application. This functionality is available in our iOS application. |
| 2.5.1: Pointer Gestures | Multi-point and path-based gestures can be operated with a single pointer. | Yes | Yes | |
| 2.5.2: Pointer Cancellation
2.5.3: Label in Name |
Functions don’t complete on the down-click of a pointer. | Yes | Yes | |
| 2.5.4: Motion Actuation | Where a component has a text label, the name of the component also contains the text displayed. | Not Relevant | Not Relevant | We do not have any functions operated by motion in our application. |
| 3.1.1: Language of Page | Functions operated by motion can also be operated through an interface and responding to motion can be disabled. | Yes | Yes | |
| 3.1.2: Language of Parts | Each webpage has a default human language assigned. | Yes | Yes | |
| 3.2.1: On Focus | Elements do not change when they receive focus. | Yes | Yes | |
| 3.2.2: On Input | Elements do not change when they receive input. | Yes | Yes | |
| 3.2.3: Consistent Navigation | Position menus and standard controls consistently. | Yes | Yes | |
| 3.2.4: Consistent Identification | Identify components with the same function consistently. | No | No | As we are currently making design updates in our application, some elements may appear inconsistent, however through our iterative design and development, this is something that we are working towards consistency throughout the application. |
| 3.3.1: Error Identification | Identify and describe input errors for users. | Yes | Yes | |
| 3.3.2: Labels or Instructions | Provide labels or instructions for user input. | Yes | Yes | Label or instructions for user input appear throughout most of the application however there are some outdated areas of the app that we are working to improve consistency in this area. |
| 3.3.3: Error Suggestion | Suggest corrections when users make mistakes. | Yes | Yes | |
| 3.3.4: Error Prevention (Legal, Financial, Data) | Check, confirm and allow reversal of pages that cause important commitments. | Yes | Yes | |
| 4.1.1: Parsing | No major code errors. | Yes | Yes | |
| 4.1.2: Name, Role, Value | Build all elements for accessibility. | Yes | Yes | |
| 4.1.3: Status Messages | Distances between paragraphs, rows, words and characters must be able to be increased to a certain value. | Not Relevant | No | Currently we have not found an effective way to increase the text size or spacing without losing content or function, so increasing text size or spacing is not available. This is an area we would like to fix. |
