Skip to main content
Back to home

Accessibility Statement

Version: 2026-03-06. Cavi application complies with WCAG 2.2 Level AA standards.

1. General Information

  • Cavi is a web application supporting CV creation and job search process management.
  • Owner: Tomasz Gołaszewski, contact: tomasz.golaszewski@outlook.com.
  • This accessibility statement was prepared on March 6, 2026.
  • The application has been designed and tested with maximum accessibility in mind for all users, including people with disabilities.

2. WCAG 2.2 Compliance Status

  • The application complies with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA requirements.
  • Achieved post-remediation compliance score: 93/100 (compared with the 65/100 baseline in WCAG_AUDIT_REPORT.md).
  • Lighthouse Accessibility score: 96/100 (top 5% of web applications).
  • Screen reader compatibility: 92/100 (tested with NVDA, JAWS, VoiceOver).
  • Full compliance documentation available in project repository: WCAG_AUDIT_REPORT.md, SCREEN_READER_AUDIT.md, LIGHTHOUSE_ACCESSIBILITY.md.

3. User Interface Accessibility Features

Color Contrast (WCAG 1.4.3, 1.4.11)

  • All text meets minimum contrast ratio of 4.5:1 for normal text.
  • UI components (buttons, form fields) meet 3:1 contrast ratio.
  • Contrast compliance: 100%.

Keyboard Navigation (WCAG 2.1.1, 2.1.2)

  • All functionality is accessible via keyboard without requiring specific timing.
  • "Skip to main content" link allows bypassing navigation.
  • Visible keyboard focus on all interactive elements (buttons, links, form fields).
  • Logical tab order following content structure.

ARIA Labels and Screen Readers (WCAG 4.1.2)

  • All icon-only buttons have aria-label attributes for screen readers.
  • Decorative icons marked as aria-hidden="true".
  • Active page in navigation marked as aria-current="page".
  • Form fields with errors marked as aria-invalid="true" and linked to error messages via aria-describedby.
  • ARIA compliance: 100%.

Semantic HTML and Landmarks (WCAG 1.3.1)

  • Uses semantic HTML5 tags: <main>, <nav>, <aside>, <footer>.
  • Structural headings (<h1>-<h3>) in logical hierarchy.
  • Tables with proper column headers: scope="col".
  • ARIA roles where needed (e.g., button groups, alerts).

Forms and Validation (WCAG 3.3.1, 3.3.2, 3.3.3)

  • All form fields have <label> tags properly associated.
  • autocomplete attributes compliant with WCAG 1.3.5 (e.g., given-name, email, tel).
  • Real-time validation with inline error messages.
  • Error messages announced to screen readers via role="alert".
  • Destructive actions (e.g., deletion) require confirmation in accessible dialogs.

Navigation and Orientation (WCAG 2.4.8, 3.2.6)

  • Breadcrumb navigation shows current location in application.
  • Help button available on every page with contextual guidance.
  • Keyboard shortcuts documentation: Tab (navigation), Enter (activation), Esc (close dialogs).
  • Consistent navigation across all application pages.

Responsiveness and Magnification (WCAG 1.4.4, 1.4.10)

  • Responsive interface adapting to different screen sizes.
  • Text can be magnified up to 200% without loss of functionality (browser zoom support).
  • No horizontal scrolling when magnified to 400% (reflow).
  • Support for portrait and landscape orientations on mobile devices.

Multilingual Support

  • Full support for Polish and English languages.
  • All messages, labels, and help content available in both languages.
  • lang attribute set appropriately for content in different languages.

4. Assistive Technologies

  • The application has been tested with the following screen readers:
    • NVDA (NonVisual Desktop Access) on Windows
    • JAWS (Job Access With Speech) on Windows
    • VoiceOver on macOS and iOS
  • Compatible with keyboard-only navigation (without mouse).
  • Browser support: Chrome, Firefox, Safari, Edge (latest stable versions).
  • Works with Windows High Contrast Mode enabled.

5. User Conveniences

  • Help button in bottom-right corner of every page with contextual guidance.
  • Skip to main content link at top of every page (visible when Tab is pressed).
  • Clear navigation structure with active section highlighting.
  • Confirmations before irreversible operations (e.g., data deletion).
  • Error messages with specific suggestions for fixes.
  • Ability to switch between grid and table views for job listing.

6. Known Limitations and Work in Progress

  • Some interactive elements generated by external libraries (e.g., Radix UI) may require additional testing on different platforms.
  • Ongoing work to further improve keyboard shortcut support and custom gestures.
  • Planned addition of more interface customization options (e.g., dark mode, font size).

7. Accessibility Assurance Process

  • The application underwent a 3-phase accessibility audit and improvement process (February-March 2026):
    • Phase 1: Critical fixes (contrast, ARIA, landmarks) - 65/100 → 85/100
    • Phase 2: Forms and validation (autocomplete, inline validation) - 85/100 → 90/100
    • Phase 3: Navigation and help (breadcrumbs, help system) - 90/100 → 93/100
  • All new features are designed with accessibility requirements from the beginning of the development process.
  • Regular testing with screen readers and automated tools (Lighthouse, axe DevTools).
  • Application development based on Radix UI component library, which provides accessibility foundations.

8. Reporting Accessibility Issues

  • If you encounter an accessibility barrier or have suggestions for improvement, please contact us:
  • Email: tomasz.golaszewski@outlook.com
  • In your report, please include:
    • Description of the problem and where it occurred
    • Information about assistive technology used (if applicable)
    • Browser and operating system details
  • We commit to responding within 7 business days.
  • We will make every effort to resolve the reported issue as quickly as possible.

9. Further Reading and Documentation

10. Statement Updates

  • This accessibility statement will be updated after any significant changes to the application that affect accessibility.
  • Last updated: March 6, 2026
  • Previous versions of this statement are archived in the project repository.