Accessibility Statement

Last Updated: March 24, 2026

Our Commitment: Opossum CMS is committed to providing a website and software that is accessible to everyone, including people with disabilities. We believe technology should be inclusive and usable by all.

Conformance Status

Conformance Level: Partially Conformant with WCAG 2.2 Level AA

The Opossum CMS website (ocms.tech) has been designed with accessibility in mind and aims to meet WCAG 2.2 Level AA standards published by the World Wide Web Consortium (W3C).

What This Means

Our website:

  • ✓ Works with screen readers: Tested with NVDA and VoiceOver
  • ✓ Keyboard accessible: All functions reachable via Tab key, no keyboard traps
  • ✓ High contrast: Text meets 4.5:1 contrast ratio for readability
  • ✓ Clear heading structure: Semantic HTML with proper heading hierarchy (H1 → H2 → H3)
  • ✓ Descriptive links: Link text describes the destination
  • ✓ Responsive design: Works on mobile devices and with zoom
  • ✓ Plain language: Documentation written clearly for readability
  • ⚠ Cookie consent banner: Being implemented to meet WCAG accessibility requirements

Current Limitations

While we strive for full WCAG 2.2 AA conformance, some limitations exist:

  • Third-party services: Google Analytics, hCaptcha, and Dify AI may have accessibility limitations. We're evaluating alternatives.
  • Code examples: Syntax highlighting in code blocks may not meet perfect color contrast in some cases
  • PDF documents: Older PDFs in downloads may not be fully accessible; new PDFs are tagged

We're actively working to address these limitations and appreciate your feedback.

Accessibility Features

Keyboard Navigation

  • All interactive elements (buttons, links, form inputs) are reachable via keyboard
  • Tab order follows logical page flow (top-to-bottom, left-to-right)
  • Focus is always visible (shown with outline or highlight)
  • No keyboard traps — you can always move focus away from an element

Screen Reader Support

  • All images have alt text describing the content
  • Form inputs have associated labels for screen reader users
  • Buttons have descriptive text (not just "Click Here")
  • Semantic HTML ensures proper heading structure and landmark regions
  • ARIA attributes used where needed for complex interactive components

Visual Accessibility

  • Color contrast: Text meets WCAG AA (4.5:1 normal, 3:1 large)
  • Text sizing: Scalable up to 200% without loss of functionality
  • Zoom support: Site works with browser zoom (Ctrl/Cmd + plus)
  • Color independence: Information is not conveyed by color alone
  • Font size: Readable baseline of 16px with proper line height

Content Accessibility

  • Plain language: Avoiding jargon; explaining technical terms
  • Clear structure: Headings organize content logically
  • Lists: Used for grouped information (not relying on visual formatting alone)
  • Links: Descriptive link text (not "click here")
  • Data tables: Proper headers and row/column associations

Mobile Accessibility

  • Responsive design works on all screen sizes
  • Touch targets are at least 44x44 pixels (WCAG recommendation)
  • No content requires both vertical and horizontal scrolling
  • Zoom and text scaling work correctly on mobile

Known Limitations & Workarounds

Third-Party Services

Service Status Limitation Workaround
Google Analytics Optional (requires consent) Some analytics UI elements may lack perfect contrast Can be disabled via consent preferences
hCaptcha Optional (forms only) Visual CAPTCHA challenge difficult for blind users Audio alternative available; contact us for alternative verification
GitHub Issues External link GitHub's UI may not meet our standards Email alternative: webmaster@ocms.tech

Content Limitations

  • Code blocks: Syntax highlighting may have contrast issues. Tip: Use your browser's developer tools to view source code.
  • Demo pages: Complex interactive demos may require keyboard or mouse input. We're working on keyboard alternatives.
  • Blog (when available): Embedded videos will include captions and transcripts.

How to Request Accommodations

If you encounter a barrier not listed above, please contact us immediately:

Email: accessibility@ocms.tech

Include a description of the barrier and the page or feature affected. We'll respond within 5 business days.

Technical Standards & Technologies

Web Content Accessibility Guidelines (WCAG)

Our site aims for WCAG 2.2 Level AA conformance. WCAG is the international standard for web accessibility published by the W3C.

WCAG 2.2 Principles (POUR):

  • Perceivable: Information is presented in ways all users can perceive (text alternatives for images, captions for video, sufficient contrast)
  • Operable: Users can interact with the site using keyboard, mouse, or other input methods
  • Understandable: Content is clear and navigation is consistent
  • Robust: Content works with assistive technologies (screen readers, voice control, etc.)

Technologies We Rely On

  • HTML5: Semantic markup for proper document structure
  • CSS: Visual styling that respects user preferences
  • JavaScript: Progressive enhancement (site works without JavaScript)
  • ARIA: Accessibility attributes for dynamic content

Assistive Technologies Supported

Our site has been tested with:

  • Screen Readers: NVDA (Windows), VoiceOver (Mac/iOS), JAWS (Windows)
  • Voice Control: Works with browser voice control features
  • Keyboard Navigation: No mouse required
  • Browser Extensions: Color contrast enhancers, dark mode, text size adjusters
  • Operating System: Windows High Contrast Mode, macOS Increase Contrast, etc.

Testing & Validation

Accessibility Testing Methods

  • Automated scanning: Lighthouse, axe DevTools, WAVE
  • Manual testing: Keyboard navigation, screen reader usage, visual inspection
  • User testing: Testing with real assistive technology users
  • Conformance reviews: Regular audits against WCAG 2.2 AA criteria

Browser & Device Compatibility

We support the latest versions of:

  • Google Chrome / Edge (Chromium-based)
  • Mozilla Firefox
  • Apple Safari (Mac, iOS)

The site is also compatible with:

  • Mobile browsers (iOS Safari, Chrome Mobile, Firefox Mobile)
  • Tablets (iPad, Android)
  • Older browsers (with graceful degradation)

Performance & Accessibility

Fast load times benefit all users, especially those on slow connections or mobile devices. Our site:

  • Loads in < 2 seconds on 4G
  • Uses efficient caching
  • Minimizes JavaScript for faster interaction

Feedback, Requests & Complaints

Report Accessibility Issues

Found an accessibility problem? Please tell us:

Accessibility Contact: accessibility@ocms.tech

Include:

  • The page or feature affected
  • The accessibility barrier you encountered
  • Your assistive technology (screen reader, voice control, etc.)
  • Browser and operating system

Response Time: We'll respond to accessibility reports within 5 business days and work toward a fix.

Request Features or Accommodations

Have a suggestion to improve accessibility? We'd love to hear it! Email us with:

  • Your suggestion or feature request
  • How it would help you or others

File a Formal Complaint

If you're not satisfied with our response, you may file a complaint with your national accessibility authority:

Additional Resources

For Users

For Developers

For Organizations

Contact Us

For accessibility-related questions, requests, or concerns:

General Contact: webmaster@ocms.tech
Accessibility Contact: accessibility@ocms.tech

Related Documents

Continuous Improvement

This Accessibility Statement reflects our current efforts and known limitations as of March 24, 2026. We are committed to continuously improving accessibility and welcome your feedback to help us do better.

Thank you for helping us make Opossum CMS more inclusive!