Accessibility Policy

DRKNYT believes access is part of product quality, not a final compliance pass. We want people with different bodies, senses, cognition, devices, bandwidth, languages, and ways of interacting to be able to understand and use our work.

We design toward current recognized accessibilityaccessibilityMaking information and controls usable by people with different abilities and ways of interacting.Open the source ↗Close explanation guidance, with WCAGWCAGWeb Content Accessibility Guidelines: testable requirements for making web content more accessible.Open the source ↗Close explanation 2.2 Level AAAALevel Double-A: the middle level of the Web Content Accessibility Guidelines. It includes the applicable basic and intermediate requirements.Open the source ↗Close explanation as a practical target for public web experiences where applicable. A target is not a claim that every surface is already conformant.

Access includes understanding the intended meaning, not just operating an interface. We aim to preserve the subject, context and symbolism of an image across supported screen sizes and ways of accessing the content.

Cropping, overlays, text and motion should not remove or change essential meaning. When an image cannot be seen, its essential meaning should remain available through appropriate text. Decorative images should not create unnecessary noise for assistive technology.

Semantic structure, meaningful descriptions, source attribution and machine-readablemachine-readableStructured so software can identify the content and its meaning instead of guessing from appearance.Close explanation representations help assistive technology and other systems interpret content and its relationships. Machine access is another access pathway; it is not equivalent to the needs or experiences of people with disabilities.

• Semantic structure, logical reading and focus order, and keyboard access.
• Sufficient contrastcontrastThe measurable brightness difference between foreground information and its background.Close explanation, visible focus, understandable labels, and useful error messages.
• Text alternatives for meaningful images and captions or transcripts for meaningful audio and video where practical.
• Layouts that tolerate zoom, larger text, small screens, reduced motionreduced motionA device preference asking interfaces to limit nonessential movement and animation.Close explanation, and different input methods.
• Plain language, progressive disclosureprogressive disclosureShowing the information needed now while keeping more detail available when it becomes useful.Close explanation, and alternatives when an interaction is not usable by everyone.

DRKNYT includes prototypes, experiments, third-party services, and work in active development. Some experiences may not yet meet this standard. Automated test success alone does not prove accessibilityaccessibilityMaking information and controls usable by people with different abilities and ways of interacting.Open the source ↗Close explanation.

When someone identifies a barrier, we want to understand the affected task, device, assistive technology, route, and urgency. We will record, prioritize, and correct verified barriers rather than treating accessibilityaccessibilityMaking information and controls usable by people with different abilities and ways of interacting.Open the source ↗Close explanation feedback as cosmetic.