Offer a usable file-picker alternative to dragging quote photos

Identify every action in the upload task

List the upload actions a customer needs: open the picker, select a file, understand its status, remove an incorrect file and continue. Put the mouse aside and try each action. A drop zone may display instructions yet fail to provide a reachable selection control. Test replacement too; selecting the right file is not the whole task.

Keep the picker and feedback understandable

W3C keyboard guidance supports an operable equivalent for pointer actions, and form instructions clarify expected input. Wix's upload field has configurable file settings. Use the platform's supported picker and verify how its visible and programmatic labels describe the task. Do not make customers depend on a drag gesture to provide a quotation image.

The non-drag pointer check is separate from the keyboard check. W3C's Dragging Movements criterion calls for a single-pointer alternative to applicable dragging actions. Test a tap or click that opens the picker and a tap or click that removes a selection, without requiring a drag gesture.

For Wix site forms, confirm the plan supports the premium upload field and identify whether the form uses the old or new builder. Inspect the existing field's privacy setting. Keep protected uploads protected and test authorized downloads; do not make them public merely to restore email previews.

Source checks: W3C: Understanding Keyboard · Wix Forms: Adding a File Upload Field · W3C WAI: Form Instructions · W3C: Understanding Dragging Movements

Test selection, rejection and removal

Prepare a harmless sample image and an unsupported sample file. Use the native picker from the keyboard, then remove the image and select another. Observe the file name, status and error text. Repeat on a phone, where selection sources may differ. Keep any essential instructions near the control rather than only inside the drop zone.

• Reach a clearly labeled file picker without using a mouse or drag gesture.
• Select a supported sample and verify the chosen file is identifiable.
• Remove or replace that selection through a reachable labeled action.
• Choose an unsupported sample and check the correction message and preserved form answers.
• Continue through submission and verify staff can retrieve the intended attachment.
• On a phone or with a mouse, use a single tap or click to choose and remove a file without dragging.

Avoid drag-only or visually silent behavior

A drag-only area can exclude customers who cannot perform that gesture. An unlabeled icon for removing a file may not communicate its purpose. A color change alone does not explain whether upload succeeded. Avoid claiming that a file has been accepted just because it was chosen locally; the receiving path still needs verification.

Record whether the full upload task completes

Record completion of each action with the tested input method. Separate local selection from upload acceptance and staff retrieval. Note where customers could not identify status or repair a wrong selection. These are task-level accessibility observations, not a full certification of the file component or every device's picker.

Preserve the alternative during redesigns

Keep the supported non-drag path and its labels in the component's maintenance note. Retest after changing upload settings, plan features or form builders. Staff should know how to recognize an attachment that arrived without a usable preview. Offer another enquiry route when the customer cannot supply a photo, if the service process allows it.

Worked example: an illustrative customer journey

For example, a fence-repair form advertises 'Drop your photo here' but its selection control is not reachable with the keyboard. The maintainer provides a labeled supported picker and a clear remove action. A sample user selects a non-sensitive image, removes it and chooses a replacement.

TEST-UPLOAD-3301 reaches storage with the intended file; an unsupported file receives a useful correction. This tests the upload task and alternative input route. It does not establish that photographs alone can assess the fence or that the whole site meets an accessibility standard.

Questions about this task