Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide the visually hidden file input from assistive technologies #185

Open
afercia opened this issue Dec 11, 2019 · 0 comments
Open

Hide the visually hidden file input from assistive technologies #185

afercia opened this issue Dec 11, 2019 · 0 comments

Comments

@afercia
Copy link

afercia commented Dec 11, 2019

On a related issue on the WordPress Trac, it was pointed out that the visually hidden input of type=file FileInput is still perceived by assistive technologies e.g. screen readers. See https://core.trac.wordpress.org/ticket/47611

This input is visually hidden (positioned off screen) thus it's meant to be not available to sighted users.

A while ago, it was also made not available to keyboard users by adding a tabindex="-1" attribute to it, see d2e3bfd

However, when using a screen reader this input is still perceived and can be navigated to, for example:

  • by using arrow keys (which is the most commonly navigation mechanism used by screen reader users)
  • by using one of the several navigation tools screen readers provide, for example: the list of form controls in a page (see screenshot below)

In order to make this input non perceivable by assistive technology users too, it would be great to consider to add an aria-hidden="true" attribute to it. This should be enough to effectively hide it from assistive technologies (pending testing with various browsers / screen readers / other assistive technologies).

Screenshot using Safari + VoiceOver and the list of form controls provided by the VoiceOver "rotor" in WordPress:

Screenshot 2019-12-11 at 10 17 54

Screenshot using Safari + VoiceOver and Control Option Arrow keys to navigate content:

Screenshot 2019-12-11 at 10 29 30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant