A job application may look simple on a recruiter’s laptop and become almost impossible on a candidate’s phone. Tiny controls, repeated questions, large uploads and a form that forgets its progress can quietly remove capable people from the shortlist.
Mobile-friendly hiring is not achieved by shrinking a desktop page. It means designing the journey around a small screen, limited time, inconsistent connectivity and the possibility that the phone is the candidate’s only practical way to apply.
Test the real journey
Ask someone who did not build the form to complete an application on an ordinary phone using mobile data. Start from the job advert, not the application page. The test includes opening the listing, understanding the role, creating an account, entering information, uploading documents and receiving confirmation.
Observe without helping. Record every point where the tester zooms, searches for a button, re-enters information or wonders whether anything happened. Repeat the test on more than one screen size and with a slower connection.
Do not treat successful submission as the only measure. Count the minutes, taps, fields, page loads and failed attempts. A technically functional application can still demand unreasonable effort.
Make the first step smaller
A candidate should be able to understand the opportunity before creating an account. Place the location, working arrangement, salary information where available, core requirements and closing date in the advert itself.
Ask only for information needed to decide the next step. If a CV already contains employment history, do not force candidates to type the same history into several boxes during the first application. Additional information can be requested later when it becomes relevant.
Clearly distinguish required and optional fields. Explain why sensitive information is requested and whether it will influence selection. Shorter forms are easier to complete, easier to maintain and less likely to collect personal information without a defined purpose.
Design for thumbs and small screens
Use a single-column layout with readable text and generous spacing. Buttons and selection controls need to be large enough to tap without hitting the option next to them. Keep labels visible after a candidate starts typing; placeholder text should not be the only explanation of a field.
Choose the right input for the answer. Dates, telephone numbers, email addresses and short numerical fields should activate a suitable mobile keyboard. Avoid large dropdown lists when search or a short set of choices would be faster.
Error messages must identify the exact field and explain how to fix it. Do not erase correctly completed fields because one answer is invalid. Move focus to the problem and preserve everything else.
Treat uploads as a high-risk moment
Document uploads often cause the greatest frustration. State accepted file types and size limits before the candidate selects a file. Support common formats and let applicants upload a clear photograph or scan where that is appropriate.
Do not require a cover letter in a special format if a plain-text answer would meet the same need. Avoid asking candidates to combine several documents into one file unless there is a compelling operational reason.
If an upload fails, preserve the rest of the application and offer a retry. Where possible, allow candidates to save progress and return through a secure link. A connection failure should not mean starting again.
Make accessibility part of the build
A mobile application must work for candidates who use screen readers, keyboard navigation, magnification or other assistive technology. Every field needs a meaningful label, focus order should follow the page, colour should not be the only way to communicate status and controls must expose their purpose correctly.
Provide an accessible route for requesting help or an adjustment. That route should not require the candidate to disclose more personal information than necessary.
Automated accessibility checks can catch common errors, but they cannot replace practical testing. Include people with different access needs in user testing and fix obstacles before a live vacancy depends on the form.
Measure where people leave
Track progress through meaningful stages: advert viewed, application started, first page completed, documents uploaded and application submitted. Compare completion by device type without using the data to identify or disadvantage individual candidates.
Investigate sudden exits rather than assuming candidates lost interest. A high drop-off after account creation may point to password rules or email verification. Exits at document upload may indicate file limits. A long completion time may reveal repeated or unclear questions.
Review the journey after every substantial change. A small improvement that increases completed, usable applications is more valuable than adding another feature candidates did not need.
Sources and limits
The design recommendations align with the W3C’s official Web Content Accessibility Guidelines 2.2 and mobile accessibility guidance. Decisions about collecting and retaining applicant information should also be considered against South Africa’s Protection of Personal Information Act.
Accessibility conformance cannot be established from this article or from automated testing alone. Employers should obtain specialist testing where needed and review privacy, security and record-retention decisions with appropriately qualified advisers.