Accessibility Statement

1. Our Commitment to Accessibility

We are dedicated to making our platforms accessible to all users, regardless of their abilities or the technologies they use to access the web. Our goal is to comply with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards.

1.1 Scope of Coverage

This accessibility statement applies to all JustKrith platforms:

• Portfolio: krithiv.dev (Netlify + Cloudflare CDN)
• Blog: blog.krithiv.dev (Self-hosted in Germany + Cloudflare CDN)
• Resume: resume.krithiv.dev (Netlify + Cloudflare CDN)
• Documentation: docs.krithiv.dev (Netlify + Cloudflare CDN)
• Links: links.krithiv.dev (Netlify + Cloudflare CDN)
• Status: status.krithiv.dev/status/main (Self-hosted in US + Cloudflare CDN)
• Community: JustKrith Community Forum (Hosted via Freeflarum)

1.2 Standards and Guidelines

Our accessibility efforts are guided by:

• WCAG 2.1 Level AA: Web Content Accessibility Guidelines as our primary standard
• Section 508: U.S. federal accessibility requirements for electronic content
• ADA Compliance: Americans with Disabilities Act digital accessibility principles
• ARIA Standards: Web Accessibility Initiative's Accessible Rich Internet Applications specification

2. Accessibility Features Implemented

2.1 Visual Accessibility

• High Contrast Support: Sufficient color contrast ratios meeting WCAG AA standards
• Color Independence: Information conveyed through color is also available through other means
• Scalable Text: Text can be resized up to 200% without loss of functionality
• Responsive Design: Content adapts to different screen sizes and orientations
• Focus Indicators: Clear visual focus indicators for keyboard navigation
• Dark/Light Mode: Theme toggle available across all platforms for visual comfort

2.2 Keyboard and Navigation Accessibility

• Keyboard Navigation: All interactive elements accessible via keyboard only
• Logical Tab Order: Sequential navigation follows logical content flow
• Skip Links: "Skip to main content" links provided for screen readers
• Consistent Navigation: Navigation structure remains consistent across pages
• No Keyboard Traps: Users can navigate away from any component using standard keyboard controls

2.3 Screen Reader Compatibility

• Semantic HTML: Proper use of HTML elements for meaningful structure
• ARIA Labels: Comprehensive labeling for dynamic content and complex interactions
• Alternative Text: Descriptive alt text for all images and visual content
• Heading Structure: Logical heading hierarchy (H1-H6) for content organization
• Form Labels: Clear, descriptive labels for all form elements
• Status Updates: ARIA live regions for dynamic content changes

2.4 Motor and Interaction Accessibility

• Large Click Targets: Buttons and links meet minimum size requirements (44x44px)
• Adequate Spacing: Sufficient spacing between interactive elements
• Timeout Extensions: Options to extend or disable time limits where applicable
• Error Prevention: Clear instructions and confirmation for irreversible actions
• Input Assistance: Help text and format requirements clearly indicated

2.5 Cognitive Accessibility

• Clear Language: Plain language and simple sentence structure where possible
• Consistent Layout: Predictable page structure and navigation patterns
• Error Messages: Clear, specific error messages with suggestions for resolution
• Progress Indicators: Clear indication of current location and process steps
• Content Organization: Logical content grouping with clear headings

3. Platform-Specific Accessibility Considerations

3.1 Portfolio and Professional Pages

• Project descriptions include comprehensive alternative text for visual elements
• Technical skills and experience information presented in accessible formats
• Contact forms fully accessible with proper labeling and error handling
• Timeline and experience sections use semantic markup for screen readers

3.2 Blog and Documentation

• Code examples include proper syntax highlighting with sufficient contrast
• Technical diagrams and images include detailed alternative descriptions
• Article structure uses proper heading hierarchy for easy navigation
• Search functionality is keyboard accessible and provides clear results

3.3 Status and Monitoring Pages

• Service status information is available in both visual and text formats
• Status indicators use both color and symbols/text for accessibility
• Historical data presented in accessible table formats with proper headers
• Incident updates include timestamps and clear status descriptions

4. Third-Party Content and Services

While we strive to ensure accessibility across all JustKrith platforms, some content and services are provided by third parties:

4.1 Social Media Integration

