Check what a tap can reach, not just what the screen shows
On October 23, I completed a local correction to three groups of candidate-facing issues on locdemunca.ro. Mobile navigation could overlap controls in job overlays, dashboard content did not always fit the phone layout, and some English interactions still used Romanian text. These were visible details, but the acceptance question was practical: could someone understand the screen and operate the control they were looking at?
The filter and job-preview overlays needed to sit above the fixed navigation. The checks reproduced a failed pointer hit on the affected action before correcting its layer. This matters because a button can be drawn on the page while another element receives the tap at that position. Looking only for the button's text would miss the problem. The correction stayed within those overlays instead of moving the shared navigation or changing employer layouts.
The candidate dashboard also received responsive grid adjustments. Cards used a smaller column count on phones, while the chart and interview areas stacked rather than competing for a narrow width. The changes preserved the existing information and actions. The English copy correction covered the reported shell labels, CV title, job controls, employer-verification explanation and plan features, keeping shared Romanian defaults and employer behavior intact where those components were reused.
The dated record closes a local implementation endpoint. Romanian and English checks used phone and desktop dimensions, actual mobile navigation and isolated response fixtures. They verified that the filter action received the tap, dashboard content fitted and the identified platform-owned English text was English. Some shared and legacy content remained outside that specific list. The work did not establish deployed behavior or physical-phone acceptance, and no production account data was changed during the checks.
Reflection
A mobile screen needs both spatial and linguistic clarity. On locdemunca.ro, the useful checks connected the rendered layout to the action underneath it and the language around it. A visible button, a fitted panel and a translated heading are each incomplete unless the surrounding interaction also works.