We open our Arkevia space to retrieve a payslip, and instead of the usual form, a field displays “no label” with no indication. It’s impossible to know what to enter, where to click, or even if the page has finished loading. This display bug regularly affects employees accessing their digital vault, often after an update or a browser change.
Arkevia “no label” bug: why the form loses its labels
The “no label” message is not a password error or an account issue. It’s a display defect of the login form: the field exists, but its text label (the HTML label that indicates “Username” or “Password”) does not load.
Read also : How to Choose the Right Climbing Plant?
Specifically, the HTML label is no longer associated with the input field. This type of break can occur after an update to the authentication process on the Arkevia side when an interface component loses its link to the text that describes it. The WCAG 2.2 standard, published on October 5, 2023, by the W3C WAI, emphasizes the explicit association between labels and form fields to avoid this kind of malfunction.
This problem also arises when the portal uses a federated authentication flow (SSO) or loads the form in an iframe. These architectures multiply technical layers, and it only takes one script not executing correctly for the labels to disappear. When looking for solutions for the no label bug on Arkevia, the instinct to clear the cache is often the first piece of advice, but it doesn’t solve all cases.
You may also like : How to Easily Find the Best Beauty Spots Near You
Browser and blocked scripts: the most common cause of the no label bug
Since 2024, several browsers have strengthened their protections against tracking and third-party scripts. Firefox, Brave, and even some configurations of Chrome now block elements that were previously loaded without restriction.
On a portal like Arkevia, which can integrate external authentication components, a script blocker is enough to break the display of the form. The field appears, but without its label, because the script that dynamically generates this text has been intercepted before execution.
Checks to make in order
- Temporarily disable all browser extensions, especially ad blockers (uBlock Origin, AdBlock, Ghostery). Then reload the page.
- Test with another browser. If the form displays correctly on Edge but not on Firefox, the problem lies with the initial browser configuration, not Arkevia.
- Clear the cache and cookies for the site myarkevia.com specifically, not just the global cache. On Chrome: Settings, Privacy, Cookies, then search for “arkevia” and delete the entries.
- Check that JavaScript is enabled. Some enterprise security suites disable JS on unreferenced domains.
Feedback varies on this point, but in the majority of reported cases, disabling the blocking extension resolves the bug immediately.
Employer portal and iframe: when the no label bug comes from the architecture
Some employers do not send their employees directly to myarkevia.com. They integrate access to the digital vault into their own HR portal, via an iframe or SSO redirection. This is where things get complicated.
An iframe loads Arkevia inside another page. The browser then applies additional security restrictions (same-origin policy, blocking third-party cookies). As a result, the Arkevia login form ends up missing its labels, or even completely empty.
Bypass the iframe issue
The most reliable solution: access myarkevia.com directly instead of going through the employer portal. Type the address into the browser’s address bar, without using an internal link from the company’s HR site.
If the employer enforces a dedicated portal with a custom URL, contact the HR department to obtain the direct authentication link. Some companies use a specific subdomain that does not have the same integration constraints as an iframe.
Persistent Arkevia bug: actions to try when nothing works
We have cleared the cache, disabled extensions, tested another browser, accessed myarkevia.com directly, and the “no label” bug persists. Here’s what remains.
First, test from a completely different device: a smartphone on 4G (not on corporate Wi-Fi). Corporate networks sometimes apply proxy filters that modify the content of loaded pages. A 4G test isolates the network problem from the browser issue.
Next, take a screenshot of the bug and send it to Arkevia support via the contact form on the site. Mention the browser used, its version, and specify if the problem also appears on mobile. This information helps the technical team identify if the bug comes from a regression on the server side.
- From a mobile device, use the system’s default browser (Safari on iOS, Chrome on Android) without any installed extensions.
- Check that the operating system is up to date: some older versions of Android no longer handle recent SSL certificates properly, which can disrupt script loading.
- If the employer provided an activation code by email, check that this email has not expired. An expired activation link may redirect to an incomplete form.
The “no label” bug on Arkevia remains a display issue, not a security issue for the vault. The stored documents are not affected. Most of the time, the workaround involves changing the browser or removing a blocking extension. When the problem arises from the architecture of the employer portal, only direct access to myarkevia.com allows for a functional form.