Accessibility Status

WCAG 2.2 AA remediation and verification status

Status, not a conformance claim: This engineering report combines a hand-maintained checklist with automated source, component, and browser checks. Passing these selected checks does not establish WCAG conformance for the whole service.

Verification still required: Manual assistive-technology testing, user testing, and an independent audit have not been completed. Last reviewed: 2026-08-27.

93%
Selected check pass rate
26
Checks passed

of 28 selected checks

2
Checks needing review

criteria still needing review

WCAG 2.2 AA verification in progress

Automated checks cover selected semantics, names, keyboard interactions, contrast, reflow, and cross-browser behavior. Manual screen-reader and usability verification remain outstanding.

Detailed Results

Selected accessibility checks and their current engineering status
CriterionLevelStatusNotes
1.1.1 Non-text ContentA PASSIcons marked with aria-hidden="true", buttons have aria-label
1.3.1 Info and RelationshipsA PASSNavigation, main, and aside landmarks present
1.4.1 Use of ColorA PASSStatus indicators use text labels alongside colors
2.1.1 KeyboardA PASSTab navigation, Enter/Space activation implemented
2.1.2 No Keyboard TrapA PASSModal dialogs have Escape key handling; creed catalog Tab navigation releases focus at the first/last card
2.4.3 Focus OrderA PASSTab order follows visual layout
2.4.4 Link PurposeA PASSAll links have descriptive aria-labels
3.2.1 On FocusA PASSFocus events do not trigger navigation
3.3.1 Error IdentificationA PASSaria-invalid and aria-errormessage implemented
3.3.2 Labels or InstructionsA PASSAll form controls have aria-label or visible labels
4.1.2 Name, Role, ValueA PASSARIA attributes properly implemented
1.4.3 Contrast (Minimum)AA PARTIALMost text meets requirements, some subtle text may need review
1.4.4 Resize TextAA PASSResponsive design with rem/em units
1.4.5 Images of TextAA PASSAll text is actual HTML text, not images
1.4.10 ReflowAA PASSResponsive design adapts to viewport
1.4.11 Non-text ContrastAA PARTIALMost components meet requirements, review needed for subtle borders
2.4.5 Multiple WaysAA PASSNavigation menu, search, and direct navigation available
2.4.6 Headings and LabelsAA PASSClear, descriptive headings throughout
2.4.7 Focus VisibleAA PASSFocus rings implemented with :focus-visible
3.1.2 Language of PartsAA PASSlang attribute on HTML element
3.2.3 Consistent NavigationAA PASSSidebar navigation consistent across views
3.2.4 Consistent IdentificationAA PASSConsistent button labeling and iconography
3.3.3 Error SuggestionAA PASSForm validation provides helpful suggestions
3.3.4 Error PreventionAA PASSDelete confirmations implemented
1.3.5 Identify Input PurposeAA PASSAutocomplete attributes where applicable
1.4.12 Text SpacingAA PASSFlexible layout handles text spacing changes
1.4.13 Content on Hover or FocusAA PASSTooltips properly implemented
4.1.3 Status MessagesAA PASSaria-live regions and announcement service implemented

Checklist export

This generated text summarizes selected checks and is not a conformance declaration.

# Creed Space Accessibility Engineering Checklist

Hand-maintained engineering checklist (not a complete automated or manual audit). Last reviewed: 2026-08-27.

## Selected Check Status

- **Total Criteria Checked**: 28
- **Passed**: 26 (93%)
- **Partial**: 2 (7%)
- **Failed**: 0 (0%)

## Checks Grouped by WCAG Level

- **Level A**: 11/11 passed (100%)
- **Level AA**: 15/17 passed (88%)

## Scope and Limits

**WCAG 2.2 AA verification is in progress. This checklist is not a conformance declaration.**

Manual screen-reader testing, user testing with people who use assistive technology, and independent review remain required.


## Areas Needing Attention

- **1.4.3 Contrast (Minimum)** (Level AA): PARTIAL
  - Most text meets requirements, some subtle text may need review
- **1.4.11 Non-text Contrast** (Level AA): PARTIAL
  - Most components meet requirements, review needed for subtle borders

## Recommendations

1. Conduct manual contrast ratio testing for borderline cases
2. Test with actual screen readers (NVDA, JAWS, VoiceOver)
3. Perform user testing with individuals who use assistive technologies
4. Regular accessibility audits with automated tools (axe DevTools)