Philosophy & Commitment Standard Reference
For Kartunet, digital accessibility is not just a technical checklist or paper compliance. It is a Manifesto of Inclusion. Launched on January 19, 2006, as the first website initiated by the blind community in Indonesia, Kartunet has now evolved into a Living Benchmark of how a modern media platform is built accessibly without sacrificing aesthetics.
We are fully committed to maintaining the Web Content Accessibility Guidelines (WCAG) 2.1 Level AAA standard. This website is designed as a real-world reference space for web designers, corporations, and academics to see first-hand how accessibility code is implemented at production scale.
Main Technical Implementation (Next.js & Supabase Architecture)
The Kartunet platform integrates cutting-edge accessibility technology end-to-end, including:
- Dynamic Content Accessibility: Disiplined use of
aria-liveregions to provide instant, real-time feedback on contact forms, the audio player, and external announcement alerts. - Landmark Navigation & Keyboard Focus: Rigorous use of pure HTML5 semantic elements and logical Focus Order management for seamless mouse-free navigation.
- Inclusive Monetization Free from CLS: Rejection of automated ad systems (Auto Ads) that disrupt layouts. We implement isolated manual ad units wrapped in
<aside aria-label="Advertisement">tags with min-height constraints to prevent cumulative layout shifts (Zero CLS). - Adaptive Cross-Ecosystem PWA: Our Progressive Web App (PWA) supports push notifications and includes a visual guide banner for manual installation tailormade for cognitive accessibility on iOS Safari.
- Extreme Contrast & Visual Optimization: Ensuring a minimum contrast ratio of 7:1 for normal text elements, avoiding visual camouflage, and supporting automatic integration with the user's OS high-contrast preferences.
Testing Methods (Lived Experience Testing)
Beyond automated compliance checkers, every line of component code on Kartunet is regularly and manually tested by our Access Squad team using their lived experiences across various Assistive Technologies:
- • NVDA (Windows)
- • VoiceOver (macOS / iOS)
- • TalkBack (Android)
- • JAWS (Windows)
Limitations & Continuous Improvement Efforts
Digital inclusion is an ongoing process of adaptation. Minor limitations that might still be found during our technology migration process include:
- Legacy Content Archive: Some articles or community essays submitted in the past, before strict alternative text standards were enforced, are currently undergoing curation.
- Multimedia Content: A few legacy audio-video files from the community archives have not yet been fully equipped with narrative text transcripts.
We minimize this by equipping every external contributor with strict writing guidelines via the Inclusive Writing Guide module before their work is approved for publication.
Feedback & Technical Support
If you find any code elements that violate accessibility, hinder screen reader devices, or if you require alternative data formats, our technical team is ready to process your report:
Every accessibility complaint ticket will be evaluated directly by our blind accessibility auditors with a guaranteed maximum response time of 2 business days.