Review a Trail Form for Missing Markup Names
Admin ·
A registration form can display an obvious icon and nearby words while leaving a screen reader without a usable control name. Start with the saved source to catch wiring errors, then check what the browser exposes after the application runs.
HTML Accessibility Quick Audit
Find the six issues in the registration sample
Choose Overview. Load the example in Complete document mode and audit it. The result has six findings and two native headings. Line 2 lacks the page language. The map image on line 6 lacks alt. The jump from h1 to h3 is on line 7.
Line 8 accounts for two findings. The label uses mail but the field ID is email, so the label cannot name that field. Line 9 has an icon-only button. Its SVG is marked aria-hidden and the button needs its own name.
W3C WAI Easy Checks for Web AccessibilityWHATWG HTML label element and control association
Correct the source and run the same audit again
Set lang="en" on html. Give the map suitable alternative text, such as Trail map, if it communicates information, and describe important route details in surrounding text. Use h2 if Participant details is a direct subsection of the main heading. Change the label to for="email" and give the icon button an action name, such as aria-label="Continue registration" if that is what it does.
Run the audit again. These edits clear the sample findings in the supported checks. To review only the form portion, choose Fragment. Page language and title checks apply to the complete document.
W3C WAI Easy Checks for Web AccessibilityW3C Accessible Name and Description Computation
Confirm the control names in the running page
Download the audit JSON for reviewers who need source positions and finding codes. Reopen the report and check that the line and column refer to the version you supplied.
Inspect the form in the browser’s accessibility tree. Confirm the field and button names, test how keyboard focus moves, and check whether client scripts change labels. Saved markup cannot establish those results or whether the names are helpful in context.
W3C WAI Easy Checks for Web AccessibilityW3C Accessible Name and Description Computation
Find the label that misses its select field
Choose Form labels, then Load example and Check form labels. The inventory has five controls, including the hidden Campaign input. Email address points to the email field. The textarea references the hidden Access requirements text on line 10, which can still provide its name.
Supply preference uses for="supply" on line 7, while the select is gear on line 8. Change the label to for="gear". In the running page, click the label or inspect the select’s accessible name. The label on line 12 already points to a control, but contains no text. Give it meaningful text and make the ID unique.
WHATWG HTML label element and control associationW3C Accessible Name and Description Computation
Compare the keyboard findings with actual Tab order
Choose Keyboard navigation and load its example. It flags tabindex="2" on the second button, the click handler on a div and the inline outline suppression on Clear form. Start Tab from the document in a trusted copy. The priority button can receive focus ahead of First control.
Remove the positive tabindex and test again. Replace the action-like div with a native button, then verify Enter and Space in the application. Test Clear form with a keyboard and inspect its focus indicator. A visible border or other indicator can be supplied by CSS elsewhere.
WHATWG HTML sequential focus navigationW3C WAI Easy Checks for Web Accessibility
Distinguish a page banner from an article header
Choose Landmarks and load its example. The inventory has seven entries. The page header is a banner and the header inside the article is ordinary content. Checklist is a named region because aria-labelledby points to its heading.
Two navigation landmarks occur, one named Primary and one unnamed. Give the second a name that describes its distinct purpose, then inspect both in the running browser. The downloaded report uses one-based lines and columns and zero-based UTF-16 offsets. Its ending offset is exclusive.
W3C WAI ARIA landmark regionsW3C Accessible Name and Description Computation
Common questions
Can aria-labelledby refer to a hidden element?
A direct reference can contribute a name from hidden text. The audit looks for this source evidence. Verify the computed name when styles, nested references or scripting are involved.
Can a heading level jump be intentional?
A jump is a review prompt. Examine the resulting hierarchy and revise the level if the headings misrepresent the document’s structure.
Does aria-hidden remove an element from Tab order?
aria-hidden can remove content from the accessibility tree. A native control or explicit tabindex may still make it reachable by keyboard. Check the warning and test focus in the running page.
Does an article header create a banner landmark?
An ordinary header inside an article does not create the native page banner. Inspect the source inventory and the browser’s exposed role if the element has explicit ARIA.