cevuno*Become a Partner
Design4 min readBy CEVUNO Editorial

Accessible Interface Design: Decisions to Make Before Development

Bring readability, keyboard access, labels and understandable feedback into interface design before the frontend implementation begins.

Mono interface concept illustrating contrast, hierarchy and labelled financial information
Original CEVUNO portfolio concept, used to illustrate the topic. It does not represent a commissioned client engagement or measured business results.

Accessibility becomes easier to address when it is part of the initial interface decisions. A developer can improve semantics and keyboard handling, but cannot always repair a design that relies on tiny text, indistinguishable states or hidden instructions without changing the composition. Agencies can make the production brief stronger by stating accessibility expectations early.

Make information perceivable

Choose readable text sizes and sufficient contrast for the intended use. Do not make colour the only way to distinguish an error, selection or status. Pair visual signals with a clear label or another meaningful cue.

Images that explain something need an appropriate text alternative. Decorative images can be treated differently. Discuss what each visual contributes rather than writing the same generic description for every asset.

Design the complete interaction

Specify visible keyboard focus and ensure important information does not depend on hover. Forms need persistent labels and useful error messages. A visitor should understand what went wrong and how to correct it without relying on a temporary notification.

Plan navigation, dialogs and accordions as interactions with names, states and dismissal behaviour. Content order should remain understandable when layouts stack on smaller screens or when users navigate without a pointer.

Accessible interaction needs several layers to work togetherAccessible interaction needs several layers to work togetherReadable contentSemantic structureKeyboard operationClear feedback
Readable content, semantic structure, keyboard operation and feedback support the same task. An automated scan checks only part of that experience.

Include review in the production plan

Automated checks can find some issues, but they do not replace reviewing keyboard operation, reading order and actual task completion. Agree which standard and evaluation scope the project requires, then record the checks performed and any unresolved issues.

CEVUNO can incorporate accessibility considerations into UI design and frontend production. The precise audit, remediation or conformance scope should be agreed for the project; a general design engagement should not imply a certification or a universal compliance guarantee.

Turn accessibility expectations into design requirements

Accessible web design starts with the work someone needs to complete. For a contact page, the task includes understanding the form, entering information, finding an error and knowing whether the enquiry was sent. Each step involves visual, structural and interaction decisions. A contrast check on the final composition cannot cover the whole journey.

Specify the standard and evaluation scope required by the project with the responsible team. A general commitment to accessibility is helpful, but it should not be presented as a certification or proof of legal compliance. The agency needs a clear record of what was designed, tested and left unresolved.

Check forms as a conversation

A field label tells the visitor what to provide. Helper text explains a constraint. An error should identify the problem and offer a realistic way to fix it. Keep those roles distinct so important instructions do not disappear when a placeholder is replaced by typed content.

After submission, communicate the actual outcome. “Sent” should mean the defined delivery condition was met, not simply that a local animation finished. When an external service fails, preserve useful input where appropriate and show a recovery route. These decisions support many visitors while making the website more understandable overall.

Review keyboard and reading order together

A visual grid can appear in one order while its document structure reads in another. Check that headings, controls and supporting explanations form a logical sequence. Menus and dialogs need predictable operation, a meaningful accessible name and a sensible destination for focus when they close.

Visible focus should help someone locate the current control without relying on colour alone. Avoid making a hover effect the only route to essential information. When a layout changes on mobile, confirm that the reading order and the task still make sense.

Use automated and manual checks for different questions

Automated tools can identify certain missing labels, contrast issues and structural problems. They cannot determine whether every text alternative communicates the right meaning or whether an entire task is understandable. Include manual keyboard checks and representative task review according to the agreed evaluation scope.

W3C’s accessibility tutorials provide practical guidance for page structure, menus, images, tables and forms. Use those resources to inform decisions, then verify the implemented experience. CEVUNO can incorporate accessible UI design and relevant frontend checks into an approved scope, with any specialist audit requirements assigned explicitly.

Explore CEVUNO’s design, development and creative services or browse the portfolio concepts to see the type of production we can discuss with your agency.

Make room for your next project.

Tell us what your agency needs to produce. We’ll review the scope, estimate the work and confirm availability together. Monthly partnerships and one-time projects are available.