Tillgänglighetsrevision av globalsign.com — skannad Feb 20, 2026
Technology9 problem hittade i 2 kategorier
Form elements must have associated labels so users know what information to enter.
WCAG 1.3.1<input type="text" name="query"><select name="(no name)"><select name="gs-pricing">Add <label> elements with matching for attributes, or use aria-label.
Buttons must have discernible text for screen reader users.
WCAG 4.1.2<button><button>Add text content, aria-label, or title to all <button> elements.
Headings should follow a logical order (h1 → h2 → h3) without skipping levels.
WCAG 1.3.1<h3> "Are you ready?" (after h1)<h4> "Cloud Signatures" (after h2)<h5> "New Revenue Line" (after h2)<h4> "EXCELLENT BUSINESS SUPPORT SERVICES!" (after h2)Restructure headings to follow sequential order. Don't skip from h1 to h3.
Iframes must have title attributes describing their content.
WCAG 2.4.1<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-5DHLZW">Add descriptive title attributes to all <iframe> elements.
Element IDs must be unique to ensure correct assistive technology behavior.
WCAG 4.1.1id="gmoheadertag"Make each id attribute value unique within the page.
Pages should have a mechanism to bypass repeated navigation blocks.
WCAG 2.4.1No skip navigation link foundAdd a 'Skip to main content' link as the first focusable element on the page.
ARIA attributes must be valid and used correctly to work with assistive technologies.
WCAG 4.1.2<div aria-labelledby="concentMessageBoxLabel"> (missing ref)Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.
Interactive elements must have visible focus indicators for keyboard users.
WCAG 2.4.7<a style="...outline:none..."><a style="...outline:none...">Ensure :focus styles are visible. Don't use outline: none without a replacement.
Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.
WCAG 2.4.4<a href="/en/blog/ae/google-90-day-certificate-validity-requires-auto">learn more</a><a href="/en/blog/in/google-90-day-certificate-validity-requires-auto">learn more</a><a href="/en/blog/ae/google-90-day-certificate-validity-requires-auto">learn more</a><a href="/en/blog/in/google-90-day-certificate-validity-requires-auto">learn more</a><a href="/en/blog/ae/google-90-day-certificate-validity-requires-auto">learn more</a>Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.
Här är de mest betydande ändringarna som globalsign.com bör göra:
Add <label> elements with matching for attributes, or use aria-label.
Add text content, aria-label, or title to all <button> elements.
Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.
globalsign.com fick 14/100 (betyg F) i vår revision. Poängen återspeglar automatiserade kontroller enligt WCAG 2.1 nivå AA.
Vår skanning hittade 9 tillgänglighetsproblem på globalsign.com. Full WCAG-överensstämmelse kräver att alla kritiska och allvarliga problem åtgärdas.
Den europeiska tillgänglighetslagen kräver att webbplatser uppfyller WCAG 2.1 AA. Se den detaljerade rapporten ovan för globalsign.coms status.
Se den fullständiga problemlistan ovan med allvarlighetsgrad, påverkade element och rekommenderade korrigeringar för globalsign.com.
Få en gratis tillgänglighetsrapport på några sekunder.