Problem/Motivation
During the Minnesota Accessibility studies at Drupal Camp Twin Cities in 2013, our testers noted that a file upload field does not express to a screen reader that the file upload is in progress or that the upload is finished.
Proposed resolution
First, manual testing is needed to confirm the problem exists.
We might try a progress
tag http://www.w3schools.com/tags/tag_progress.asp
Remaining tasks
Test with PECL to determine if this is still a problem.
Try to reproduce this issue and make a video. Post the link to the video.
User interface changes
For screen reading user agents, the uploading of a file will be indicated aurally.
API changes
Maybe a change to the file field.
Comments
Comment #1
mgiffordRelated issue #1333292: Screen-reader users receive information if file upload was successful
There's no indication even that the upload was successful.
Needless to say, this would be useful, particularly with large files or slow connections.
Comment #2
mgiffordComment #3
mgiffordComment #4
Anishnirmal CreditAttribution: Anishnirmal as a volunteer and commentedComment #6
Anishnirmal CreditAttribution: Anishnirmal as a volunteer and at UniMity Solutions Pvt Limited commentedHi,
Can anyone suggest me with an approach. If the file upload field is provided with a progress tag as mentioned below
<progress value="43" max="100"></progress>
Do i need to update the upload progress via ajax frequently (i.e status of the upload progress), or updating once the upload completes.
Comment #18
catchCore supports a progress indicator out of the box, however it only appears when you have PECL uploadprogress installed:
From file_requirements()
It's not clear to me whether the issue summary was written with this in mind. If it's to add that, then I think we can close this as outdated. However if there is something that could be added to the non-upload progress file widget when a file is actually uploaded, that seems worth adding separately.
Comment #21
quietone CreditAttribution: quietone at PreviousNext commentedI asked about this in #accessibility. @mgifford responded stating that this needs to be tested with PECL to determine if this is still an issue.
I am adding the tag for manual testing and setting to Needs Work for the manual testing.
Comment #22
mgiffordI think we can tie this most closely to 3.3.1.