WCAG Break Down

TheA breakdownreview of how the CrowdComms Front End application scoresmeasured against the Web Content Accessibility 2.1 2 requirements.

 

 

Largeisnot Iconshavetool

Web Content Accessibility Guidelines (WCAG) 2.12
WCAG Requirements	Current CC Platform build complaint with standards	Notes
1.Perceivable	Partial
1.1Text Alternatives	Partial	Braille not supported, as each app is custom built we cant confirm the FE supportsupports users with issues relating to seeing colour/s or colour blindness.
1.1Textprint Alternatives	Yes	supported but zoom functionality works. "Simpler language" cant be confirmed as app is custom built so the language complexity used cant be defined by CrowdComms but we have the ability to select multiple different languages if the app is required to support them.
1.1.1Non-text Content	Yes	Non text content as text alternatives is possible as html alternate text "alt=" but clients have to specify what the alternate text for the image is otherwise the default is no alternative text. This is to reduce confusion around what the image is designed to express to the reader.
1.2Time-2 Time-based Media	No	As each app is custom built we cant confirm the FE media will also be replicated with alternative prerecordedpre-recorded audio/video only content. As each app is custom built we cannot control whether media content has clearyclear audio 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-1 Audio-only and Video-only (Prerecorded)Pre-recorded)	No	As each app is custom built we cant confirm the FE media will also be replicated with alternative prerecordedpre-recorded audio/video only content. Alternative for time based media could include transcripts added as documents into applications for example but this is upon the requirements of each unique client.
1.2.2Captions2 Captions (Prerecorded)Pre-recorded)	NoPartial	As each app is custom built we cant confirm the FE media will contain captions supports sign language. Video functionality allows for Closed Captions to be generated and stored at the time of video creation but only if the designed requirements of the client specify this functionality is enabled.
1.2.3Audio Description or Media Alternative (Prerecorded)Pre-recorded)	No	As each app is custom built we cant confirm the FE media will have audio description.
1.2.4Captions (Live)	NoPartial	As each app is custom built we cant confirm the FE media will havecontain captions.captions supports sign language. Video functionality allows for Closed Captions to be generated and stored at the time of video creation but only if the designed requirements of the client specify this functionality is enabled.
1.2.5Audio Description (Prerecorded)Pre-recorded)	No	As each app is custom built we cant confirm the FE media will have audio description.
1.2.6Sign6 Sign Language (Prerecorded)Pre-recorded)	No	As each app is custom built we cant confirm the FE media will have sign language.
1.2.7Extended7 Extended Audio Description (Prerecorded)Pre-recorded)	No	As each app is custom built we cant confirm the FE media will have audio description.
1.2.8Media8 Media Alternative (Prerecorded)Pre-recorded)	No	As each app is custom built we cant confirm the FE media will have audio description or sign language.
1.2.9Audio-9 Audio-only (Live)	No	As each app is custom built we cant confirm the FE media will have audio description or sign language.
1.3Adaptable3 Adaptable	Yes	Multiple examples of creating bespoke layouts including multiple templates for module layouts and functionality options.
1.3.1Info1 Info and Relationships	No	As each app is custom built we cant ensure textinformation font,is colour, spacing, blank spaces, paragraphsstructured or sizeprogrammatically isdetermined. App appropriate.creation and app design options have been built in a structured uniformed way to ensure ease of use and intuitive to computer literate users.
1.3.2Meaningful2 Meaningful Sequence	No	As each app is custom built we cant ensure data presentpresented is in an appropriate sequence.
1.3.3Sensory3 Sensory 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.4Orientation4 Orientation	Yes	Orientation is flexible between portrait, landscape and the most common screen size combinations.
1.3.5Identify5 Identify 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. Data input by users such as in a Live Poll can be extracted for data analysis.
1.3.6Identify6 Identify 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.select ability.
1.4Distinguishable4 Distinguishable	Yes
1.4.1Use1 Use of Color	Yes
1.4.2Audio2 Audio Control	Yes
1.4.3Contrast3 Contrast (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.4Resize4 Resize 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.5Images5 Images 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.6Contrast6 Contrast (Enhanced)	No	As each app is custom built we cant confirm that text or images of text have a contract contract  ratio of 7:1
1.4.7Low7 Low or No Background Audio	No	As each app is custom built we cant confirm the FE media will not have background audio. The ability to filter out audio background is not a supported functionality.
1.4.8Visual8 Visual 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 selected as a design feature but not selectable by eachindividual users. Text formatting and layout is based on individual user,design onlyspecifications theso adminunique forto theeach application.build.
1.4.9Images9 Images of Text (No Exception)	No	As each app is custom built we cant confirm confirm  images of text will only be for decorative purposes.
1.4.10Reflow10 Reflow	NoPartial	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 repsonsiveresponsive as a percentage of the screen and no defined by pixel count.
1.4.11Non-11 Non-text Contrast	YesNo	As each app is custom built we cant confirm a non-text contrast ratio of 3:1 would be maintained.
1.4.12Text12 Text Spacing	No	As each app is custom built we cant ensure textspacing,text spacing, blank spaces, paragraphs or size is appropriate.
1.4.13Content13 Content on Hover or Focus	Partial	Most selectable content on a standard app version has a hoover alternative state.
2. Operable	Partial
2.1Keyboard1 Keyboard Accessible	Yes
2.1.1Keyboard1 Keyboard	Yes
2.1.2No2 No Keyboard Trap	Yes
2.1.3Keyboard3 Keyboard (No Exception)	Partial	Embedded content such as Video Library videos and filters cant be selected via a keyboard only.
2.1.4Character4 Character Key Shortcuts	NoN/A	No keyboard shortcuts are implemented.
2.2Enough2 Enough Time	Yes
2.2.1Timing1 Timing Adjustable	PartialN/A	As each appThere is custom built we cant ensure users will have enoughno time tolimit viewfeatures media content beforein the mediaapplication progressesand althoughno thereplans areto pauseimplement optionsany available.time limited based feature.
2.2.2Pause,2 Pause, Stop, Hide	Yes	Alert and pop up displays have a minimum display time of 5 seconds.
2.2.3No3 No Timing	Yes
2.2.4Interruptions4 Interruptions	PartialPlanned	Availability selectable by the user for chat, video meetings, meeting booking, business card exchanges, sound notification and email notification. User does not have the ability to prevent interruptions from Alerts.
2.2.5Re-5 Re-authenticating	PartialYes	Auto Auth token refreshes enable continued service. Connection dropping for external features such as VBO and Zoom calls will require re-authentication but are driven by 3rd party software.
2.2.6Timeouts6 Timeouts	No	No warning is displayed before user logout currently.when 24 hours of continuous login without user input has been reached.
2.3Seizures3 Seizures 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.1Three1 Three Flashes or Below Threshold	Yes
2.3.2Three2 Three Flashes	Yes
2.3.3Animation3 Animation from Interactions	No	No functionality yet built around giving the users the option to prevent animation or integration including preventingalert screenpop scrollingup ornotifications, dynamicicon movementchanges ofupon menuselection bars.etc.
2.4Navigable4 Navigable	Partial	FE can be navigated via keyboard, mouse and on native touch screen devices. No instructions on basicabasic navigation actions are provided in a standard FE app. Search bars are present in appropriate application modules to assist in item retrieval.
2.4.1Bypass1 Bypass Blocks	PartialYes	The Navigation menu bar is collapablecollapsible 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.2Page2 Page Titled	Partial	All modules and user menu options have a title within the head section but modualsmodules 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.3Focus3 Focus Order	Yes
2.4.4Link4 Link Purpose (In Context)	No	As each app is custom built we cant ensure all links are in context and named appropriatley.appropriately.
2.4.5Multiple5 Multiple Ways	No	As each app is custom built we cant ensure all pages are linked to each other directly and the requirement is not appariateappropriate for an interactive application rathecomparable thanto a static web site.site of displayed content. Access permissions also prevent specified users/groups from accessing specified area's of the application.
2.4.6Headings6 Headings and Labels	Yes
2.4.7Focus7 Focus Visible	Yes
2.4.8Location8 Location	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.9Link9 Link Purpose (Link Only)	YesPartial	As each app is custom built we cant ensure all links are in context and named appropriately.
2.4.10Section10 Section Headings	NoPartial	As each app is custom built we cant ensure all pages have sub headers where appropriate.appropriate although the standard build templates do have appropriate section heading names.
2.5Input5 Input Modalities	Yes
2.5.1Pointer1 Pointer Gestures	Yes
2.5.2Pointer2 Pointer Cancellation	NoYes	ThereAbort isOr noUndo functionalitycan tobe performapplied abut pointerremaining selection cancellation or alter user selection withinin the FEdown-event app.then moving off the selector so the up event occurs off selector.
2.5.3Label3 Label in Name	No	As each app is custom built we cant ensure labels are appropriate for their content.
2.5.4Motion4 Motion Actuation	NoN/A	Not applicable. There is no functionality impacted by device motion other than on tablets and mobile devices when the screen size corresponds to the portrait or landscape state of the device.
2.5.5Target5 Target Size (Enhanced)	No	As each app is custom built we cant ensure target size is a minimum of 44 CSS pixels.
2.5.6Concurrent6 Concurrent Input Mechanisms	Yes
2.5.7 Dragging Movements	Yes
2.5.8 Target Size (Minimum)	No	As each app is custom built we cant ensure all target input sizes are of a minimum 24 pixels or have applied selection alternatives present.
3. Understandable	Partial
3.1Readable1 Readable	Yes
3.1.1Language1 Language of Page	Yes
3.1.2Language2 Language of Parts	Yes
3.1.3Unusual3 Unusual 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.4Abbreviations4 Abbreviations	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.5Reading5 Reading 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	PartialNo	As each app is custom built we cant ensure all fieldstext is at a userreading canlevel updateequivalent haveto errorlower identificationsecondary detailseducation but all user profile fields that are as standard have error identification details.level.
3.1.6 Pronunciation	No	As each app is custom built we cant ensure a mechanism is put to provide contexts to ambiguous words.
3.1Error2 Predictable	Yes
3.2.1 On Focus	Yes
3.2.2 On Input	Yes
3.2.3 Consistent Navigation	Yes
3.2.4 Consistent Identification	Yes
3.2.5 Change on Request	Yes
3.2.6 Consistent Help	No	As each app is custom built we cant ensure any help information or contact details is presented in the same order on all pages.
3.3 Input Assistance	Yes	All standard input fields within the app are clear about what data is expected to be held there and which input fields are mandatory.
3.3.2Labels1 Error Identification	Yes
3.3.2 Labels or Instructions	No	As each app is custom built we cant ensure labels or instructions are present for all user inputs.
3.3.3Error3 Error 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.4Error4 Error Prevention (Legal, Financial, Data)	No	As each app is custom built we cant ensure user submissions are revisable, checked or reversible.
3.3.5Help5 Help	NoPartial
3.3.6Errorand Preventionsymbols (All)	No	Astips applied where appropriate to indicate in text what function they perform as standard but as each app is custom built we cant ensure userthis submissionsstandard areis revisable,maintained.
3.3.6 Error Prevention (All)	Yes	Data input by users can be reversible except in specific defined individual instances such as voting. Input fields such as User name etc. can be  edited multiple times. Data entered in mandatory fields is checked orfor reversible.errors and presents an error to the user upon attempting to save the input so that incorrect data entered is not saved.
4. Robust	Yes
4.1Compatible1 Compatible	Yes
4.1.1Parsing1 Parsing (Obsolete and removed)	Yes
4.1.2Name,2 Name, Role, Value	Yes
4.1.3Status3 Status Messages	PartialYes	ChatStatus messages,messages alertssuch as toast messages can be selected and videoread callsby displayassistive 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.technologies.
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.1Interpreting1 Interpreting Normative Requirements	No	As each app is custom built we cant ensure normatativenormative standards are maintained.
5.2Conformance2 Conformance Requirements	No	As each app is custom built we cant ensure confirmation standards are maintained.
5.2.1Conformance1 Conformance Level	No	As each app is custom built we cant ensure confirmation standards are maintained.
5.2.2Full2 Full pages	Yes
5.2.3Complete3 Complete processes	Yes
5.2.4Only4 Only Accessibility-Supported Ways of Using Technologies	Yes
5.2.5Non-5 Non-Interference	Yes
5.3Conformance3 Conformance Claims (Optional)	No	No functionality to support conformance claims.
5.3.1Required1 Required Components of a Conformance Claim	No	No functionality to support conformance claims.
5.3.2Optional2 Optional Components of a Conformance Claim	No	No functionality to support conformance claims.
5.4Statement4 Statement 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.5Statement5 Statement of Partial Conformance - Language	No	As each app is custom built we cant ensure a statement of conformance with languagethird party content is visibledisplayed or required as users can make the FE operate in multiple languages making a statementpartial redundant.conformance due to unsupported languages.