What Is Focus Indicator Tester?
Focus Indicator Tester is a free online tool by TechnSols that checks pasted HTML for visible focus indicators on every focusable element. Paste the markup, press Check Focus Indicators, and the tool lists each link, button, and form control with a pass or a fail, so a keyboard user is never left guessing where they are.
A focus indicator is the outline or highlight a browser draws around the element that has keyboard focus, and without it a keyboard user cannot tell which control is active. The MDN focus-visible guide explains how browsers decide when to show that outline, so the rule is clear even when the markup looks fine at first glance.
This tester is different from the live Focus Order Visualizer tool, which shows the order in which focus moves through a page. That tool checks the sequence; this one checks whether each control shows a visible indicator when focus lands on it, so the two answer different questions about the same keyboard journey.
People use it to check a form before launch, to prove a fix to a client, to audit a page after a redesign, or to learn which controls fail the visibility rule. It suits a developer, a tester, an accessibility auditor, or anyone who wants keyboard users to see where they are.
How To Use Focus Indicator Tester?
Here is how to test focus indicators online in three quick steps. Using Focus Indicator Tester is simple. There is no software to install and no account to make. Paste the HTML, press the button, and read the report. If the order of focus also needs checking, the Keyboard Navigation Tester tool shows that order step by step.
Step 1: Paste The HTML To Check
Paste the HTML of the page or the part of the page you want to check into the box. A form, a menu, or a whole page all work, because the tester reads the markup you give it. Keep the style block with the markup when the focus styles live in a style tag, because the check reads those rules too.
Step 2: Press Check Focus Indicators
Press Check Focus Indicators and the tool parses the markup in your browser. It finds every link with an href, every button, every input, select, and textarea, and every element with a tabindex, then looks for a focus rule that gives each one a visible outline or background change.
Step 3: Read The Report And Download It
Read the report: each element is named with a pass or a fail, and the summary counts how many controls are covered. Press Download Report to save the list as a text file for the fix list. If a full audit is needed next, the WCAG Accessibility Auditor tool runs the wider check.
The whole check takes less than a minute, because the page does the work the moment you press the button. A focus ring you can see is a keyboard journey you can follow, and that is the whole point of testing it here.
Why Focus Indicator Tester?
A visible indicator beats a guess because a keyboard user navigates by sight, and the indicator is the only sign of where focus sits. The tester names the controls that lack one instead of leaving you to tab through the page by hand. If the colour of the indicator also needs checking, the Color Contrast Checker tool measures that contrast.
The reason the rule matters is that WCAG asks for focus to be visible, and a missing indicator fails that rule even when the page is otherwise sound. The W3C page on the Focus Visible criterion states the same point plainly: when an element has keyboard focus, some part of it must be visible, so the user always knows where they are.
Every Focusable Element Is Listed
A page can hide a focus problem in one control among dozens, and a manual tab through the page can miss it. The tester lists every focusable element it finds, so the check covers the whole form or menu instead of the few controls you happened to try.
Pass And Fail Are Plain Words
A report full of scores is hard to act on, and a pass or fail beside each element is not. Each row says whether the element has a visible focus style, so the fix list writes itself: every fail is one control that needs a focus rule.
It Checks The Styles You Pasted
A focus style only counts if it is actually in the page, so the tester reads the style rules in the pasted markup instead of assuming a framework provides them. If a rule hides the outline with outline none and gives nothing back, the element fails. When the markup itself needs a closer look, the Screen Reader Preview tool inspects that single element.
What Can You Do With Focus Indicator Tester?
A focus indicator tester fits any job where keyboard access is part of the question. These are the jobs this tester handles best.
Audit A Form Before Launch
A form is where a missing indicator hurts most, because a user who cannot see the active field cannot fill the form in. Paste the form markup, read the report, and fix every fail before launch. If the images in the form also need checking, the Alt Text Checker tool checks their alt text.
Prove A Fix To A Client
A fix is only done when it can be shown, and the downloaded report is that proof: run the check before the fix, run it again after, and the two reports show the fails dropping to zero. The file is plain text, so it pastes straight into a ticket or an email.
Learn Which Controls Fail Most
Custom buttons and styled inputs fail more often than plain links, because their styles often remove the default outline without adding one back. Checking a few components shows the pattern, and the pattern tells you which component styles need a focus rule added to the stylesheet.
Quality And Settings
The tester parses pasted HTML in the browser, finds links, buttons, inputs, selects, textareas, and tabindex elements, and checks each one against the focus rules in the pasted styles. The report counts the focusable elements, names the passes and fails, and downloads as a text file. If the page behind the markup also needs a layout check, the HTML Element Inspector tool tests it at phone, tablet, and desktop widths.
- Every focusable element listed: links, buttons, and form controls.
- Each element marked pass or fail for a visible focus style.
- Focus rules read from the style blocks in the pasted markup.
- Summary counts: total controls, covered controls, and fails.
- Report downloads as a plain text file for the fix list.
There are no other settings to learn, because the check is the whole tool. Open it, paste the markup, and read the report.
How Focus Indicator Tester Works
The tester parses the pasted HTML with the browser parser, collects every element that can take focus, and reads the text of every style block for focus rules such as :focus and :focus-visible. An element passes when a rule gives it an outline, a border change, or a background change on focus, and fails when no rule does. If a single element needs a closer look, the ARIA Attribute Inspector tool inspects that element in the markup.
Two limits are worth knowing. The tester checks pasted HTML in the browser only: it cannot test a live site the visitor does not paste in, and it cannot fetch a page by URL, because nothing is ever uploaded. It also reads styles from the pasted markup only, so focus styles in an outside stylesheet the visitor does not paste are not seen, and the element reads as a fail even when the live page shows an outline. Keyboard users include people who cannot use a mouse, people with a broken trackpad, and power users who tab through forms for speed, so the audience for a visible indicator is wider than one group.
Privacy
Everything you check stays in your browser. The markup you paste is read on your own computer, and nothing you type is uploaded to a server, stored, or shared with anyone. The tool reads the input and shows the answer, and that is all it does.
Because no account is needed, there is no name, email, or history tied to what you check. Closing the tab ends the session, and the browser clears the input from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.
Tips
A few habits make Focus Indicator Tester work smoother, whether this is your first check or your fiftieth.
- Paste the style block with the markup, so focus rules are seen.
- Check the whole form, not one field, because fails hide in groups.
- Fix fails one control at a time and re-run the check after each fix.
- Keep the default outline unless the replacement is clearly visible.
- Download the report before the fix, so the before and after can be compared.
When the report shows zero fails, the keyboard journey is visible from the first control to the last. If the page also needs a width check, the Responsive Design Tester tool tests it at phone, tablet, and desktop sizes.
More Tools For The Same Job
These tools handle the same kinds of jobs: testing pages, controls, and text for access.
- Focus Order Visualizer: shows the order focus moves through a page.
- Keyboard Navigation Tester: tests a page with keyboard keys only.
- WCAG Accessibility Auditor: runs a wider accessibility audit on a page.
- Color Contrast Checker: measures the contrast of text against its background.
- Screen Reader Preview Tool: previews how a reader announces a page.
- Alt Text Coverage Checker: checks the alt text on every image in a page.
- Accessible Form Tester: tests a form for labels and keyboard access.
- ARIA Attribute Inspector: inspects the ARIA attributes on a page.
- Heading Hierarchy Checker: checks the heading order on a page.
- Accessibility Statement Generator: writes an accessibility statement for a site.
FAQ
Common questions about testing focus indicators, answered plainly.
Is Focus Indicator Tester by TechnSols Free?
Yes, Focus Indicator Tester by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can test as much markup as you like, and everything is checked in your browser, so nothing is uploaded or stored anywhere.
What Counts As A Visible Focus Indicator?
A visible focus indicator is any change a keyboard user can see when an element takes focus: an outline, a thicker border, or a clear background change. The default browser outline counts, and a custom style counts too, as long as the change is easy to spot against the page.
How Is This Different From The Focus Order Visualizer?
The live Focus Order Visualizer shows the sequence focus follows when you press Tab, while this tester checks whether each control shows a visible indicator when focus lands on it. Order and visibility are different questions, so the two tools check different parts of the same keyboard journey.
Does It Test A Live Website?
No, it checks only the HTML you paste in, because nothing is ever uploaded and no page is fetched. Paste the markup of the page or the part you want to check, with its style block, and the tester reads exactly what you gave it, in your browser only.
What If My Styles Live In An Outside File?
Paste the focus rules from that file into the markup, or paste the whole style block with the HTML. The tester reads only what you paste, so an outside stylesheet it cannot see reads as a fail even when the live page shows an outline.
Paste the markup, press Check Focus Indicators, and read the report. A focus ring you can see is a keyboard journey you can follow, and that is the whole point of testing it here.