The customer found the product. The price works for them. They want to order. But the variant selector cannot be used with a keyboard. Or a form signals an error only with a red outline, without explaining what needs correction.
The report may show an incomplete order. Without examining the experience, it is easy to turn immediately to price, interest or retargeting. Sometimes the first question should be whether the person could actually continue.
Digital accessibility means designing and developing content and functionality that people with disabilities can also use. It requires attention to the whole journey, from information to confirmation of the action.
People use the website in different ways
Some navigate with a screen reader. Others use a keyboard, voice commands or enlarged text. People may have visual, hearing, movement or information-processing difficulties, and needs differ between individuals.
An accessible website can also help in temporary or situational circumstances: an immobilized hand, bright light on a screen or an environment where sound cannot be used. W3C explains the connection between accessibility and varied conditions of use. W3C: introduction to web accessibility
A demographic profile cannot tell us our audience does not need these features. An absence of complaints does not confirm that everyone interested could use the website.
Design needs to remain usable
Subtle text can support a visual direction, but important information must be readable. An animation may explain a product, but should not be the only way to understand the offer or prevent people from controlling the page.
We examine contrast, text resizing, information order and interactive behavior. Visual identity is developed alongside these requirements. The result needs to work on the user’s screen and in their circumstances, beyond the design presentation.
Accessibility also concerns independence. People should be able to decide and act without being forced to ask for help because of a barrier created by the interface. A phone number can complement the experience, but does not automatically resolve an unusable checkout.
There are concrete criteria to check against
WCAG is a set of W3C recommendations for web content accessibility. Version 2.2 organizes criteria around perceivable information, operable interfaces, understandable content and robust compatibility with technologies people use. W3C: WCAG 2.2
We agree on the version, target level and evaluation scope. Checking a few pages does not justify a claim about every website feature. Technical conformance, actual experience and legal obligations need evaluation according to their purposes.
For a store, the important journey includes product selection, basket, authentication where required, payment and confirmation. For a service, it may include choosing a date, submitting an inquiry and receiving a response. One barrier can stop the entire journey.
Forms should explain what is happening
A form needs clear labels and relevant instructions. If information is missing or entered in the wrong format, the message should identify the problem and help correct it. Final confirmation should be perceivable, including through assistive technologies.
W3C recommends clear feedback for both errors and successful submission. Feedback can be associated with a field and complemented by an overall message suited to the interaction. W3C: form notifications
These details also affect trust. After pressing the button, people need to understand whether the inquiry was sent and what happens next. An ambiguous screen may lead them to repeat the action or contact support just to confirm receipt.
Images and video need appropriate alternatives
An informative photograph needs a text alternative suited to its role. A purely decorative element is treated differently. If product dimensions appear only in an image, that essential information also needs to be available without visually reading the image. W3C: image alternatives
For video, we prepare accurate captions and alternatives appropriate to the information, including descriptions of relevant visual content where needed. A transcript can help, but cannot alone satisfy every requirement for every material. W3C: accessible audio and video
Page copy should remain clear. Button and link names should help people understand where they lead. These are communication choices too: explaining a product in a form the audience can use.
Can the person continue?
Check complete tasks using different ways to interact.
Understand the offer
Legible, structured information in appropriate forms.
Choose a variant
Navigation and selectors the person can control.
Complete the action
Usable forms, booking and payment.
Receive confirmation
Clear feedback, including when an error needs correcting.
An explanatory diagram. Application depends on the project and its data.
An example: the interest exists, but booking is blocked
Imagine a creative workshop platform. Someone navigating by keyboard chooses a course and tries to select a date. The calendar responds only to a mouse, and the visible focus indicator disappears in the booking window.
They can understand the offer but cannot complete enrollment independently. The team sees traffic and few bookings. A discount or another ad shown to the same person will not repair the selector.
This is a fictional example. It shows why investigation needs to include interactive components and navigation methods. After a fix, we retest the whole journey, including errors and confirmation. We do not attribute a percentage improvement to the intervention without supporting data.
An automated score is only part of the check
Automated tools can identify some problems and help track them. W3C explains that a tool alone cannot establish whether a website meets accessibility standards. Competent evaluation is needed, with manual checks and, where possible, participation from users with disabilities. W3C: evaluating accessibility
A useful report states what was evaluated, under which conditions, which barriers were found and what needs correction. We prioritize obstacles by severity and effect on tasks. Retesting confirms whether an intervention resolved the observed problem.
Installing a widget does not prove the structure, forms and integrations are accessible. We check the resulting behavior. Public conformance claims need to match the evaluation and the scope we can support.
Understanding the legal context
In Romania, Law no. 232/2022 covers certain products and services, including consumer ecommerce, with application from 28 June 2025 under the conditions set by the law. There are exemptions and transitional provisions, including an exemption for microenterprises providing services. Its definition must be checked separately from Romania’s tax regime also called “micro.” Applicability depends on the actual activity. Law no. 232/2022: scope and obligations
A WCAG score is not a universal certificate of legal compliance. In a project, we establish applicable requirements and who validates technical assessment and legal interpretation. This article provides context for that discussion; it does not determine every business’s legal position.
Accessibility needs to be maintained after launch
A new page, payment integration or booking module can change the experience. Later content needs the same attention: headings, image alternatives, documents and video.
Responsibilities and checks therefore belong in the working process. W3C recommends integrating accessibility into planning, implementation and monitoring. W3C: planning and managing accessibility
At NOT MORE., we connect communication, design and development to the actions people need to complete. A new website does not automatically make buying easier develops the same perspective. Depending on the project, we work with the specialists needed for evaluation and implementation and prioritize changes based on observed problems.
Evaluation should lead to practical fixes
NOT MORE. can take on the agreed analysis, content, design, development and checks to improve website use. If a developer is already designated, we establish which fixes we deliver, which they own and how changes are confirmed. The client facilitates access and validates information and commercial priorities.
Handover describes what was checked and the evaluation’s limitations, without implying certification of the entire website. For monitoring and maintenance, we agree on who checks later changes, including new pages and components. Accessibility and usability need to remain part of subsequent production.