• Community Forum: Accessibility depends on Freeflarum's platform accessibility features
• Discord: Community server accessibility depends on Discord's platform accessibility
• X (Twitter), Instagram, GitHub: Third-party social platforms manage their own accessibility standards
• We provide alternative contact methods for users who cannot access third-party platforms

4.2 CDN and Infrastructure

• Cloudflare CDN: Accessibility features maintained across global content distribution
• Hosting Providers: Netlify and self-hosted infrastructure comply with accessibility standards

5. Assistive Technology Compatibility

Our platforms are designed to work with a wide range of assistive technologies:

5.1 Tested Assistive Technologies

• Screen Readers: NVDA, JAWS, VoiceOver, TalkBack
• Voice Recognition: Dragon NaturallySpeaking and similar software
• Keyboard Navigation: Switch navigation and alternative keyboards
• Magnification: ZoomText, built-in OS magnifiers, browser zoom

5.2 Browser and Device Compatibility

• Modern Browsers: Chrome, Firefox, Safari, Edge (latest 2 versions)
• Mobile Accessibility: iOS VoiceOver and Android TalkBack support
• Operating Systems: Windows, macOS, iOS, Android accessibility features

6. Known Limitations and Ongoing Improvements

6.1 Current Limitations

We are aware of the following accessibility challenges and are actively working to address them:

• Some dynamic content animations may not be fully compatible with motion sensitivity preferences
• Certain interactive portfolio elements may require JavaScript enabled for full accessibility
• Third-party embedded content may not always meet our accessibility standards
• Community forum accessibility is limited to Freeflarum's platform capabilities

6.2 Ongoing Improvements

• Regular Audits: Quarterly accessibility audits using automated and manual testing
• User Testing: Feedback collection from users with disabilities
• Feature Updates: Continuous improvement of accessibility features
• Training: Ongoing education about accessibility best practices

7. Feedback and Support

7.1 Accessibility Feedback

We welcome feedback about the accessibility of JustKrith platforms. If you encounter accessibility barriers or have suggestions for improvement, please contact us:

• Email: [email protected]
• General Contact: [email protected]
• Response Time: We aim to respond to accessibility inquiries within 2-3 business days

7.2 Alternative Access Methods

If you are unable to access any content or functionality on our platforms, we can provide:

• Alternative formats for content (text, audio, large print)
• Direct assistance with accessing information or services
• Alternative communication methods for support and inquiries
• Guidance on using assistive technologies with our platforms

7.3 Complaint Process

If you are not satisfied with our response to accessibility concerns:

1. Contact us directly at [email protected] with specific details
2. We will acknowledge your complaint within 2 business days
3. We will investigate and provide a detailed response within 10 business days
4. If needed, we will work with you to develop a timeline for addressing the issue

8. Technical Implementation

8.1 Code Standards

• Valid HTML: All pages use valid, semantic HTML5
• CSS Accessibility: Styles support user preferences for motion, contrast, and font size
• JavaScript Enhancement: Progressive enhancement ensures functionality without JavaScript
• Performance: Optimized loading times to support users with slower connections

8.2 Testing and Validation

• Automated Testing: Regular use of accessibility testing tools (axe, WAVE, Lighthouse)
• Manual Testing: Keyboard navigation and screen reader testing
• Color Contrast: All color combinations verified to meet WCAG AA standards
• Focus Management: Proper focus flow and visual indicators tested across all browsers

9. Legal Framework and Compliance

9.1 Legal Standards

Our accessibility efforts are guided by:

• Americans with Disabilities Act (ADA): U.S. federal disability rights legislation
• Section 508: U.S. federal accessibility standards for electronic content
• European Accessibility Act: EU accessibility requirements for digital services
• WCAG 2.1: International accessibility guidelines Level AA compliance

9.2 Geographic Considerations

• Global Access: Cloudflare CDN ensures accessible content delivery worldwide
• EU Compliance: Blog service (Germany) complies with European accessibility directives
• US Standards: Status page (US) and Netlify services meet American accessibility requirements

Conclusion

Accessibility is an ongoing commitment, not a one-time achievement. We continuously work to improve the accessibility of all JustKrith platforms and welcome your feedback in this effort.

Questions about accessibility? Contact us at [email protected]. We're here to help ensure everyone can access and use our platforms effectively.

Thank you for helping us create a more inclusive digital experience!