Basic web accessibility: what an automated tool can check

What the scanner observes

AuditLume can inspect the declared language, alternative text, form labels, viewport, H1 count and a simple heading signal in initial HTML. These checks expose useful omissions, but they cannot establish that a page works for every person or assistive technology.

The implemented checks cover lang, missing alt attributes, the relation between visible controls and label elements, H1 count and viewport presence. They do not test keyboard use, contrast or assistive technology.

AuditLume reads the final public response and initial HTML only; the finding remains a prompt for verification rather than a conclusion about the whole organisation.

A responsible manual review

Automated output is an invitation to investigate, not a verdict. Check representative pages, complete the real user task and include people with different devices or needs. Treat unusual results as context to understand rather than a score to optimise blindly.

• Confirm that the declared language matches the visible copy.
• Give informative images a useful text alternative.
• Associate every input with a clear, persistent label.
• Navigate the complete task with a keyboard and visible focus.

How to prioritise

Review the evidence on the exact public page, record the current state, make one controlled change and check again. Keep screenshots or response details when they help colleagues understand the decision.

1. Confirm that the declared language matches the visible copy.
2. Give informative images a useful text alternative.
3. Associate every input with a clear, persistent label.
4. Navigate the complete task with a keyboard and visible focus.

Limits to remember

A positive signal does not certify accessibility, privacy, security, legal compliance or search performance. A missing signal does not by itself prove harm. AuditLume reads public responses and initial HTML; specialist, legal and manual reviews remain separate activities.