Accessibility Statement
Commitment to Accessibility
We are committed to ensuring that this blog is accessible to all users, including those with disabilities. Our aim is to provide an inclusive reading experience and comply with internationally recognized accessibility standards such as the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.
Scope of This Statement
This accessibility statement applies to this blog and its contents, including all posts, pages, links, embedded media (such as videos or documents), and interactive elements provided by us.
Current Accessibility Status
This blog is partially compliant with WCAG 2.1 Level AA. Most of the content is accessible, but some limitations remain.
Non-Accessible Content
Known Limitations
Some embedded media (e.g., YouTube, Vimeo videos) may lack captions or transcripts.
Certain documents or media previews may not be fully optimized for screen readers.
Posts published using older templates may include structural issues (e.g., heading hierarchy).
Interactive components such as embedded viewers or third-party widgets may not offer full keyboard or screen reader support.
Disproportionate Burden
In some cases, adapting third-party content or legacy embeds to full accessibility standards would involve significant technical effort. These cases are considered a disproportionate burden under applicable regulations.
Content Outside the Scope
Content originating from third-party sources or added before September 2018 may not fall under the current legal requirements and may not be fully accessible.
Evaluation Methods
We perform regular accessibility checks using the following tools and practices:
Axe DevTools
WAVE Accessibility Checker
Chrome Lighthouse
Keyboard navigation testing
200% zoom compatibility
Last Evaluation Date: May 2025
Review Cycle: Every 6 months
Feedback and Contact
If you encounter any accessibility barriers while using this blog or have suggestions for improvement, we welcome your feedback.
Contact details can be found below on this page. We will do our best to respond in a timely manner.
Enforcement Process
If you believe your concern has not been adequately addressed, you may reach out to the relevant accessibility authority in your country or region, in accordance with your local laws and guidelines.
Email: to be defined
Date: "CURRENT_DATE variable"- so it matches the date when deployed ?
