Digital Accessibility addresses barriers that prevent people with disabilities from perceiving, understanding, navigating, and using digital experiences. It depends on the decisions made across design, content, technology, and the ongoing care of a product.
At Abstraction Creative, accessibility is one of the ways empathy becomes a practical responsibility. It asks us to consider people whose way of experiencing a product may differ from our own—and to let that understanding change what we make.
A welcome on the homepage means little if someone cannot get through the next interaction.
Whose independence does the design assume?
A website or application can appear straightforward while relying on assumptions about sight, hearing, movement, cognition, or the technology someone uses.
Perhaps the only indication of an error is a change in color. Perhaps an important explanation exists only in a video. Perhaps an action works with a mouse but cannot be reached from a keyboard.
For the person encountering that barrier, the consequence is not an abstract quality score. It may be needing help with something they should be able to do independently, losing access to information, or giving up on a task that matters to them.
We want to understand those consequences without speaking for everyone who experiences them. Empathy motivates the work; people's lived experience and appropriate technical expertise deepen it.
Accessibility is not something an audience has to earn by appearing large enough in an analytics report.
A welcome becomes meaningful when someone can take part.
What the work is composed of
Information people can perceive
Visual design needs to consider legibility, contrast, hierarchy, and what happens when someone enlarges the content. Color can contribute meaning without carrying essential meaning alone.
Images and media need appropriate alternatives. Depending on the material, that can mean a useful text description, captions, a transcript, or description of important visual information. The purpose is to communicate what matters, not merely attach a field to an asset.
For Abstraction, this is also a content question: what is the image or experience saying, and how can that meaning remain available through another form?
Interactions people can operate
We consider how people reach controls, understand where they are, and move through an experience using relevant input methods and assistive technologies.
Keyboard behavior, visible focus, control states, and the ability to move into and out of interactive elements need deliberate treatment. Motion, time limits, and gestures deserve attention where they affect someone's ability to participate.
The answer is not to add every possible interaction to every product. It is to avoid making a particular action or input an unnecessary barrier and to evaluate the alternatives the experience needs.
Content people can understand
Meaningful headings, useful labels, clear instructions, and understandable error messages help people interpret what is happening. We look at what an action promises and whether the result supports that expectation.
Writing can retain character while making a requirement clear. The task may be complex; the explanation does not need to make it more difficult. Content Design, Information Architecture, and UX Writing all contribute here.
Structure technology can communicate
An interface has more than a visual structure. Its implementation needs to communicate relationships, control names, states, and changes to the technologies people use to access it.
A heading that only looks like a heading, or a control that has no meaningful accessible name, can lose important information outside the visual presentation. Design and development need to agree on the intended structure and behavior, then examine the built result.
The design file is not the finished experience.
Consider the whole digital path
When we shape an exhibition's digital experience with a cultural organization, we consider the invitation and the practical path together. The work needs to communicate the exhibition's character while helping visitors understand access information, choose a time, obtain a ticket and use the confirmation on arrival.
We ask the team what the artwork, photography and movement contribute, then work through how their meaning remains available. That can involve useful descriptions, understandable supporting information and choices about optional motion. Creative expression and access inform one another; neither is resolved by declaring the site visually simple.
We follow the task into ticket selection, error recovery and the confirmation sent outside the website. Can people operate the controls and understand what happened? Where do content, design and implementation need a shared decision?
If a third-party ticketing service forms part of the route, we identify that dependency and involve the responsible provider. A considered introduction does not cancel a barrier in the purchasing path. We agree what can change, who follows it up and what support is available while the underlying issue is addressed.
The physical visit needs its own consideration. Customer Experience Design and Architectural Design help connect those questions without pretending a digital review assesses the venue. Working through the whole path makes the responsibilities easier for the organization to understand and sustain.
Standards give us a shared reference
The Web Content Accessibility Guidelines, or WCAG, provide a recognized technical reference for web accessibility. An engagement should identify the applicable version, target level, product scope, and evaluation approach rather than rely on the word “accessible” without explanation.
Standards help us be specific about requirements. They do not remove the need to understand the person, the task, and the context. A technical finding and someone's difficulty completing a meaningful task can contribute different evidence.
We support standards-informed design, evaluation, and remediation. We do not present that work as legal certification or a guarantee that every person will encounter no difficulty. Where legal requirements need interpretation, qualified legal advice is a separate responsibility.
That honesty should make the work more useful, not less ambitious.
Build the responsibility into the process
Discover → Define → Explore → Design / Develop / Market → Learn → Advance → Discover
Discover helps identify the audience, existing barriers, relevant technologies, content, and organizational constraints. Define establishes requirements and priorities. Explore gives us room to consider different ways of meeting the need before a particular treatment becomes expensive to reconsider.
During Design and Development, accessibility affects components, content, behavior, and implementation. In Marketing, the same care needs to reach campaign pages, emails, media, and other material through which people encounter the organization.
We can contribute design and content work, coordinate implementation, and collaborate with accessibility specialists according to the product and scope. Clients and partners bring knowledge we should not assume we already possess.
Responsibilities need names as well as intentions. Who writes the media alternatives? Who implements a control's behavior? Who evaluates it? Who can change a third-party component? The answers help keep accessibility from becoming everyone's concern but nobody's task.
Evaluate with more than one kind of evidence
Automated checks can help identify certain issues. Expert review, manual interaction checks, and evaluation with assistive technology address questions an automated report cannot settle by itself.
Involving people with disabilities adds an essential perspective on the experience of using the product. Their participation complements standards-based evaluation; a small study cannot represent every disability or prove that every requirement has been met.
An Accessibility Audit provides a defined assessment and prioritized findings. Remediation turns recommendations into changes, and follow-up evaluation examines those changes. These are connected responsibilities, but they are not the same activity.
We agree the appropriate combination rather than describing a single tool or a quick visual review as comprehensive assurance.
Begin with the experience, not a promise of a perfect score
Where do we start with an existing product? Bring the known concerns, important tasks and any previous findings. We can help establish an appropriate Accessibility Audit or work from usable evidence toward Accessibility Remediation. A whole-site rebuild is not the predetermined answer.
Can we keep the character of our design? Yes. We examine what the expression contributes and where it creates a barrier, then explore how to preserve meaning and personality through usable alternatives. The decisions deserve design attention, not a blanket instruction to remove everything distinctive.
A product can change; its access needs attention too
A new component, a content update, an embedded service, or a change to a shared template can affect accessibility after launch.
Digital Design Systems can preserve tested patterns and document how to use them. Content Operations can give editors useful guidance and review responsibilities. Neither removes the need to examine a changed experience.
The work can leave the client with requirements, annotated designs, content guidance, component decisions, documented findings, and a plan for what needs further attention. The exact mix depends on the engagement.
Learn and Advance return new knowledge to Discover. Reports and feedback become part of the shared intelligence around the product, helping us improve the practice as well as address individual issues.
Accessibility within a wider view of inclusion
Inclusive Design considers a broader range of abilities, circumstances, identities, languages, and ways of participating across Abstraction's practices. Digital Accessibility brings focused attention to disability-related barriers in digital products and content.
The two inform one another without becoming interchangeable. We can recognize wider benefits while keeping the needs of people with disabilities central to accessibility work.
This is not simply about reaching more people. It is about taking seriously the people we already say the experience is for.
Care for the experience includes care for the ways people reach it.
Start with the experience you have—or the one you are making
Digital Accessibility can be a focused engagement or part of a broader design and development effort. We can help identify a useful starting point, assemble the appropriate expertise, and work through improvements with your team.
You do not need to arrive with every barrier diagnosed. Bring us the product, the concern, or the ambition. We can begin by understanding who it needs to serve and what stands in the way.