---
esco_uri: http://data.europa.eu/esco/skill/1774bd31-8893-44cf-9498-7e3d95508419
esco_label: "screen reader"
relation: optional
onet_soc: 15-1252.00
source: model-knowledge
confidence: high
qa_count: 0
generator: gemma3:27b (prompt-designed and spot-checked by Claude)
generated: 2026-07-10
---

# screen reader — Software Engineer

As a Software Engineer, 'screen reader competence' isn’t about *using* a screen reader as a primary tool – it's about building software that *works with* them. This means understanding how screen readers interpret your code: HTML structure (semantic elements are key!), ARIA attributes, dynamic content updates, and even image alt text. Daily tasks involve verifying accessibility during development; not just visually, but by testing with a screen reader to ensure logical reading order, proper announcement of controls, and meaningful information delivery. Think beyond 'does it look right' to 'does it *sound* right?'

Typical tools include NVDA (free & open source), VoiceOver (macOS/iOS), and JAWS (commercial). You’ll use browser developer tools with accessibility audits, but the real test is actually navigating your application with a screen reader. Common pitfalls are overly complex JavaScript interactions that aren't announced correctly, missing or poor alt text on images, improper heading structures, and relying solely on visual cues for important information.  Don't assume automated accessibility checkers catch everything – manual testing is crucial.

Good looks like writing code with accessibility baked in from the start (accessibility-first approach), proactively addressing ARIA needs, and being able to debug screen reader behavior when things go wrong. It also means collaborating effectively with QA testers who *are* expert screen reader users; their feedback is invaluable.  Being able to quickly diagnose why a screen reader isn't reading something as expected – is it a missing attribute? A structural issue? – is a sign of true competence.

Ultimately, screen reader competence for a Software Engineer translates into building inclusive software that provides equal access to all users, regardless of ability. It’s not just about compliance (though that matters!), but about ethical development and expanding your potential user base.

## Weitere Anreicherung

Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).
