Engineering guides / Angular applications and AWS infrastructure
By Arte Soft engineering · 24 October 2026
Commissioning a practical web accessibility review
An accessibility review should help people complete the tasks your website exists to support. Automated scans can identify some issues, but they cannot establish whether a checkout, booking flow or dashboard makes sense with a keyboard or assistive technology. Begin with the journeys and user environments that matter, then agree the standard and the boundaries of the assessment.
Define coverage before asking for a score
List representative page types, reusable controls and state changes. A landing page, a form with validation and an authenticated table have different failure modes. Include mobile layouts, dialogs, consent controls and error messages instead of sampling only pristine screens. Agree the WCAG version and conformance target relevant to your requirements. This is an engineering scope, not a legal opinion or a certification. If procurement requires formal compliance assurance, identify the responsible specialist and evidence format separately. A percentage from an automated tool should never be presented as a complete statement that a product is accessible.
Examine interaction as well as appearance
Trace keyboard focus from entry through completion. Check whether a dialog receives focus, prevents confusing background interaction and returns focus after closing. Inspect labels, instructions and error recovery without relying only on color. Test magnification, narrow widths and reduced motion. For dynamic content, determine what a screen reader announces and whether that announcement helps rather than overwhelms. Record the exact steps, affected component and user consequence for each finding. These details allow developers to reproduce problems and distinguish a systemic design issue from a single missing attribute on an otherwise sound control.
Turn findings into verified fixes
Deliver a prioritized issue register with screenshots or recordings where appropriate, affected criteria and suggested remediation. Group repeated issues by component so the team can repair the shared cause. Acceptance should revisit the original task with the proposed change, including keyboard-only use and the agreed assistive technology combination. An automated scan can support that check but cannot replace it. Keep unresolved questions visible when a control depends on an embedded third-party service. A review is more valuable when it explains what remains outside coverage than when it suggests that a small sample proves every page and device combination.
Make shared components part of the remediation plan. Fixing an accessible name or focus behavior centrally can improve several journeys, while a page-specific patch may leave the same barrier in the next form or dialog a visitor encounters.
Fit the review into delivery
For a new product, review interaction patterns before they spread across dozens of screens. For an existing site, start with the task most closely tied to user access or revenue, then expand coverage. Arte Soft’s own product sites provide examples of interfaces we maintain; they are not a claim of independent accessibility certification. Bring your design system, primary journeys and known complaints. A scoped review can produce actionable engineering work, a retest plan and guidance for future components. The tradeoff is deliberate depth on important interactions rather than a superficial claim to have checked every URL.
Relevant Arte Soft work
Cloud Calendars — our own product is our own product or engineering project. It provides context for the work we discuss here; it is not a claim of identical results for every client deployment.
Sources and further reading
Need help with Web accessibility assessment?
Send the current app, system or brief, the behaviour you need and your constraints. We can agree a discovery, implementation or repair scope with concrete acceptance criteria.
Discuss this with Arte Soft