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

Spinbutton - Initial commit, work in progress #724

Merged

Conversation

gerardkcohen
Copy link
Contributor

This is the initial commit for the Spinbutton issue #125, very much a work in progress.

Testing without AT (VoiceOver/ Safari), UP/DOWN will increment/ decrement as designed. With AT, VoiceOver suggests different keys for operation. I am looking for advice on how to proceed.

With VO, CTRL+OPTION+UP/DOWN is required to increment/ decrement the counter. CTRL+OPTION is not firing, so while VO is announcing the change I am not capturing any events to respond to.

cc: @mcking65

@mcking65
Copy link
Contributor

mcking65 commented Jun 22, 2018

@gerardkcohen,

Revising my request here since I learned you can change the base branch of a PR.

I'd like to develop this in a feature branch before landing in master. I made branch issue125-add-spinbutton-example. Could you please edit this pull request and change the base branch from master to issue125-add-spinbutton-example?

Also, please run npm test. There's eslint errors.

WRT the VO slider keys, it is a bug in VO that it provides that keyboard help for a web slider. Those keys only work on native sliders. Without AOM, it is not possible for us to capture VO slider increment and decrement events in JavaScript.

@mcking65 mcking65 changed the base branch from master to issue125-add-spinbutton-example June 25, 2018 00:22
@mcking65
Copy link
Contributor

@gerardkcohen, I just realized I can change the base branch on anyone's PR ... so I did that. But, we still have errors. Please push another commit to your compare branch to fix those. Thanks!

@gerardkcohen
Copy link
Contributor Author

@mcking65 In a bit of a bad cycle here. I am getting the error "Element input is missing one or more of the following attributes: type." when trying validate HTML.

Ok, add type="text" and get "Bad value spinbutton for attribute role on element input." with "Attribute aria-valuemin not allowed on element input at this point."

I can use type="number" and get off with a warning of "The spinbutton role is unnecessary for element input whose type is number." but then example changes with the native browser spinbutton UI.

This seems like a validator issue. @stevefaulkner, any comments?

@mcking65
Copy link
Contributor

mcking65 commented Jun 26, 2018

Raised w3c/html-aria#111.

@stevefaulkner
Copy link

@gerardkcohen will review and update where necessary

@mcking65
Copy link
Contributor

@gerardkcohen, stevefaulkner closed w3c/html-aria#111 so that when validator/validator#670 is closed, the validator will allow role spinbutton on input type text.

@gerardkcohen
Copy link
Contributor Author

@stevefaulkner Thanks for the quick turnaround. Since the default type for input is text would omitting the type also pass?

@mcking65 mcking65 merged commit ed36d3e into w3c:issue125-add-spinbutton-example Jul 11, 2018
@stevefaulkner
Copy link

@gerardkcohen WFM

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

Successfully merging this pull request may close these issues.

3 participants