Accessibility Statement

Commitment and scope

Access to journalism, ideas, production, technology, and opportunities should not depend on a person using a particular sense, input method, screen size, connection, or interaction pattern. The organization’s goal is to reduce avoidable barriers in websites, applications, articles, newsletters, documents, video and audio, campaigns, forms, events, and support communications that it controls. The work should consider permanent, temporary, situational, and combined disabilities without assuming that one solution serves everyone.

This statement guides the public work of the companies described in the public organizational registry and their listed verticals while respecting their different formats and audiences. Responsibility follows control: teams should address experiences they create or procure and should identify alternatives where a third-party limitation cannot reasonably be removed. A link, embed, distribution channel, venue, client engagement, or collaboration does not give the organization control over every external experience.

Axis News Network

News and editorial. This statement also guides work presented through Axis Climate, Axis Sports, Axis Health, Axis Space, Axis HBCU.

HUMAN Ideas Company

Communications and creative.

Positive Space Productions

Film and video production.

Structure, navigation, keyboard, and input

Digital experiences should use semantic structure and predictable interaction so people can understand where they are, move efficiently, and complete core tasks without a mouse. Page titles, headings, landmarks, labels, instructions, link purpose, status changes, and error messages should provide meaningful orientation. Visual order and programmatic reading order should remain coherent, including when content is zoomed, reflowed, translated, or viewed on a small display.

• Make interactive controls reachable and operable by keyboard, with a visible focus indicator and a logical focus sequence.
• Avoid keyboard traps; provide a practical way to bypass repeated navigation and return from dialogs, menus, media, and overlays.
• Give controls accessible names that describe their purpose, and do not rely only on icon shape, color, position, hover, or gesture.
• Associate form labels, instructions, required status, validation, and errors with the affected fields; preserve entered information when feasible.
• Support reasonable zoom, text spacing, orientation, touch target, and reflow without obscuring essential controls or requiring unnecessary two-dimensional scrolling.

Authentication, security, maps, visualizations, drag interactions, and complex creative interfaces can create particular barriers. Teams should consider accessible input, recovery, instructions, and equivalent paths early in design. An inaccessible challenge or single interaction should not be the only route to a core action when a reasonable alternative can be offered.

Visual presentation, language, and cognitive access

Text and essential interface elements should have sufficient visual distinction for their context, and information should not be communicated through color alone. Teams should consider contrast, typography, line length, spacing, hierarchy, magnification, forced colors, dark or light presentation, and images behind text. Images that convey information should have a suitable text alternative; decorative images should not add noise to assistive output. Complex charts and graphics should provide the underlying conclusion or data in another understandable form where practical.

Clear language benefits people with cognitive, learning, language, and attention disabilities. Headings should preview content; instructions should state the action and consequence; unfamiliar abbreviations and specialist terms should be explained where audience context requires it. Long legal, research, health, finance, technology, climate, political, sports, space, or education material may remain substantively complex, but complexity should come from the subject rather than avoidable sentence structure or interface ambiguity.

• Use consistent navigation and naming for repeated actions.
• Allow enough time or provide extension, pause, save, or restart options when timing is not essential.
• Avoid unexpected context changes on focus or data entry.
• Provide correction before consequential submissions and avoid making essential tasks depend solely on memory or rapid reaction.

Motion, animation, flashing, and sensory effects

Motion can communicate change and support storytelling, but it can also trigger vestibular symptoms, seizures, distraction, or loss of orientation. Nonessential animation and autoplay should be restrained. Experiences should respect available reduced-motion preferences where practical, preserve content and function when effects are reduced, and provide pause, stop, dismiss, or static alternatives for motion that starts automatically or continues alongside other content.

Content should avoid flashing patterns known to create seizure risk and should not rely on parallax, rapid zoom, strobing, or large unexpected movement to perform a core task. When motion is essential to an artistic, scientific, or explanatory work, the surrounding experience should provide advance context and a less motion-intensive way to reach the material’s essential information where reasonably possible.

Audio, video, live media, images, and documents

Prerecorded video with meaningful speech should aim to provide synchronized captions, and audio-first material should aim to provide a transcript or equivalent summary appropriate to its purpose. Captions should identify speakers when needed, include relevant non-speech sound, and reflect the communication rather than merely displaying unreviewed automated output. Important visual information not available from the soundtrack should be addressed through audio description, integrated narration, a descriptive transcript, or another usable alternative according to the work and resources.

Live media presents additional constraints. Teams should consider live captions, interpreters, advance materials, moderated question channels, recordings, and corrected post-event transcripts based on audience need and event significance. If an accommodation or alternative cannot be available simultaneously, that limit should be communicated honestly and another useful route should be explored. This is an aim, not a promise that every live session will offer every service.

