ACVREP CLVT common mistakes
ACVREP CLVT · Understand the traps and how to avoid them.
Reporting a single distance acuity value (e.g., 20/200) as the complete functional acuity finding without specifying the testing distance, chart type, illumination, or whether the value was obtained with or without the prescribed device.
Candidates memorize acuity notation and treat it as a stand-alone number, forgetting that functional acuity is only interpretable with its measurement conditions; they also conflate Snellen notation with M-units or logMAR.
What to do instead
For every acuity statement, record and report the metric (Snellen/logMAR/M-unit), the test distance, the chart or target used, the lighting condition, and the refractive/device condition. Practice converting between notations and stating the functional implication (e.g., print size accessible at a given distance).
Interpreting a visual field result as a single global descriptor (e.g., 'tunnel vision') without translating the measured field into functional consequences such as detection of obstacles, mobility, or reading span.
Candidates learn field-testing procedures but skip the interpretation step that connects isopters, scotoma location, and hemianopic patterns to real-world task performance.
What to do instead
For each field finding, explicitly state the location and extent of loss and pair it with at least one functional consequence (e.g., inferior field loss and fall risk, central scotoma and reading rate). Rehearse translating field plots into task-based statements.
Treating contrast sensitivity as interchangeable with visual acuity, or omitting contrast sensitivity testing when acuity is normal but the client reports difficulty in dim light or low-contrast environments.
Candidates over-rely on acuity as the summary measure and do not recognize that contrast sensitivity can be reduced independently and predicts performance in mobility and daily tasks.
What to do instead
Include contrast sensitivity as a distinct measure in every functional evaluation plan. Practice selecting appropriate targets (e.g., grating or letter contrast charts) and describing how the result informs environmental modifications and device selection.
Assessing color vision and stereopsis only nominally (recording 'tested' without interpreting the result) or skipping them entirely because they seem irrelevant to low vision device prescription.
Candidates prioritize acuity and fields and treat color and depth perception as peripheral findings, missing their relevance to task safety, occupational demands, and device use.
What to do instead
State the test used, the result, and the functional implication for each (e.g., color discrimination affecting medication or signal identification; reduced stereopsis affecting stairs and grasp). Tie findings to specific recommendations.
Conflating visual perceptual and visual motor deficits with acuity loss, attributing reading or handwriting difficulty solely to reduced acuity without screening perceptual-motor components.
Candidates with a strong optical/acuity orientation underweight the perceptual and motor contributors to literacy and daily task performance, especially in acquired brain injury or pediatric cases.
What to do instead
Use a structured screening of visual perceptual and visual motor function and explicitly separate sensory (acuity/field) from perceptual-motor contributors when explaining task difficulty. Document which component drives the functional limitation.
Taking an incomplete history that omits work history, educational performance, ADL/IADL status, technology use, or psychosocial factors, then writing goals that do not connect to the client's actual life roles.
Candidates focus on the clinical eye report and device fitting and treat the interview as a formality, so the evaluation lacks the contextual data needed for meaningful goal-setting.
What to do instead
Use a structured intake covering work/education, ADL/IADL, technology use, quality of life, and psychosocial and cognitive factors. Link each stated goal back to a documented functional limitation in one of those areas.
Documenting a device recommendation without recording the task, working distance, and environmental conditions under which the device was trialed and shown to be effective.
Candidates equate 'prescribed device' with 'successful outcome' and skip the trial documentation that demonstrates functional benefit and supports training targets.
What to do instead
For each device, record the task trialed, working distance, magnification/field of view, lighting, duration of use, and observed performance with and without the device. Base training goals on the documented trial results.
Designing instruction that teaches device mechanics (how to turn it on, how to focus) without teaching the client to integrate the device into real tasks and environments.
Candidates treat device operation as the endpoint of training rather than the prerequisite, so clients can operate the device but do not use it functionally.
What to do instead
Structure instruction from component skills to real-task application: eccentric viewing or scanning practice, then structured tasks in the actual environment, then generalization checks. Measure success by task performance, not device manipulation.
Failing to verify and train the required viewing distance, focus, and eccentric viewing technique for each prescribed device, allowing the client to use a magnifier at the wrong distance and conclude it does not work.
Candidates assume the device's labeled power guarantees function and do not account for the interaction of working distance, accommodation, and stand versus handheld use.
What to do instead
During instruction, explicitly establish and practice the correct eye-to-lens and lens-to-target distances, confirm focus, and teach eccentric viewing where indicated. Verify the client can reproduce correct technique independently before ending the session.
Writing progress notes and recommendations that describe activities performed ('trained with magnifier') rather than measurable change in function, making outcomes unverifiable and goals untestable.
Candidates default to activity-based documentation and do not convert findings into measurable baselines and targets, which undermines both accountability and goal revision.
What to do instead
For each goal, document a baseline measure (e.g., print size, reading rate, task completion, accuracy) and a criterion for success, then record post-instruction performance against that criterion. Revise the plan when data show no change.