A reader finds a helpful real-estate article. She then wants to open a checklist and return to the appropriate explanation. With the mouse the demonstration works immediately. Using the keyboard, the team already loses orientation at the topic menu. That is a different question from the readability of the text: the path to the information must be operable.
This in-house commission workshop is aimed at real-estate companies in Austria and Germany. It uses W3C explanations as technical guidance. It neither decides on the application of national accessibility laws nor certifies a fully accessible website.
Select a complete path
The team starts with a reader task, not with a collection of individual buttons. In the fictional example the task is: find a suitable article, reach a related checklist and then continue reading at the correct place. This includes navigation, selection, opening and the way back.
The editorial team describes what should happen at each step. They do not have to invent a keyboard command for this. The technical support clarifies the suitable operation and later the actual implementation. A nicely drawn design alone does not yet show how a person can move through the published version.
The W3C explanation for 2.1.1 requires that functionality be operable through a keyboard interface, with the exception there for underlying path-dependent inputs. It does not require making every visible mouse-operated area itself focusable if the same or a comparable action is possible via an appropriate keyboard route. [KEY]
For the commission the reachable result therefore counts. The team does not look for artificial objections to each individual deviation from the mouse route. It asks how the affected person can accomplish the same meaningful task and recognise that route.
Recognise where the next input will take effect
In the demonstration of the pattern the operation jumps on, but no one can see which element is currently selected. An impatiently repeated input eventually opens an unexpected area. The observation is not only “keyboard sometimes doesn’t work”, but: the effect of the next action is unclear due to a lack of visible orientation.
W3C describes in 2.4.7 an interaction mode with a visible keyboard focus. The visible indication should not disappear after a short time. The explanation takes into account that browsers may only show it when keyboard operation is used. [FOCUS]
The team therefore does not demand arbitrary outlines around everything. It requests a comprehensible visible orientation of the elements that are actually focused. Concrete design, contrast and further technical requirements remain the subject of an appropriate specialist review.
Distinguish between text comprehension and an operability barrier
In the example the label of the download is clear, but the associated control is not reachable. Elsewhere the element is operable but is labelled only “More”. These observations need different improvements. Better link text does not fix a missing operability route; a technical keyboard binding does not clarify an unclear content.
The editorial team therefore records position, initial state, intended result and actual observation separately. It does not write a suspected technical cause into the report if it does not know it. “After opening I can no longer find the promised way back” is at first a verifiable finding.
For later coordination, dedicated test content is used. The team can include longer article titles, multiple hits and an empty search state. This selection is an editorial recommendation to cover a reader task, not a complete technical test standard.
Review the corrected version along the same path
After an agreed revision not only the previously criticised element is shown in isolation. The person responsible goes through the complete selected path again and documents the concrete version as well as the conditions actually tested.
A successful run can show that this task now works under these conditions. It does not permit a blanket statement about every form, every browser combination or every assistive technology. Other important reader paths are planned separately with justification.
The real-estate company thus receives an actionable design brief: people should be able to reach required information independently and be able to recognise where their input takes effect. The initial question remains the concrete reading and continuing work, rather than judging the website only from the convenient perspective of the mouse demonstration.