Prove the work Pro
Response targets and burden records
Set how quickly you aim to answer accessibility feedback, get told when a request is overdue, and keep structured disproportionate burden records.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Overview
Response targets are set under Lumtera → Settings → Response targets. Your response targets has one field per request type: Barrier, Accessible version and Other, in calendar days, counted to the end of the day in your site's time zone. They start at 5, 10 and 10 days, and 0 means no target. This is your own goal, not a legal deadline.
In the feedback inbox, under Lumtera → Feedback & statement, each request shows when it should be answered by. A request still New or In progress after its target is marked Overdue and appears in the Overdue view. Lumtera checks every hour and announces each overdue request once, by email and Slack through your Alerts settings, and to the activity log and webhooks. A weekly summary of overdue requests goes out with the Monday summary.
Burden records are under Lumtera → Feedback & statement → Burden records. Record your assessment asks for a Name, the Scope (web addresses, and posts, pages and documents, by ID; any ID that is not on the site is named in a warning after saving), the Requirements affected, the Annex VI assessment (cost compared with your organization, benefit to people with disabilities, and how often and how long the content is used), the Accessible alternative provided, who assessed it and when, and the Next review, five years later by default. A Public summary can be added to your accessibility statement.
Why does it matter?
A visitor who reports a barrier is waiting for an answer. Without a target and a reminder, requests sit in an inbox. And when a requirement cannot reasonably be met, the European Accessibility Act expects a written assessment, not a note in someone's head.
What do you get?
- A response target in calendar days for each type of request: Barrier, Accessible version and Other.
- Overdue requests get a badge, their own view in the inbox, and one alert by email and Slack.
- Assign a request to a person, or create a fix task on the page it is about.
- Disproportionate burden records that follow the Annex VI structure, with a review date.
- A public summary of each record can be added to your accessibility statement.
How does it work?
-
Set your targets
Under Lumtera → Settings → Response targets, enter the days you aim for per request type.
-
Work the inbox
Assign requests and turn barriers into fix tasks. Overdue ones are flagged for you.
-
Record burden assessments
Under Lumtera → Feedback & statement → Burden records, write down your assessment and its alternative.
Who is it for?
-
Small teams with a shared inbox
Assign each request to one person, who gets an email with a link to it, so nothing waits because everyone thought someone else had it.
-
Barriers that need a fix
Create fix task puts the request on the page it is about, in Fixes, without copying what the visitor wrote.
-
Businesses selling into the EU
Keep a written assessment for content you cannot make accessible yet, such as an old video archive, with the alternative you offer.
Good to know
How it behaves, what it needs, and where its limits are.
- Plans and access
- Included in every Pro plan with an active license. Setting response targets needs an administrator. Assigning requests and creating fix tasks need the Handle accessibility feedback permission. Burden records need a role that can publish pages, editors and administrators by default.
- Emails
- "Accessibility feedback assigned to you" goes to the assignee. "N accessibility requests are past your response target" goes to your Alerts recipients, and the weekly overdue summary goes with the weekly summary email.
- Fix tasks from feedback
- No check reports these, so a re-scan never closes them. A person closes the task when the barrier is fixed.
- Not legal advice
- Lumtera stores the burden assessment you make. It does not decide whether a burden is disproportionate. The screen links to Directive (EU) 2019/882, Annex VI.
- Evidence
- Received, assigned and overdue feedback, and recorded or reviewed burden assessments, are added to the evidence log. Feedback appears by reference only, never with the visitor's name, email or message.
Questions
Something else on your mind? Contact support
Is the response target a legal deadline?
No. It is your own goal. Check with your adviser which deadlines apply to you.
Does Lumtera decide whether a burden is disproportionate?
No. It stores the assessment you make. It is not legal advice.
Does changing a target affect open requests?
Yes. Changes apply to every open request.
Can a burden record be deleted?
Yes, but keep assessments you have relied on. The evidence log keeps the entries made when the record was saved.
More in “Prove the work”
-
Pro
Accessibility Conformance Report (VPAT 2.5)
A WCAG 2.2 A and AA conformance report in the VPAT 2.5 layout, filled in from your checks, manual tests and test sessions, ready to review and export.
-
Pro
Tamper-evident evidence log and evidence pack
A dated record of scans, manual tests, statement changes, fixes and feedback, hash-chained so changes can be detected, with a pack you can print or export.
-
Pro
Test sessions
Test each key page template by hand, record the assistive technology and browser used, add screenshots, and sign the results off.
Response targets and burden records
Get it with Lumtera Pro
In every Pro plan. Personal is $149 a year. Pro installs alongside the free plugin, and your settings and results stay.
14-day refund (opens in a new tab)Keeps working if you don't renew