Kaya Development is committed to making kayadevelopment.com accessible to as many people as possible, including people who use assistive technologies. We design and build the site against the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, and we keep accessibility on the engineering team's running checklist rather than as a one-off audit.
Current conformance
This website is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means that some content does not fully meet the standard. We list the known gaps below and the timeline for fixing them.
What we have done
- Semantic HTML structure: headings in a logical order, landmarks (header, nav, main, footer), form labels paired with inputs.
- Keyboard accessibility: every interactive control is reachable and operable with keyboard alone; focus styles are visible.
- Colour contrast: text on background meets or exceeds 4.5:1 for body copy and 3:1 for large text and UI components.
prefers-reduced-motion: scroll-triggered animations, chart draw-on effects, and transitions short-circuit to their final state when the user has reduced motion enabled.- Image alt text: meaningful images carry descriptive alt text; decorative images are marked accordingly.
- Responsive design: content reflows down to 320px width without horizontal scrolling.
- Live data widgets (World Bank Open Data API exhibits) render text-equivalent values alongside SVG charts so the data is available to screen readers.
Known limitations
- Some SVG exhibits in older reports lack inline ARIA descriptions; we are progressively adding them.
- Podcast player on Development Talks pages is a UI mock; full audio descriptions and transcripts are being added episode by episode.
- PDF downloads on selected reports may not yet be fully tagged for screen readers; HTML versions of the same content are available where possible.
We aim to close these gaps progressively. If a specific limitation affects you, we want to hear — contact details below.
Feedback & help
If you encounter an accessibility barrier, or you need content in an alternate format, please email accessibility@kayadevelopment.com. We aim to respond within five working days. Please describe the page or content, the issue you experienced, and your preferred contact method.
Formal complaints
If we are not able to resolve your concern, you may escalate to the relevant national body. In Türkiye, we recommend contacting the relevant ministry; in the EU, your national equality body; in the UK, the Equality and Human Rights Commission.
Technical specifications
Accessibility relies on the following technologies: HTML, CSS, JavaScript (progressive enhancement), and SVG. These are reasonably-current standards. The site is tested on the latest two versions of Chrome, Firefox, Safari, and Edge, with NVDA, VoiceOver, and TalkBack as the primary screen readers in our testing rotation.
Assessment approach
We use a combination of self-evaluation (axe DevTools, Lighthouse, manual keyboard walks), informal user testing with people who rely on assistive technologies, and periodic third-party audits. The next external audit is scheduled for Q4 2026.