1. Our Commitment

We strive to ensure that MeridAIn is accessible to all users, regardless of ability. We are working to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.

2. Accessibility Features

MeridAIn includes the following accessibility features:

2.1 Navigation

• Keyboard navigation support throughout the site
• Skip-to-content links for screen reader users
• Consistent and predictable navigation structure
• Focus indicators on interactive elements

2.2 Content

• Semantic HTML structure with proper heading hierarchy
• Alt text for images (where available)
• Readable font sizes with responsive scaling
• Sufficient color contrast ratios
• No content that flashes more than three times per second

2.3 Assistive Technology

• Compatibility with screen readers (VoiceOver, NVDA, JAWS)
• ARIA labels on interactive components
• Form labels and error messages

3. Known Limitations

While we strive for full accessibility, some content may have limitations:

• AI-sourced images: Some images may lack alt text if not provided by the source. We are working to improve this.
• Third-party content: External embedded content may not meet our accessibility standards.
• PDF exports: Generated PDFs may have limited accessibility features.

4. Browser and Assistive Technology Compatibility

MeridAIn is designed to be compatible with:

• Modern browsers (Chrome, Firefox, Safari, Edge - latest 2 versions)
• Screen readers (VoiceOver, NVDA, JAWS)
• Screen magnification software
• Voice recognition software

5. Feedback and Assistance

We welcome feedback on the accessibility of MeridAIn. If you encounter accessibility barriers or have suggestions for improvement:

• Contact us: Submit an accessibility request
• Response time: We aim to respond within 5 business days

6. Alternative Formats

If you need content in an alternative format, please contact us and specify:

• The article or page URL
• Your preferred format
• Your contact information

We will do our best to provide the content in an accessible format.

7. Continuous Improvement

We are committed to improving accessibility:

• Regular accessibility audits
• User feedback integration
• Training on accessibility best practices
• Ongoing updates to meet evolving standards

8. Technical Specifications

Accessibility of MeridAIn relies on the following technologies:

• HTML5
• CSS
• JavaScript
• WAI-ARIA

9. Assessment Approach

MeridAIn assesses accessibility through:

• Self-evaluation using automated tools (axe, WAVE)
• Manual testing with keyboard and screen readers
• User feedback and testing

10. Contact

For accessibility-related questions or concerns, contact us.