https://Www.tsipower.in
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
74
GRADE
C
FIX
8
REVIEW
3
PASS
13
INFO
0
Checks
2413 PASS 3 REVIEW 8 FIX
DLandmark StructureAction4 landmarksFIX
Landmark Structure
Action4 landmarks
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
3 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Why this matters
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
Multiple navigations need aria-label to distinguish them for screen readers.
Why this matters
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Why this matters
Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.
Learn more ▾ ▴
Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.
Source: WCAG 2.1 SC 2.4.1
DLink & Button QualityAction34 issue(s) across 183 links and 0 buttonsFIX
Link & Button Quality
Action34 issue(s) across 183 links and 0 buttons
34 issue(s) across 183 links and 0 buttons
Critical::
11 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: https://tsipower.in; https://tsipower.in; https://tsipower.in/toyota-kirloskar-motor-entrusts-tsis-static-voltage-regul…; https://tsipower.in/all-group-companies-of-bapasitaram-now-use-tsi-vrp/; https://tsipower.in/proudly-serving-the-ordnance-factory/; https://tsipower.in/toyota-kirloskar-motor-entrusts-tsis-static-voltage-regul…; https://tsipower.in/all-group-companies-of-bapasitaram-now-use-tsi-vrp/; https://tsipower.in/proudly-serving-the-ordnance-factory/; https://tsipower.in/toyota-kirloskar-motor-entrusts-tsis-static-voltage-regul…; https://tsipower.in/all-group-companies-of-bapasitaram-now-use-tsi-vrp/ (+1 more)
Warning::
23 link(s) with generic text
Generic link text like 'click here' doesn't describe the destination.
Got: https://tsipower.in/toyota-kirloskar-motor-entrusts-tsis-static-voltage-regul… ("Read more"); https://tsipower.in/all-group-companies-of-bapasitaram-now-use-tsi-vrp/ ("Read more"); https://tsipower.in/ashok-leyland-is-rapidly-switching-to-tsis-static-voltage… ("Read more"); https://tsipower.in/powering-okamoto-indias-grinding-machine-on-a-special-occ… ("Read more"); https://tsipower.in/starrag-india-at-imtex-2025-powered-by-tsi/ ("Read more"); https://tsipower.in/macpower-cnc-at-imtex-2025-powered-by-tsi/ ("Read more"); https://tsipower.in/supplying-pure-power-for-defense-and-mission-critical-app… ("Read more"); https://tsipower.in/powered-a-seamless-demo-for-laser-technologies-at-blech-i… ("Read more"); https://tsipower.in/proudly-serving-the-ordnance-factory/ ("Read more"); https://tsipower.in/how-jay-polypack-makes-perfect-bottles/ ("Read more") (+13 more)
Warning::
1 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://www.linkedin.com/company/tsi-elecpower-p-ltd-
Info::
148 link(s) with descriptive text
183 links
11 empty
23 generic text
1 new tab
0 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://tsipower.in | (empty) | empty | Add link text or aria-label |
| https://tsipower.in | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/toyota-kirloskar-mot… | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/toyota-kirloskar-mot… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Toyota Kirloskar Motor Entrusts Tsis Static Voltage Regulation Technology For Sag Mitigation | |||
| https://tsipower.in/all-group-companies-… | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/all-group-companies-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: All Group Companies Of Bapasitaram Now Use Tsi Vrp | |||
| https://tsipower.in/ashok-leyland-is-rap… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Ashok Leyland Is Rapidly Switching To Tsis Static Voltage Regulation Technology | |||
| https://tsipower.in/powering-okamoto-ind… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Powering Okamoto Indias Grinding Machine On A Special Occasion | |||
| https://tsipower.in/starrag-india-at-imt… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Starrag India At Imtex 2025 Powered By Tsi | |||
| https://tsipower.in/macpower-cnc-at-imte… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Macpower Cnc At Imtex 2025 Powered By Tsi | |||
| https://tsipower.in/supplying-pure-power… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Supplying Pure Power For Defense And Mission Critical Applications | |||
| https://tsipower.in/powered-a-seamless-d… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Powered A Seamless Demo For Laser Technologies At Blech India Exhibition | |||
| https://tsipower.in/proudly-serving-the-… | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/proudly-serving-the-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Proudly Serving The Ordnance Factory | |||
| https://tsipower.in/how-jay-polypack-mak… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: How Jay Polypack Makes Perfect Bottles | |||
| https://tsipower.in/toyota-kirloskar-mot… | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/toyota-kirloskar-mot… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Toyota Kirloskar Motor Entrusts Tsis Static Voltage Regulation Technology For Sag Mitigation | |||
| https://tsipower.in/all-group-companies-… | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/all-group-companies-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: All Group Companies Of Bapasitaram Now Use Tsi Vrp | |||
| https://tsipower.in/ashok-leyland-is-rap… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Ashok Leyland Is Rapidly Switching To Tsis Static Voltage Regulation Technology | |||
| https://tsipower.in/powering-okamoto-ind… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Powering Okamoto Indias Grinding Machine On A Special Occasion | |||
| https://tsipower.in/starrag-india-at-imt… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Starrag India At Imtex 2025 Powered By Tsi | |||
| https://tsipower.in/macpower-cnc-at-imte… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Macpower Cnc At Imtex 2025 Powered By Tsi | |||
| https://tsipower.in/supplying-pure-power… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Supplying Pure Power For Defense And Mission Critical Applications | |||
| https://tsipower.in/powered-a-seamless-d… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Powered A Seamless Demo For Laser Technologies At Blech India Exhibition | |||
| https://tsipower.in/proudly-serving-the-… | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/proudly-serving-the-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Proudly Serving The Ordnance Factory | |||
| https://tsipower.in/how-jay-polypack-mak… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: How Jay Polypack Makes Perfect Bottles | |||
| https://tsipower.in/toyota-kirloskar-mot… | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/toyota-kirloskar-mot… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Toyota Kirloskar Motor Entrusts Tsis Static Voltage Regulation Technology For Sag Mitigation | |||
| https://tsipower.in/all-group-companies-… | (empty) | empty | Add link text or aria-label |
| https://tsipower.in/all-group-companies-… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: All Group Companies Of Bapasitaram Now Use Tsi Vrp | |||
| https://tsipower.in/ashok-leyland-is-rap… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Ashok Leyland Is Rapidly Switching To Tsis Static Voltage Regulation Technology | |||
| https://profiles.dunsregistered.com/Duns… | (empty) | empty | Add link text or aria-label |
| https://www.linkedin.com/company/tsi-ele… | new tab | Add '(opens in new tab)' to text | |
148 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
https://tsipower.in; https://tsipower.in; https://tsipower.in/toyota-kirloskar-motor-entrusts-tsis-static-voltage-regul…; https://tsipower.in/all-group-companies-of-bapasitaram-now-use-tsi-vrp/; https://tsipower.in/proudly-serving-the-ordnance-factory/; https://tsipower.in/toyota-kirloskar-motor-entrusts-tsis-static-voltage-regul…; https://tsipower.in/all-group-companies-of-bapasitaram-now-use-tsi-vrp/; https://tsipower.in/proudly-serving-the-ordnance-factory/; https://tsipower.in/toyota-kirloskar-motor-entrusts-tsis-static-voltage-regul…; https://tsipower.in/all-group-companies-of-bapasitaram-now-use-tsi-vrp/ (+1 more)
Why this matters
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Generic link text like 'click here' doesn't describe the destination.
https://tsipower.in/toyota-kirloskar-motor-entrusts-tsis-static-voltage-regul… ("Read more"); https://tsipower.in/all-group-companies-of-bapasitaram-now-use-tsi-vrp/ ("Read more"); https://tsipower.in/ashok-leyland-is-rapidly-switching-to-tsis-static-voltage… ("Read more"); https://tsipower.in/powering-okamoto-indias-grinding-machine-on-a-special-occ… ("Read more"); https://tsipower.in/starrag-india-at-imtex-2025-powered-by-tsi/ ("Read more"); https://tsipower.in/macpower-cnc-at-imtex-2025-powered-by-tsi/ ("Read more"); https://tsipower.in/supplying-pure-power-for-defense-and-mission-critical-app… ("Read more"); https://tsipower.in/powered-a-seamless-demo-for-laser-technologies-at-blech-i… ("Read more"); https://tsipower.in/proudly-serving-the-ordnance-factory/ ("Read more"); https://tsipower.in/how-jay-polypack-makes-perfect-bottles/ ("Read more") (+13 more)
Why this matters
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
https://www.linkedin.com/company/tsi-elecpower-p-ltd-
Why this matters
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
DTabindex Anti-PatternsAction0 positive, 90 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 90 -1-on-focusable
0 positive, 90 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
F404 Error PageActionSoft 404 detectedFIX
404 Error Page
ActionSoft 404 detected
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-8c3uma
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
FWeb ManifestActionInvalid JSONFIX
Web Manifest
ActionInvalid JSON
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://Www.tsipower.in/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://Www.tsipower.in/manifest.json
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
BHeading Hierarchy34 headingsREVIEW
Heading Hierarchy
34 headings
34 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
- H2 Industries
- H2 Products
- H2 Knowledge Hub
- H2 Industries
- H2 Products
- H2 Knowledge Hub
- H2 What is your industry?
- H2 Our Origin
- H2 Our Success
- H2 Toyota Kirloskar Motor Entrusts TSi’s Static Voltage Regulation Technology for Sag Mitigation
- H2 All Group Companies of Bapasitaram now use TSi-VRP
- H2 It Started with One Machine – Now We Power Many. Our journey with Ashok Leyland (Ennore).
- H2 Powering Okamoto India’s grinding machine on a special occasion.
- H2 Starrag India at IMTEX 2025 (powered by TSi)
- H2 Macpower CNC at IMTEX 2025 (powered by TSi)
- H2 Supplying pure power for defense and mission-critical applications
- H2 Powered a seamless demo for Laser Technologies at BLECH India Exhibition.
- H2 Proudly serving ‘The Ordnance Factory’.
- H2 How Jay Polypack Makes Perfect Bottles!
- H2 Toyota Kirloskar Motor Entrusts TSi’s Static Voltage Regulation Technology for Sag Mitigation
- H2 All Group Companies of Bapasitaram now use TSi-VRP
- H2 It Started with One Machine – Now We Power Many. Our journey with Ashok Leyland (Ennore).
- H2 Powering Okamoto India’s grinding machine on a special occasion.
- H2 Starrag India at IMTEX 2025 (powered by TSi)
- H2 Macpower CNC at IMTEX 2025 (powered by TSi)
- H2 Supplying pure power for defense and mission-critical applications
- H2 Powered a seamless demo for Laser Technologies at BLECH India Exhibition.
- H2 Proudly serving ‘The Ordnance Factory’.
- H2 How Jay Polypack Makes Perfect Bottles!
- H2 Toyota Kirloskar Motor Entrusts TSi’s Static Voltage Regulation Technology for Sag Mitigation
- H2 All Group Companies of Bapasitaram now use TSi-VRP
- H2 It Started with One Machine – Now We Power Many. Our journey with Ashok Leyland (Ennore).
- H2 FAQ
- H2 Follow us
Every page should have one H1 that describes the page content.
Why this matters
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
BFavicon & Branding4 icon(s) detectedREVIEW
Favicon & Branding
4 icon(s) detected
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
BLighthouse Accessibility AuditsScore 85/100 — 5 failing, 21 passedREVIEW
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 21 passed
85
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.e-con-inner > div.elementor-element > div.elementor-widget-container > div.elementor-swiper-button div.e-con-inner > div.elementor-element > div.elementor-widget-container > div.elementor-swiper-button |
div.e-con-inner > div.elementor-element > div.elementor-widget-container > div.elementor-swiper-button div.e-con-inner > div.elementor-element > div.elementor-widget-container > div.elementor-swiper-button |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Read More div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text |
Why do I need a voltage regulator? Is power conditioning a necessary evil for m… div.uc_container > div.uc_ac_box > div.uc-heading > div.ue_title |
TSi Power (P) Ltd.
154-155, Siddhi Industrial Infra Park, Waghodia, Vadodara, G… div.elementor-element > div.elementor-element > div.elementor-widget-container > p |
TSi Power (P) Ltd. div.elementor-element > div.elementor-widget-container > p > strong |
+91-7567722666 div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > span.elementor-icon-list-text |
+91-8000455999 div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > span.elementor-icon-list-text |
info@tsipower.in ul.elementor-icon-list-items > li.elementor-icon-list-item > a > span.elementor-icon-list-text |
Contact Us div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text |
© 2026 All Right Reserved div.elementor-element > div.elementor-element > div.elementor-widget-container > p |
Terms & Conditions div.e-con-inner > div.elementor-element > div.elementor-widget-container > p |
These are opportunities to improve the legibility of your content.
Names and labels
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > div.elementor-element > div.elementor-widget-container > a |
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Skip to content body.home > a.skip-link |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+Heading Text QualityAll 34 heading(s) have substantive, well-formed textPASS
Heading Text Quality
All 34 heading(s) have substantive, well-formed text
All 34 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+Alt Text QualityAll 38 images OKPASS
Alt Text Quality
All 38 images OK
All 38 images OK
Info::
23 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
38 images 15 good alt text 23 decorative
All images have appropriate alt text.
A+Form AccessibilityNo form controlsPASS
Form Accessibility
No form controls
No form controls
Info::
No form controls on this page
No form controls found.
A+Form Input TypesNo form controls on this pagePASS
Form Input Types
No form controls on this page
No form controls on this page
Info::
No form controls on this page
A+Form Input QualityNo form controls on this pagePASS
Form Input Quality
No form controls on this page
No form controls on this page
Info::
No form controls on this page
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+Document LanguageLang attribute set to "en-US"PASS
Document Language
Lang attribute set to "en-US"
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+Iframe AccessibilityNo iframes on this pagePASS
Iframe Accessibility
No iframes on this page
No iframes on this page
Info::
No iframes on this page
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+Mobile-Readable Font SizesAll 73 visible text node(s) render at >= 12 CSS pixelsPASS
Mobile-Readable Font Sizes
All 73 visible text node(s) render at >= 12 CSS pixels
All 73 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+PWA DepthNo PWA depth issues detectedPASS
PWA Depth
No PWA depth issues detected
No PWA depth issues detected
Info::
No PWA depth issues detected
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
Mobile UX Depth
1 mobile-depth signal(s) detected
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
20 pass
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Industries | 19.01:1 | 3.0:1 | #000000 | #FAF2EF | Pass |
| h2 Products | 19.06:1 | 3.0:1 | #000000 | #FBF2F0 | Pass |
| h2 Knowledge Hub | 19.06:1 | 3.0:1 | #000000 | #FBF2F0 | Pass |
| h2 Industries | 19.06:1 | 3.0:1 | #000000 | #FBF2F0 | Pass |
| h2 Products | 19.06:1 | 3.0:1 | #000000 | #FBF2F0 | Pass |
| h2 Knowledge Hub | 19.06:1 | 3.0:1 | #000000 | #FBF2F0 | Pass |
| h2 Follow us | 19.06:1 | 3.0:1 | #000000 | #FBF2F0 | Pass |
| title Home - TSi Power | 19.01:1 | 4.5:1 | #000000 | #FAF2EF | Pass |
| a Skip to content | 19.01:1 | 4.5:1 | #000000 | #FAF2EF | Pass |
| span Industries | 19.01:1 | 4.5:1 | #000000 | #FAF2EF | Pass |
| span Auto & Auto Ancillar… | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span CNC & Robotics | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span Building Management | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span Engineering & Proces… | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span Oil & Gas | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span Plastic Processing | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span Printing & Packaging | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span Radar, Security & Te… | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span Textile | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
| span Woodworking | 19.06:1 | 4.5:1 | #000000 | #FBF2F0 | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.