WCAG Success Criteria | Conformance Level | Remarks and Explanations |
1.1.1 Non-text Content | Partially Supports | Most images include alt text. Decorative images use empty alt attributes. Improvements are under review; targeting in 2027. |
1.2.1 Audio-only and Video-only (Prerecorded) | Supports | Client-uploaded content. Clients can add transcripts or descriptions via third-party platforms (youtube or vimeo). |
1.2.2 Captions (Prerecorded) | Supports | Client-uploaded content. Clients can add captions via third-party platforms (youtube or vimeo) or directly. |
1.2.3 Audio Descriptions or Media Alternative (Prerecorded) | Supports | Client-uploaded content. Clients can add a link to a transcript or description of this audio. |
1.3.1 Info and Relationships | Supports | Structured with semantic HTML elements (h1, h2, etc.) Form fields use associated label elements. Modals have properly associated close buttons. |
1.3.2 Meaningful Sequence | Supports | Content structured with semantic HTML following logical hierarchy. Keyboard tab not currently supported as the application does not rely on physical or digital keyboards. |
1.3.3 Sensory Characteristics | Partially Supports | Supports VoiceCommands, VoiceOver, and TalkBack for auditory feedback. Does not rely on sensory characteristics (shape, size, color, location) alone. Clients responsible for additional instructions in their content; we are evaluating areas where client control is limited. |
1.4.1 Use of Color | Supports | Icons and labels used alongside color to convey information. Labels support voice-over technologies. Error messages supplement color indicators. While compliant, we're always exploring ways to improve. |
1.4.2 Audio Control | Supports | Client-uploaded content uses hosted third-party platforms (youtube, vimeo, soundcloud) or OS players, which provide audio controls. |
2.1.1 Keyboard | Not Applicable | Application does not rely on physical or digital keyboard for navigation. Keyboard input support for form field entry. |
2.1.2 No Keyboard Trap | Not Applicable | No keyboard-based navigation. Touch and other interaction methods used. |
2.1.4 Character Key Shortcuts | Not Applicable | No character key shortcuts implemented. |
2.2.1 Timing Adjustable | Not Applicable | No time limits or timing mechanisms requiring user interactions. |
2.2.2 Pause, Stop, Hide | Not Applicable | No moving, blinking, scrolling or auto-updating content by default. Clients responsible for uploaded content and to ensure compliance. |
2.3.1 Three Flashes or Below Threshold | Not Applicable | No flashing content by default. Clients responsible for uploaded content and to ensure compliance. |
2.4.1 Bypass Blocks | Not Applicable | No dedicated skip mechanism. Minimal elements (side menu, profile icon, logo) before main content. |
2.4.2 Page Titled | Supports | Pages include description titles. Clients responsible for some page titles to ensure clarity and relevance. |
2.4.3 Focus Order | Partially Supports | Screen readers enable navigation through form fields and focusable components. No physical/digital keyboard navigation. |
2.4.4 Link Purpose (In Context) | Supports | Links displayed in blue and underlined. Clients responsible for making link 'text' descriptive and relevant. Clients can override link text color using custom CSS. |
2.5.1 Pointer Gestures | Not Applicable | No complex pointer gestures implemented. |
2.5.2 Pointer Cancellation | Not Applicable | No complex pointer gestures requiring cancellation mechanisms. |
2.5.3 Label In Name | Partially Supports | Provides accessible names for matching visible labels for assistive technology compatibility. Some buttons lack appropriate aria-label or equivalent markup. Reevaluation of buttons scheduled for end of year review. |
2.5.4 Motion Actuation | Not Applicable | No motion actuation features implemented. |
3.1.1 Language of Page | Supports | Default language supported. Internationalization implemented for future multi-language support. |
3.2.1 On Focus | Partially Supports | Focus management via screen readers, which provide appropriate feedback. Traditional focus indicators not applicable as application does not use physical/digital keyboards. |
3.2.2 On Input | Supports | No unexpected context changes upon user input. |
3.3.1 Error Identification | Supports | Error identification and help text provided for input errors. |
3.3.2 Labels or Instructions | Supports | Input labels and helper text provided where applicable. |
4.1.1 Parsing | Supports | Code properly structured for assistive technologies. |
4.1.2 Name, Role, Value | Supports | UI components have programmatically determined names, roles and values accessible to assistive technologies. |
| WCAG Success Criteria | Conformance Level | Remarks and Explanations |
1.2.4 Captions (Live) | Supports | Client-uploaded content. Clients responsible for providing live captions. |
1.2.5 Audio Description (Prerecorded) | Supports | Client-uploaded content. Clients responsible for providing and linking to audio descriptions. |
1.3.4 Orientation | Partially Supports | Portrait orientation required throughout user experience. Essential for digital scorecard and GPS. Landscape orientation may be explored for other features in the future. |
1.3.5 Identify Input Purpose | Supports | Standard HTML input types (email, phone number, etc.) used to identify form field purposes. |
| 1.4.3 Contrast (Minimum) | Supports | High-contrast by default. Clients can customize colors. Clients responsible for ensuring color compliance. |
1.4.4 Resize Text | Partially Supports | Android allows for resize text. Exploring relative font sizing to accomodate user preference with iPhone. Clients can currently customize font size. |
1.4.5 Images of Text | Partially Supports | Real/Alt text is used where possible. Client-uploaded images may contain text. Improvements are under review; targeting 2027. |
1.4.10 Reflow | Supports | Layouts generally reflow well across screen sizes (phone to tablet). Some features (Scorecard & GPS) may require vertical scrolling. |
1.4.11 Non-text Contrast | Supports | High-contrast by default. Clients can customize colors. Clients are responsible for ensuring color compliance. |
1.4.12 Text Spacing | Does Not Support | Does not support spacing overrides via device accessibility settings. Clients can customize text spacing. |
1.4.13 Content on Hover or Focus | Supports | Custom tooltips accessed via tapping where applicable, user can close by tapping close button. |
| 2.4.5 Multiple Ways | Supports | Multiple navigation options: home screen content, side menu, footer menu. Horizontal content navigable via swipe or navigation buttons. |
2.4.6 Headings and Labels | Supports | Clear, descriptive headings and labels. Clients responsible for ensuring compliance on pages where they add headings and labels. |
2.4.7 Focus Visible | Partially Supports | No physical/digital keyboard. Focus indicators visible when using VoiceOver and TalkBack assistive technologies. |
2.4.11 Focus Not Obscured (Minimum) | Supports | Form fields remain at least partially visible during keyboard interface use and are not completely obscured by UI elements. |
2.5.7 Dragging Movements | Not Applicable | No drag-and-drop functionality. Swipe gestured users for interaction. |
2.5.8 Target Size | Partially Supports | Most interactive elements meet 44x44 pixel minimum. Improvements to be considered in the future. |
| 3.1.2 Language of Parts | Not Applicable | Default language supported. Multiple language selection is not currently supported. |
3.2.3 Consistent Navigation | Support | Side menu and footer menu maintain consistent order. User navigates every where from home screen. |
| 3.2.4 Consistent Identification | Support | Components with same functionality consistently identified across all pages. |
3.3.3 Error Suggestion | Partially Supports | Error messages inform users of incorrect inputs. Suggestions not currently provided for all incorrect inputs. Improvements to be considered in the future. |
3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | No legal or financial transactions. Membership purchases and data deletion requests do not require error prevention processes. |
3.3.8 Accessible Authentication (Miniumum) | Supports | OTP allows for users to copy/paste from SMS or email directly in OTP input field. OAuth email and password authentication is handled by the third-party who maintains their WCAG compliance. |
4.1.3 Status Messages | Reviewing |
Perfomance Criteria | Conformance Level | Remarks and Explanations |
Blind / Screen Reader Users | Partially Supports | Accessible and navigable with screen readers using alt text, proper labeling, error identification, and semantic HTML. Keyboard functionality enabled for form inputs. Tested with VoiceOver and TalkBack assistive technologies. |
Low Vision Users | Partially Supports | Icon based indicators convey information without relying on color. Success and error messages displayed regardless of color. Most images use alt text. Text size adjustments not supported. |
Hearing Loss Users | Partially Supports | All navigation, text content, and functionality readable. Client-uploaded content. Clients responsible for including captions, transcripts and visual alerts. |
Limited Mobility (Keyboard Users) | Not Applicable | No physical/digital keyboard navigation. Users can interact via assistive technologies such as screen readers or voice commands. |