Skip to content
Tabula Lens

Accessibility Statement

Accessibility Statement

Section titled “Accessibility Statement”

Tabula Lens is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

Our Commitment

Section titled “Our Commitment”

We strive to ensure that our documentation website is accessible to people with disabilities, including:

  • Visual impairments (blindness, low vision, color blindness)
  • Motor impairments (limited mobility, tremors)
  • Cognitive impairments (attention deficits, learning disabilities)
  • Hearing impairments

Accessibility Standards

Section titled “Accessibility Standards”

Our documentation aims to comply with:

  • WCAG 2.1 Level AA - Web Content Accessibility Guidelines
  • Section 508 - U.S. federal accessibility standards
  • EN 301 549 - European accessibility requirements

Accessibility Features

Section titled “Accessibility Features”

Visual Accessibility

Section titled “Visual Accessibility”

✓ High Contrast Mode

  • Supports system high contrast preferences
  • Enhanced color contrast ratios (minimum 4.5:1 for normal text, 3:1 for large text)
  • Clear visual focus indicators for keyboard navigation

✓ Color Independence

  • Information is not conveyed by color alone
  • Text and icons maintain contrast in both light and dark modes
  • Color combinations meet WCAG AA requirements

✓ Responsive Design

  • Content reflows properly on different screen sizes
  • Text can be zoomed up to 200% without loss of content
  • Touch targets are at least 44x44 pixels for mobile users

Motor Accessibility

Section titled “Motor Accessibility”

✓ Keyboard Navigation

  • All interactive elements are keyboard accessible
  • Logical tab order throughout the site
  • Visible focus indicators on all interactive elements
  • Skip-to-content link for keyboard users

✓ Reduced Motion

  • Respects prefers-reduced-motion system preference
  • Optional to disable animations and transitions
  • No content relies on animation to convey meaning

Cognitive Accessibility

Section titled “Cognitive Accessibility”

✓ Clear Language

  • Plain language explanations
  • Consistent terminology throughout
  • Clear headings and structure
  • Technical terms are defined when first used

✓ Consistent Navigation

  • Predictable layout and navigation
  • Clear page titles and headings
  • Breadcrumb navigation for context
  • Search functionality for finding content

Assistive Technology Support

Section titled “Assistive Technology Support”

✓ Screen Reader Support

  • Semantic HTML structure
  • ARIA labels and roles where needed
  • Alt text for images
  • Proper heading hierarchy
  • Screen reader-only content for context

✓ Text-to-Speech

  • Content is structured for TTS compatibility
  • Mathematical notation is properly formatted
  • Code blocks are readable by screen readers

Known Limitations

Section titled “Known Limitations”

While we strive for full accessibility, some limitations may exist:

Third-Party Content

Section titled “Third-Party Content”
  • Some code examples may reference external libraries with varying accessibility
  • External links may lead to content not under our control

Technical Documentation

Section titled “Technical Documentation”
  • Complex code examples may be challenging for some screen reader configurations
  • Mathematical notation and technical symbols may require specialized tools

Accessibility Testing

Section titled “Accessibility Testing”

We regularly test our documentation using:

  • Automated accessibility testing tools
  • Keyboard-only navigation testing
  • Screen reader testing (NVDA, JAWS, VoiceOver)
  • Color contrast validation
  • Mobile device testing with screen readers

Browser and Assistive Technology Support

Section titled “Browser and Assistive Technology Support”

Our documentation is tested and compatible with:

Browsers

Section titled “Browsers”
  • Chrome (latest version)
  • Firefox (latest version)
  • Safari (latest version)
  • Edge (latest version)

Screen Readers

Section titled “Screen Readers”
  • NVDA (Windows)
  • JAWS (Windows)
  • VoiceOver (macOS, iOS)
  • TalkBack (Android)

Operating Systems

Section titled “Operating Systems”
  • Windows 10/11
  • macOS (latest versions)
  • iOS (latest versions)
  • Android (latest versions)

Feedback and Contact

Section titled “Feedback and Contact”

We welcome feedback on the accessibility of our documentation. Please let us know if you encounter accessibility barriers:

Reporting Accessibility Issues

Section titled “Reporting Accessibility Issues”

If you find an accessibility barrier, please:

  1. Describe the specific accessibility issue
  2. Provide the URL of the page where you encountered the issue
  3. Specify the browser, screen reader, or assistive technology you were using
  4. Share any suggestions for improvement

Contact Methods

Section titled “Contact Methods”

Ongoing Efforts

Section titled “Ongoing Efforts”

We are committed to:

  • Regular accessibility audits
  • Incorporating accessibility into our development process
  • Training our team on accessibility best practices
  • Staying informed about evolving accessibility standards
  • Engaging with the accessibility community

Future Improvements

Section titled “Future Improvements”

We plan to continue enhancing accessibility through:

  • Expanded video content with captions and transcripts
  • Enhanced keyboard shortcuts for power users
  • Improved mobile accessibility
  • Additional language support for international users
  • Accessibility testing with diverse user groups

Resources

Section titled “Resources”

For more information on web accessibility:

Last Updated: July 11, 2026

Review Date: July 11, 2027