Accessibility Statement
Last Updated: January 2026
Our Accessibility Philosophy
Accessibility is not an afterthought—it's a core principle in our design and development process. We strive to:
Visual Accessibility
- High contrast color schemes for better readability
- Responsive text sizes that scale with browser settings
- Proper semantic HTML structure for screen readers
- Alternative text for all meaningful images
- Keyboard-friendly navigation throughout the site
Keyboard Navigation
Our website can be fully navigated using only a keyboard:
- Tab key navigation through all interactive elements
- Clear visual focus indicators
- Logical tab order following visual layout
- Keyboard shortcuts for common actions
- Skip navigation links for screen reader users
Screen Reader Compatibility
- Proper ARIA labels for interactive elements
- Semantic HTML structure (headings, landmarks, lists)
- Descriptive link text (not just "click here")
- Code examples accessible via screen readers
- Alternative descriptions for visual content
Accessibility Standards
We aim to comply with the following accessibility standards:
WCAG 2.1
Web Content Accessibility Guidelines Level AA
Target LevelMobile Accessibility
Responsive design for all device sizes
ImplementedSemantic HTML
Proper HTML5 semantic elements
ImplementedTypography
Readable fonts and text scaling
ImplementedAccessibility Features
Built-in Accessibility Tools
Text Size
Use Ctrl/Cmd + to increase text size
High Contrast
Built-in high contrast mode
Keyboard Navigation
Full keyboard accessibility
Code Accessibility
Screen-readable code examples
Code Examples Accessibility
We make special efforts to ensure code examples are accessible:
Accessible Code Display
- Syntax highlighting with sufficient color contrast
- Copy buttons for code snippets
- Code descriptions for complex examples
- Keyboard navigation within code blocks
- Screen reader announcements for code changes
Feedback and Reporting Issues
We welcome your feedback! If you encounter accessibility barriers on Poetic Codes:
- Email us: pansensoyglenn@gmail.com
- GitHub Issues: Report accessibility issues on our repository
- Contact Form: Use our contact form with "Accessibility" as the subject
We aim to respond to accessibility feedback within 3 business days and to propose a solution within 10 business days.
Continuous Improvement
Our Accessibility Roadmap
We are continuously working to improve accessibility. Current focus areas:
- Implementing more detailed ARIA labels
- Adding video tutorials with captions and transcripts
- Improving code example accessibility for screen readers
- Adding a dedicated accessibility settings panel
- Regular accessibility audits and user testing
Third-Party Content
Some content on our site may be provided by third parties. While we strive to ensure accessibility of all content, we cannot guarantee the accessibility of third-party content such as:
- External code libraries and frameworks
- Linked documentation from other sources
- Embedded content from external platforms
Compliance Status
Poetic Codes is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, due to the non-compliances listed below:
Known Limitations
- Some code visualizations: Complex interactive code examples may not be fully accessible to screen reader users
- Older content: Some legacy tutorials may not meet current accessibility standards
- Third-party integrations: External tools and libraries may have their own accessibility limitations
We are actively working to address these limitations.