Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
It depends if that behaviour is documented somewhere in the button behaviour. You can’t rely on people’s intuition.
Well, the logic is simple:
1. The modal purpose is to set a link.
2. You would love to write the URL in order to set the link.
3. You don’t have to click the URL input if it’s empty because it’s already autofocused.
Intuition supports eliminating user steps for executing the purpose of the modal.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
That’s a good case for someone who is sighted, but isn’t there some useful information that would be skipped for people who can’t see the page?
Excuse me, but if you mean for people with eyesight (or else) disabilities, I believe that WP is with ARIA accessible markup. These issues are solved perfectly as I believe the electronic reader or else will promptly notice -> “autofocus input named URL”. The user would simply ask to paste or enter content via appropriated method for him/her.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
I can foresee this being more of a burden than an enhancement.
Please, give me some track to understand why.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
I just want to make clear that I’m not a core developer.
The text is already there on the popup window above the form and people can read that out. The core developers don’t know how fast people can read it out and they should not move the focus indicator straight into the form when the popup appears. For this change to make sense for assistive technologies, ARIA would have to be used as you said. I just feel like it would be using ARIA to resolve a problem that would have been introduced by moving the focus indicator – which is not really the best way to go about things.
