WCAG Break Down
The breakdown of how the CrowdComms Front End application scores against the Web Content Accessibility 2.1
| Web Content Accessibility Guidelines (WCAG) 2.1 | ||
| WCAG Requirements | Current CC Platform build complaint with standards | Notes |
| 1.Perceivable | Partial | Braille not supported, as each app is custom built we cant confirm the FE support users with issues relating to seeing colour/s or colour blindness. |
| 1.1Text Alternatives | Yes | |
| 1.1.1Non-text Content | Yes | |
| 1.2Time-based Media | No | As each app is custom built we cant confirm the FE media will also be replicated with alternative prerecorded audio/video only content. As each app is custom built we cannot control whether media content has cleary audio or prevent media with multiple voices speaking simultaneously on it. As each app is custom built we cannot control if media supports sign language when played. |
| 1.2.1Audio-only and Video-only (Prerecorded) | No | As each app is custom built we cant confirm the FE media will also be replicated with alternative prerecorded audio/video only content. |
| 1.2.2Captions (Prerecorded) | No | As each app is custom built we cant confirm the FE media will contain captions supports sign language. |
| 1.2.3Audio Description or Media Alternative (Prerecorded) | No | As each app is custom built we cant confirm the FE media will have audio description. |
| 1.2.4Captions (Live) | No | As each app is custom built we cant confirm the FE media will have captions. |
| 1.2.5Audio Description (Prerecorded) | No | As each app is custom built we cant confirm the FE media will have audio description. |
| 1.2.6Sign Language (Prerecorded) | No | As each app is custom built we cant confirm the FE media will have sign language. |
| 1.2.7Extended Audio Description (Prerecorded) | No | As each app is custom built we cant confirm the FE media will have audio description. |
| 1.2.8Media Alternative (Prerecorded) | No | As each app is custom built we cant confirm the FE media will have audio description or sign language. |
| 1.2.9Audio-only (Live) | No | As each app is custom built we cant confirm the FE media will have audio description or sign language. |
| 1.3Adaptable | Yes | |
| 1.3.1Info and Relationships | No | As each app is custom built we cant ensure text font, colour, spacing, blank spaces, paragraphs or size is appropriate. |
| 1.3.2Meaningful Sequence | No | As each app is custom built we cant ensure data present is in an appropriate sequence. |
| 1.3.3Sensory Characteristics | No | As each app is custom built we cant ensure content shape or location will allow all users to understand the data being presented. |
| 1.3.4Orientation | Yes | |
| 1.3.5Identify Input Purpose | Partial | All user input fields on a standard CC product are clear in what the content should be and have alternative text available for screen readers. |
| 1.3.6Identify Purpose | No | As each app is custom built we cant confirm content or symbols will be appropriate for all users to understand. Basic product layout is the same in most cases but nothing prevents clients from changing layouts, moving content, hiding content or adjusting it's selectability. |
| 1.4Distinguishable | Yes | |
| 1.4.1Use of Color | Yes | |
| 1.4.2Audio Control | Yes | |
| 1.4.3Contrast (Minimum) | No | As each app is custom built we cant confirm that text or images of text have a contract ratio of 4:5:1. |
| 1.4.4Resize text | Yes | FE is responsive, adjusting to reflect screen size so if a user zooms into an app the screen adjusts to correctly display the content in its adjusted size. |
| 1.4.5Images of Text | No | As each app is custom built we cant ensure text font, colour, spacing, blank spaces, paragraphs or size is appropriate. |
| 1.4.6Contrast (Enhanced) | No | As each app is custom built we cant confirm that text or images of text have a contract ratio of 7:1 |
| 1.4.7Low or No Background Audio | No | As each app is custom built we cant confirm the FE media will not have background audio. |
| 1.4.8Visual Presentation | Partial | FE is responsive, adjusting to reflect screen size so if a user zooms into an app the screen adjusts to correctly display the content in its adjusted size. Foreground and background colours are not selectable by each individual user, only the admin for the application. |
| 1.4.9Images of Text (No Exception) | No | As each app is custom built we cant confirm images of text will only be for decorative purposes. |
| 1.4.10Reflow | No | As the FE is responsive the CSS height and width is adjusts to reflect screen size changes without any limits of minimum/maximum pixel size. Content is repsonsive as a percentage of the screen and no defined by pixel count. |
| 1.4.11Non-text Contrast | Yes | |
| 1.4.12Text Spacing | No | As each app is custom built we cant ensure textspacing, blank spaces, paragraphs or size is appropriate. |
| 1.4.13Content on Hover or Focus | Partial | Most selectable content on a standard app version has a hoover alternative state. |
| 2.Operable | Partial | |
| 2.1Keyboard Accessible | Yes | |
| 2.1.1Keyboard | Yes | |
| 2.1.2No Keyboard Trap | Yes | |
| 2.1.3Keyboard (No Exception) | Partial | Embedded content such as Video Library videos cant be selected via a keyboard only. |
| 2.1.4Character Key Shortcuts | No | |
| 2.2Enough Time | Yes | |
| 2.2.1Timing Adjustable | Partial | As each app is custom built we cant ensure users will have enough time to view media content before the media progresses although there are pause options available. |
| 2.2.2Pause, Stop, Hide | Yes | |
| 2.2.3No Timing | Yes | |
| 2.2.4Interruptions | Partial | |
| 2.2.5Re-authenticating | Partial | |
| 2.2.6Timeouts | No | No warning is displayed before user logout currently. |
| 2.3Seizures and Physical Reactions | No | As each app is custom built we cant ensure content will not contain flashing images or induce physical reactions. |
| 2.3.1Three Flashes or Below Threshold | Yes | |
| 2.3.2Three Flashes | Yes | |
| 2.3.3Animation from Interactions | No | No functionality yet built around giving the users the option to prevent animation or integration including preventing screen scrolling or dynamic movement of menu bars. |
| 2.4Navigable | Partial | FE can be navigated via keyboard, mouse and on native touch screen devices. No instructions on basica navigation actions are provided in a standard FE app. |
| 2.4.1Bypass Blocks | Partial | The Navigation menu bar is collapable but still provides user access to select modules. The User menu bar is only displayed when selected by the user and disappears when a user selects another location within the FE application |
| 2.4.2Page Titled | All modules and user menu options have a title within the head section but moduals and pop ups don’t. The app has the ability to direct users to other pages or iframe content which may not have a title within the head section. Documents and lists that can populate the page are custom built so we cant ensure titles of such content will be provided. |
|
| 2.4.3Focus Order | Yes | |
| 2.4.4Link Purpose (In Context) | No | As each app is custom built we cant ensure all links are in context and named appropriatley. |
| 2.4.5Multiple Ways | No | As each app is custom built we cant ensure all pages are linked to each other directly and not appariate for an interactive application rathe than a web site. |
| 2.4.6Headings and Labels | Yes | |
| 2.4.7Focus Visible | Yes | |
| 2.4.8Location | Partial | FE supports the use of the back button in the app and most builds of the application leave the user navigation bar present which can be selected from any module however as each app is custom built we cant ensure all apps built follow this model. |
| 2.4.9Link Purpose (Link Only) | Yes | |
| 2.4.10Section Headings | No | As each app is custom built we cant ensure all pages have sub headers where appropriate. |
| 2.5Input Modalities | Yes | |
| 2.5.1Pointer Gestures | Yes | |
| 2.5.2Pointer Cancellation | No | There is no functionality to perform a pointer selection cancellation or alter user selection within the FE app. |
| 2.5.3Label in Name | No | As each app is custom built we cant ensure labels are appropriate for their content. |
| 2.5.4Motion Actuation | No | Not applicable. |
| 2.5.5Target Size | No | As each app is custom built we cant ensure target size is a minimum of 44 CSS pixels. |
| 2.5.6Concurrent Input Mechanisms | Yes | |
| 3.Understandable | Partial | |
| 3.1Readable | Yes | |
| 3.1.1Language of Page | Yes | |
| 3.1.2Language of Parts | Yes | |
| 3.1.3Unusual Words | No | As each app is custom built we cant ensure what words are used or if there is any dictionary or jargon buster present on the FE app. |
| 3.1.4Abbreviations | No | As each app is custom built we cant ensure what abbreviations are used or if there is any dictionary or jargon buster present on the FE app. |
| 3.1.5Reading Level | Yes | |
| 3.1.6Pronunciation | Yes | |
| 3.2Predictable | Yes | |
| 3.2.1On Focus | Yes | |
| 3.2.2On Input | Yes | |
| 3.2.3Consistent Navigation | Yes | |
| 3.2.4Consistent Identification | Yes | |
| 3.2.5Change on Request | Yes | |
| 3.3Input Assistance | Partial | As each app is custom built we cant ensure all fields a user can update have error identification details but all user profile fields that are as standard have error identification details. |
| 3.3.1Error Identification | Yes | |
| 3.3.2Labels or Instructions | No | As each app is custom built we cant ensure labels or instructions are present for all user inputs. |
| 3.3.3Error Suggestion | Partial | As each app is custom built we cant ensure all errors present suggestions but in the standard build of the application all login failures, failed save attempts and user profile update failures indicate a reason for the error. |
| 3.3.4Error Prevention (Legal, Financial, Data) | No | As each app is custom built we cant ensure user submissions are revisable, checked or reversible. |
| 3.3.5Help | No | |
| 3.3.6Error Prevention (All) | No | As each app is custom built we cant ensure user submissions are revisable, checked or reversible. |
| 4.Robust | Yes | |
| 4.1Compatible | Yes | |
| 4.1.1Parsing | Yes | |
| 4.1.2Name, Role, Value | Yes | |
| 4.1.3Status Messages | Partial | Chat messages, alerts and video calls display an icon change. Hoovering and selecting items usually results in a change in icon colour or its container box change of colour. As each app is custom built we cant ensure these standards are maintained in all builds. |
| 5.Conformance | No | As each app is custom built we cant ensure conformance standards are met or that a user cant be directed from the FE app to a none conformance location. |
| 5.1Interpreting Normative Requirements | No | As each app is custom built we cant ensure normatative standards are maintained. |
| 5.2Conformance Requirements | No | As each app is custom built we cant ensure confirmation standards are maintained. |
| 5.2.1Conformance Level | No | As each app is custom built we cant ensure confirmation standards are maintained. |
| 5.2.2Full pages | Yes | |
| 5.2.3Complete processes | Yes | |
| 5.2.4Only Accessibility-Supported Ways of Using Technologies | Yes | |
| 5.2.5Non-Interference | Yes | |
| 5.3Conformance Claims (Optional) | No | No functionality to support conformance claims. |
| 5.3.1Required Components of a Conformance Claim | No | No functionality to support conformance claims. |
| 5.3.2Optional Components of a Conformance Claim | No | No functionality to support conformance claims. |
| 5.4Statement of Partial Conformance - Third Party Content | No | As each app is custom built we cant ensure a statement of conformance with third party content is displayed. |
| 5.5Statement of Partial Conformance - Language | No | As each app is custom built we cant ensure a statement of conformance with language is visible or required as users can make the FE operate in multiple languages making a statement redundant. |