What a finding looks like when it’s written to be fixed.
This is a constructed example using an invented product, not client work. Real client reports are confidential. The structure, severity language, and level of detail shown here reflect what clients can expect from my work.
Impact levels
- CRITICAL
- HIGH
- MODERATE
- LOW
Interactive elements are implemented by nesting <button> elements inside <a> elements
There are 14 instances where a single interactive control creates two focus stops and duplicate announcements. For example, NVDA announces “‘Request an audit’ link button” twice in quick succession, also requiring the user to press Tab twice to move past the control.
Each interactive control should receive a single logical focus stop and be announced with a role that accurately reflects its function (e.g., a link navigates to another location, while a button performs an action). A single control should not produce duplicate focus stops, repeated announcements, or conflicting information about its role or behavior.
Keyboard and screen reader users may encounter duplicate focus stops and repetitive announcements throughout the page, making navigation slower, more confusing, and more aurally fatiguing.
Making the site easier to navigate helps visitors reach key services and the information they are looking for with less friction, supporting stronger engagement and potentially reducing the site’s bounce rate.
- Avoid nesting interactive controls within one another.
- Determine whether each control navigates or performs an action, then use the appropriate native HTML element:
<a href>for navigation and<button>for actions. - Where the same markup pattern is reused across multiple controls, correct the underlying component or pattern rather than remediating each instance individually.
What “retest included” means
One remediation verification pass of reported findings is included within 90 days of report delivery. Additional verification rounds, testing of newly introduced functionality, and re-audits are scoped separately.
Every finding gets this level of attention.
Finding a barrier is only useful if a team knows what it means for the people affected and what to do about it. Each finding connects user impact to the underlying issue, then provides clear remediation guidance for addressing it.