| 1.1.1 Non-text Content | All icons, images, and visuals must have text descriptions or be hidden from assistive tech if decorative | Partially Supports | All non-text content is labeled with meaningful text alternatives or marked decorative. Program widgets are missing contextual alt-texts for images uploaded by the company. |
| 1.2.1 Audio-only and Video-only | Audio-only needs a transcript. Video-only needs a description or audio explanation | Supports | Video-only media includes descriptive text alternatives. Videos with sound have synchronized captions. Videos without sound have descriptions. No audio-only media is present. |
| 1.2.2 Captions (Prerecorded) | Prerecorded videos with sound must have captions | Supports | Prerecorded videos with audio include synchronized captions. |
| 1.2.3 Audio Description or Media Alternative | Videos with audio must have a text alternative or audio description | Supports | Prerecorded synchronized media includes a full text alternative. |
| 1.3.1 Info and Relationships | Visual structure must be encoded for assistive tech | Supports | Semantic HTML and ARIA roles expose structure and relationships to assistive technologies. |
| 1.3.2 Meaningful Sequence | Content must be in logical order recognizable by assistive tech | Supports | DOM order matches visual presentation and ensures correct reading sequence. |
| 1.3.3 Sensory Characteristics | Instructions can’t rely only on color, shape, or position | Supports | Instructions avoid referring only to visual or sensory cues. |
| 1.4.1 Use of Color | Color alone can’t be the only way to show meaning | Supports | Color is not used as the sole method of conveying information. |
| 1.4.2 Audio Control | Auto-playing audio must be controllable | Supports | No audio content plays automatically. |
| 2.1.1 Keyboard | Everything must be usable with keyboard only | Supports | All functionality is operable via keyboard navigation. |
| 2.1.2 No Keyboard Trap | Users must be able to move focus in and out of all components | Supports | Keyboard trapping does not occur except in modal windows. |
| 2.1.4 Character Key Shortcuts | Single key shortcuts must be configurable | Supports | Character key shortcuts are not present. |
| 2.2.1 Timing Adjustable | Time limits must be adjustable | Supports | Timeout content is not present. |
| 2.2.2 Pause, Stop, Hide | Moving content must be controllable | Supports | Blinking, scrolling, or auto-updating content is not present. |
| 2.3.1 Three Flashes | Nothing should flash more than 3 times per second | Supports | Flashing content is not present. |
| 2.4.1 Bypass Blocks | Users must be able to skip repeated content | Supports | Content blocks are not present. |
| 2.4.2 Page Titled | Pages must have descriptive titles | Supports | Unique page titles are supplied by default. |
| 2.4.3 Focus Order | Focus must move in logical order | Supports | Focus moves in a logical, expected order. |
| 2.4.4 Link Purpose | Link purpose must be clear from text or context | Supports | The purpose of each link can be determined from the link text. |
| 2.5.1 Pointer Gestures | Complex gestures must have simple alternatives | Supports | Simple alternatives are provided. |
| 2.5.2 Pointer Cancellation | Pointer actions must be cancellable | Supports | Pointer interactions can be canceled before completing. |
| 2.5.3 Label in Name | Visible labels must be in accessible names | Supports | Controls and links feature accessible names matching the visual portion. |
| 2.5.4 Motion Actuation | Motion triggers must have alternatives | Supports | No motion-based input is required. |
| 3.1.1 Language of Page | Pages must define their main language | Supports | Default page language is supplied in the head section. |
| 3.2.1 On Focus | Focus should not cause unexpected changes | Supports | Focusing on components does not trigger context changes. |
| 3.2.2 On Input | Input changes shouldn’t cause major changes without warning | Supports | Input changes do not trigger significant changes without notice. |
| 3.2.6 Consistent Help | Help should be available consistently | Supports | Help options are provided consistently across applicable views. |
| 3.3.1 Error Identification | Errors must be clearly indicated with descriptions | Supports | Errors are clearly indicated with textual descriptions. |
| 3.3.2 Labels or Instructions | Forms must include clear labels | Supports | Form fields include descriptive labels and/or placeholder instructions. |
| 3.3.7 Redundant Entry | Users shouldn’t re-enter the same info | Supports | Previously entered information is retained and reused when possible. |
| 4.1.2 Name, Role, Value | UI components must expose correct info to assistive tech | Supports | All UI elements expose correct name, role, and value using semantic HTML or ARIA. |
