NFRs From Day One
Turning Accessibility from Rework into Process
Accessibility, performance, data protection — non-functional requirements often fall by the wayside in everyday project work, until they suddenly become urgent. The result: expensive rework, frustrated teams, disappointed clients.
A technical project lead and a head of QA discuss how they gradually moved accessibility from reactive rework into a structured process. Using typical TYPO3 pitfalls — missing alt tags, unclear form error messages — they present a five-pillar framework: define scope deliberately, anchor early, enable teams, embed processes, monitor continuously.
The approach is directly transferable to any NFR — performance, security, or data protection. With real tools from daily project work: Jira ticket templates, Confluence checklists, and tooling recommendations. By the end, every attendee leaves with three concrete next steps — to apply them today, this week, or at the next project kickoff.