• Do not autoplay sound without a readily available control.
• Ensure media controls have accessible names, focus behavior, and status information.
• Use meaningful alternative text and avoid repeating captions verbatim when that creates unnecessary duplication.
• Create tagged, selectable, logically ordered documents when the format supports it; provide an accessible web or text alternative when a document remains a barrier.
• Preserve captions, transcripts, credits, warnings, and accessibility information when media is republished across channels where feasible.

Editorial work, productions, communications, and events

Accessibility should enter planning before a story, campaign, shoot, software feature, event, or deliverable is locked. Plans should address accessible formats, captions or description, delivery, review, and participant communication methods. Disability, speech, assistive technology, interpreters, or accommodations should not be framed as evidence about intelligence or credibility. Event planning may consider step-free routes, seating, restrooms, quiet space, service animals, interpreters, caption visibility, microphones, lighting, remote participation, evacuation, and an access contact. Specific features must be confirmed for the event rather than inferred from this statement.

Third-party services, archives, and known limitations

The organization may rely on external video players, social media embeds, maps, analytics, consent tools, ticketing, payment, document, newsletter, hosting, distribution, or event platforms. Their accessibility can change without the organization’s control. Procurement and integration should consider accessibility evidence and critical-task alternatives, but inclusion of a third party does not establish that the service is fully accessible or that the organization can remediate its underlying code.

Archives may include older articles, documents, media, interactive projects, or acquired material created under different tools and expectations. The aim is to prioritize active and high-use experiences, essential tasks, significant public-interest material, and barriers reported by users. Retrofitting may be limited by missing source files, rights, technology, cost, or the integrity of the historical record. A usable alternative, targeted repair, transcript, description, or assistance may be more effective than changing every legacy asset in the same way.

When a known third-party or archival barrier affects a requested task, the team should seek an alternative within its practical control and avoid overstating equivalence. An alternative should convey the essential information or permit the essential action with comparable dignity and without unnecessary disclosure or cost to the requester where reasonably possible.

Evaluation, testing, procurement, and improvement

Accessibility evaluation should combine automated checks, keyboard review, zoom and reflow review, semantic inspection, media and document checks, and task-based use with assistive technologies appropriate to the experience. Automated results are indicators, not proof of usability or conformance. Testing should prioritize core journeys and include people with disabilities when practical and appropriately supported, without treating a small sample as representative of every user.

• Prioritize issues that block essential content or tasks, create safety risk, or affect many experiences.
• Record enough reproduction detail to distinguish a content, design, code, platform, device, or assistive-technology interaction.
• Retest meaningful fixes and watch for regressions in shared components and publishing workflows.
• Train roles for the accessibility decisions they make, and use feedback to revise priorities while protecting personal information.

Report a barrier or request assistance

Accessibility barriers and requests for a usable alternative may be sent to info@positivespacemedia.com. To help route the request, include the page, document, video, event, feature, or task; the address or title; what you expected to do; what happened; and the format or assistance that would be useful. Browser, device, operating system, and assistive-technology details can help reproduce a technical issue but are optional. Please describe only what is needed; a person does not need to disclose a diagnosis to request access.

Do not send passwords, payment-card information, government identifiers, full medical records, or other highly sensitive information through ordinary email. If the inaccessible task involves sensitive information, send a brief description and ask for a suitable next step. Email is not continuously monitored and is not an emergency channel. The organization aims to acknowledge and assess useful reports, but this statement does not guarantee response or remediation within a particular period.

A response may provide instructions, an alternate format or channel, human assistance, a temporary workaround, notice of a third-party limitation, a planned correction, or an explanation that the requested change cannot presently be made. Privacy, rights, security, technical feasibility, and control over third parties can affect the available response. Reporting a barrier does not create an attorney-client, health-care, employment, fiduciary, or other professional relationship.

Statement status and updates

This statement expresses accessibility goals and operating expectations. It is not evidence that every page, asset, workflow, venue, or supplier has been tested, that all barriers are known, or that conformance with a technical standard or legal requirement has been achieved. Accessibility and legal obligations vary by context, and no unresearched legal conclusion should be inferred from these general commitments.

The statement may be revised as experiences, suppliers, content, technology, feedback, and organizational capacity change. A revision may clarify priorities without implying that earlier material was inaccessible or that every new aim was previously operational. The September 18, 2026 date records the public update and is not a legal effective date.

Nothing in this statement creates a contract, warranty, service level, private certification, employment term, or waiver of rights. Applicable law and signed agreements remain controlling. A person who needs advice about legal rights should consult an appropriately qualified independent adviser.