A job applicant asks for an accommodation before an interview, or halfway through one. The request might come in an email to the recruiter, a phone call, or a single sentence at the start of a video call. The person who receives it may be busy, may not know what the request means, and may feel unsure about what they are allowed to say next.
That uncertainty is where mistakes happen. A recruiter asks a friendly question that crosses a line. A hiring manager quietly lowers an applicant's standing. A team scrambles to arrange something on the day and never settles what was actually agreed.
This post is for recruiters and hiring managers who must answer a request like this before or during an interview. It is practical on purpose. It explains what to do with the request, what to ask and what to leave alone, and how to make sure the arrangement is real when the applicant walks in.
Federal guidance on this situation is clearer than most people expect. This post turns it into three duties you can follow, whether you send the first reply or sit across the table during the interview.
One note on scope. The rules that apply to you may come from state law as well as federal guidance, and the details differ from place to place. Washington's statute, for example, carves out exceptions for certain businesses. It reads, in part, "(2) Subsection (1) of this section shall not apply to transactions with insurance entities, health service contractors, or health maintenance organizations ... ", an out-of-scope example of the kind of state-law wording that exists in other areas of the same statute. Read the full Washington statute and any rules where you hire. When you are unsure, involve your legal or HR team. Nothing here is legal advice.
The three duties are these. First, recognize the request and keep it from counting against the applicant. Second, keep your questions on the job rather than on the person's disability. Third, work out the arrangement, test it against the role, and set it up before the day.
Duty 1: Recognize the request and keep it from counting against the applicant
Recognition is harder than it sounds. Applicants rarely use formal language. They seldom cite a law or ask for a "reasonable accommodation" by name. Most simply describe what they need and assume you will understand.
| Common mistake | What it looks like | Better habit | Source |
|---|---|---|---|
| Treating the ask as a favor | Dropping it when the schedule gets busy | Acknowledge in writing | General practice |
| Secondhand briefing | Hiring manager forms a view before meeting the applicant | Route the request to a named owner | General practice |
| Hallway agreement | Promise made with no trace anywhere | Keep a simple record | EEOC |
The U.S. Equal Employment Opportunity Commission (EEOC) publishes guidance for job applicants on the Americans with Disabilities Act, and it shows how plain a request can be: "I have a disability and will need an accommodation for the job interview." That sentence names no form, no policy and no legal term. It is still a request, and you should treat it as one.
Recognition matters most for the people who handle scheduling. A note asking for a different interview format, a quieter room, more time, or materials in another format is not a scheduling quirk. Route it to the person who can act on it, and make sure that person knows it came from an applicant and needs a response.
A simple team rule helps. Any message that mentions a need connected to the interview goes to the same named owner as soon as it arrives. Shared inboxes can bury these messages among routine traffic, so when you triage, look for words such as "accommodation," "interpreter," "accessible," and "need."
Requests also arrive at the wrong moment. An applicant may say nothing in advance and then mention a need once the interview has started. A panel member may notice someone struggling with the format and ask whether they need something. Either way, keep the response calm and simple. Acknowledge the need, offer to adjust what you can, and move on. Do not stop the interview to investigate, and do not ask the applicant to justify the request before you respond.
Now consider how a request can go wrong. Imagine an applicant who writes to a recruiter two days before a panel interview to say they need a step-free room and would like the questions sent in advance. The recruiter, who has never handled this before, replies: "Is there something we should know about?"
Nothing in that reply is unkind. But it asks for information the applicant has no obligation to share, and it makes them feel scrutinized before they have even sat down. A better reply confirms the request and moves the process forward. Something like this does the job:
> Thank you for letting us know. We are arranging a step-free room for your interview, and we can send the questions in advance. I will follow up with the details shortly. Please reach out to me directly with anything else that would help you prepare.
Tone matters as much as speed. Applicants often remember the first reply more than anything that follows. A reply that is warm, short, and specific tells them the process is open to them. A reply that hedges or asks for proof tells them the opposite, even when the sender meant well.
The second half of this duty is about fairness. The same guidance is direct on the point: "An employer cannot refuse to consider you because you require a reasonable accommodation to compete for or perform a job." That applies at every stage, not only in the interview. An applicant who asks for an accommodation must be considered on the same basis as everyone else. Asking for help is not a reason to move someone to the bottom of the list, drop them quietly from the pipeline, or call the role "not a good fit" when the real reason is the request.
In practice, that means a few habits:
- Acknowledge in writing. A short reply that thanks the applicant and says you are working on it is enough. Keep the tone neutral, and avoid comments about the applicant's condition.
- Keep the request out of the scoring. Panel members need to know the format they will run, but the request should have no bearing on how answers are rated. If someone needs to know more, limit it to what they must do differently in the room.
- Don't reopen the decision. An applicant who looked strong before they asked for help still looks strong after. Watch for doubts that appear only after the request arrives, and ask whether the same doubt would exist without it.
- Keep a simple record. Note the date the request arrived, what was asked, who was told, and what was agreed. The record protects the applicant and your organization, and it lets a new team member pick up the work without asking the applicant to explain again.
Common mistakes deserve a mention. The most frequent is treating the ask as a favor that can be dropped when the schedule gets busy. Another is letting the hiring manager hear about it secondhand and form a view before meeting the applicant. A third is agreeing to something in a hallway conversation with no trace of it anywhere, so that everyone remembers a different promise.
The first duty comes down to one test. Would you treat this applicant the same way if they had not asked? If the honest answer is no, stop and fix the problem before going further.
Related guides
- Interview Scorecard Example for Consistent Hiring Teams
- Hiring Decision Debrief: Notes to a Recorded Decision
- Conviction timing rules for 3 jurisdictions
Duty 2: Keep your questions on the job, not the disability
This is the duty most interviewers get wrong, usually without meaning to. People are curious, and they want to help. An applicant says they need extra time, and the interviewer asks what it is for. An applicant mentions a condition, and the interviewer asks how long they have had it. Both questions feel kind in the moment.
The technical assistance manual on the employment provisions of the ADA draws a clear boundary. In its section on information that may be requested on application forms or in interviews, it says: "An interviewer may not ask questions about a disability, but may obtain more specific information about the ability to perform job tasks and about any needed accommodation, as set out below." The manual points back to earlier material on the subject, so read those parts before you schedule any interviews.
Read that sentence as a line with two sides. On one side is the disability itself. Interviewers may not ask about it. That includes the name of a condition, its cause, its history, how it was treated, and how it affects a person's life. These are health questions, and they have no place in a job interview. If an applicant volunteers that kind of information, you do not need to follow up. Thank them and return to the work.
On the other side of the line is the job. Your questions belong there, on the tasks the role requires and the accommodation the applicant needs. The same section offers a fair tool, and it is worth using with every applicant: "also may give the applicant a copy of a detailed position description and ask whether s/he can perform the functions described in the position, with or without a reasonable accommodation." That gives you a fair way to talk about the work without asking about anyone's health.
A practical approach follows:
- Prepare a detailed position description before the interview. List the tasks in plain language: what the person will do in a typical day or week, which tools they will use, what they will need to produce, and who they will work with. A vague job title does not give an applicant enough to answer the question.
- Share the same description with every applicant. Do not give it only to the person who asked for an accommodation. Giving everyone the same material is part of treating them fairly.
- Ask the same question of everyone. Use the guidance's wording about performing the functions described in the role, and use identical wording each time. The question stays about the work, not the person.
- Talk about the arrangement, not the reason. If an applicant names an arrangement, ask what would help them show their skills. Keep the conversation on the format and what it needs to be, not the medical reason behind it.
Here is how the difference looks in practice:
| Stays on the job | Drifts into health |
|---|---|
| What would help you show your skills in this interview? | What is your condition, and how long have you had it? |
| Can you do the functions described in this position? | Does your condition affect how you do everyday tasks? |
| Which tools will you need to complete the exercise? | Is your condition getting worse? |
The right-hand column may sound like polite curiosity. Each question in it, though, is about a disability, and interviewers may not ask about one.
Consider a short scenario. An applicant for a warehouse supervisor role tells the interviewer that they will need the questions in writing and a few extra minutes on each answer. The interviewer answers the first part well, then asks, "Is that because of something with your health?" The applicant pauses, and the conversation shifts from the job to their body.
A better path is to say, "Thanks for telling me. Let's make sure you have the questions in writing and enough time.
Watch for these common mistakes:
- Asking follow-up questions about a disclosed condition "just to understand." The interviewer's job is to understand the work, not the applicant's health.
- Remarking on an applicant's appearance, movement, or speech in a way that suggests the interviewer has noticed a disability.
- Letting one panel member ask a question the others were told to avoid. Brief all interviewers beforehand, and give them the same list of acceptable questions.
- Writing a diagnosis, or a guess about one, into interview notes. If a note mentions a condition, it becomes a record of a question that should not have been asked.
If you slip, correct it calmly. Say something like, "I shouldn't have asked that. Let's get back to the role." Then move on. Do not explain or apologize at length, because a long apology draws more attention to the health detail than the original question did.
The interviewer's job is not to diagnose anyone or to decide how much an applicant's condition matters. The job is to match the work to the applicant's stated needs and to make sure every applicant gets a fair chance to show what they can do. A good interview leaves the applicant feeling asked about the job, not about their body or history.
Finally, prepare the people who will be in the room. A panel that does not know the rules will improvise, and improvised questions are where the boundary usually gets crossed. Spend ten minutes before the interview reviewing the position description, the approved questions, and the lines you may not cross. Afterward, talk through the notes together so that everyone knows nothing crossed the line.
Duty 3: Work out the arrangement, test it against the job, and set it up before the day
The third duty is follow-through. Once a request is recognized and the questions stay on the job, someone has to work out what will be provided and make sure it is ready before the applicant arrives. This is where good intentions often fall apart. The request is noted, the team agrees to "take care of it," and on the day the room is wrong, the video link fails, or nobody knows who is meeting the applicant at the door.
| Cost factor | What is weighed | Source |
|---|---|---|
| Overall financial resources | Facility involved in the provision | New Hampshire |
| Number of persons employed | Persons at such facility | New Hampshire |
| Effect on expenses and resources | Impact on the operation of the facility | New Hampshire |
Use the table below as a quick reference when a request comes in.
| Topic | What it means for you |
|---|---|
| Questions about a disability | Do not ask them, even out of curiosity |
| Specific information about the work and any accommodation | Ask, but keep it about tasks and needs |
| Position description | Share a detailed one with every applicant |
| Performing the functions described | Ask every applicant the same question |
| Kinds of accommodations | See Accessibility of Job Information, 5.2 |
The manual also offers a starting point. It notes that "Some of the kinds of accommodations that may be needed have been suggested in the section on Accessibility of Job Information, 5.2 above." Reading that section before a request arrives gives your team concrete options to discuss, rather than a blank page. It also helps you avoid a common failure, which is answering a request with "we don't know what would work" and no further effort.
Next, talk with the applicant. Ask what they need, and listen. Applicants know their own needs better than anyone on your team, and the most useful conversations are short and specific. Ask which format works best, what details they would like in advance, how they prefer to receive information, and who they should contact on the day. Avoid guessing on their behalf. An arrangement built on assumptions often misses the mark, and it can add stress for an applicant who then has to correct it under pressure.
Let the applicant decide what they are comfortable sharing. Some people will say a great deal, and others will name a single detail. Either way, your job is to act on what was said, not to ask for more.
Then measure the arrangement against the job itself. The point of an interview is to let the applicant show they can do the work, so ask whether the format allows that. A written exercise that depends on a format the applicant cannot use may not measure the skills the role needs. A panel that cannot see or hear the applicant may get an incomplete picture. Adjust the format so the interview tests the job, and be honest with yourself if the setup you chose gets in the way of the skills you are trying to measure.
Plan for the applicant's experience, too. Picture the path from the lobby to the interview room, the moment the applicant logs in, and the first question they hear. Where would a person with the requested arrangement run into trouble? If the answer is a closed door, a missing interpreter, or a form that only works with a mouse, fix it before the day. Small details matter, and they are easy to miss when the request is treated as a box to tick.
If you cannot provide exactly what was asked, do not let the request die quietly. Say so, explain what you can offer, and ask the applicant what would work. Do not decide alone that an arrangement is impossible. Bring in the people who know the facts, such as the hiring manager and facilities staff, and consider the options together.
Cost is a fair thing to weigh, but it is weighed against the organization making the decision. Under the New Hampshire statute, cost is weighed against the resources of the facility involved and the number of people it employs; other jurisdictions and federal guidance may weigh cost differently.
Next, send a short message listing what was agreed: the format, the date and time, the room or platform, the person who will meet the applicant, the contact for questions, and any materials you will send in advance. Ask the applicant to tell you if anything differs from what they need.
Then test the setup before the day. Run through the video link, look at the room, confirm that materials are in the right format, and make sure the people involved know their roles.
On the day, assign one person as the applicant's contact. That person should know the arrangement in detail and ideally should not be scoring the applicant, so that logistics and evaluation stay separate. Plan for things going wrong, such as a late interpreter, a broken link, or a room that is already booked. A prepared fallback protects the applicant from the stress of the problem and keeps the interview on track.
After the interview, ask the applicant and the panel what worked and what did not. Their answers will show what to fix if the arrangement needs to change for a later round, and they will help you explain the decision if the applicant is not selected. The decision should rest on the job's requirements, and that feedback helps show that it did.
Put the three duties together. Recognize the request and keep it from counting against the applicant. Keep your questions on the job rather than on the disability. Make the arrangement real and ready before the applicant arrives. None of these duties asks you to be an expert in disability law. They ask you to listen, ask the right questions, and follow through. Applicants who get that treatment can compete on the same terms as everyone else.