A service that works for as many people as possible.

Our approach

Application preparation can be particularly difficult for people who face visual, motor, cognitive or communication barriers. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA and use them when designing and testing the service.

Automated checks are useful, but they cannot prove that a service is accessible to everyone. Sift Assist has not yet had a complete independent accessibility audit, so we do not claim full WCAG conformance.

What is in place

Keyboard navigation. Main journeys can be reached and operated with a keyboard, with a visible focus indicator and a skip link on public and signed-in pages.

Labels and page structure. Forms use visible labels, pages have a single main heading, and controls use names that describe their action.

Reduced motion. Non-essential movement is suppressed when your device is set to reduce motion.

Responsive layouts. Public pages and the main application journeys are tested at desktop, mobile and 320-pixel screen widths without requiring sideways scrolling.

Plain language. Instructions explain one step at a time and avoid Civil Service or technical language where a simpler phrase is clearer.

Colour and zoom. Text and controls are designed for clear contrast and layouts can reflow as the available width reduces.

What still needs testing

Before claiming WCAG 2.2 Level AA conformance, the complete service needs a formal audit and broader testing with screen readers, magnification and people who use assistive technology. Any confirmed barriers and their repair dates will be recorded here.

If something is blocking you

Contact us at civilservicehelper@outlook.com and tell us which page you were using, what you were trying to do and what went wrong. Do not include a password, full application answer or other sensitive information. We will investigate the barrier and, where possible, offer another way to complete the task.

Saving longer answers

Guided answer and refinement boxes show whether unfinished text has been saved. Wait for that message before closing the page. Other forms still need their save or continue button. If saving is unavailable, keep the tab open because unsaved text can be lost when it closes or reloads.