So I am watching the videos the W3C just put out today on accessibility. In the demo on controls they showed radio buttons actually getting bigger. How does one actually do that?
What are good, accessible ways to actually style radio buttons and check boxes. I've seen it done a ton of ways with background images and some are good for managing the state, but this really does seem like an area where people are hacking around quite a bit to get something done that should be easier.
Chrome desktop is the only browser I'm aware of that supports text to speech, and even that is imperfect. But at least with that it would be sort of possible
oh, sorry. Yeah, I see that as possible for the controls. But it does feel to me like we're hacking things to create our own that uses things like border-radius, box-shadow, etc to do what we want.
[deborah_kaplan] For a website to account for things like voice macros, it just has to be well coded, with identified form fields, real submit buttons, real buttons, etc. Usual best practice.
[ccwilcox]@deborah_kaplan: so you wouldn't have to say "click place order," Dragon would just know that if you say the name of an HTML button that you mean to click it?
[deborah_kaplan] I've been having a lot of difficulties these last couple of years because instead of using form fields a lot of divs with role textarea, which has been causing issues with both voice and speech in my experience. I haven't dug down into why yet.
[deborah_kaplan] in fact, one of the aggravating Easter eggs of bad design, is that you can say the name of a hidden button, so if there's a label for a webfont or image icon, you can actually speak the name of it. If you happen to know how to inspect the code to find out what the name of it IS.
The actual submit buttons are the ones that I've always found weird to create a label. Usually to be compliant I just wrap the button/input inside a label
[deborah_kaplan]@powrsurg, I think you might be able to speak the name of both, but hang on, let me create a proof of concept and try it out. Give me 5 minutes.
I spent 8 years working with WYSIWYG editors before my current job (built our own and then switched to TinyMCE). It doesn't surprise me that users with AT had trouble
[ccwilcox] Referring back to the custom radio buttons in the Controls video that animate to get larger and had a green dot to indicate selection, I think multiple colors requires reinventing the wheel but getting larger could be possible with native buttons and CSS alone by using :focus and :hover to increase the font-size and CSS transition to animate it
Right. I just mean, but all of this is built off of hiding the controls and using :before on the labels (or something like that). I feel like we should be able to just style the controls better.
But wouldn't a better situation be to allow them to replace it with their own, rather than disabling it all together? I know you can sort of do this in at least some browsers
[ccwilcox] Not enough people clamoring for it for browser makers to put effort into it? The bigger issue in web practices is people creating custom controls and not including the real controls in the HTML and hiding them. "Native radio buttons are small, ugly, and look different in Chrome vs. IE, I'll just make some nice ones in Photoshop and add click events to the images."
@jiatyan looks okish. first thing i would do is change role="list region" to role="list". I'm pretty sure everything supports list so the region is meaningless anyway
I donated to that gofundme campaign for Molly that was supposed to get me the slides from 2 years worth of a conference, but I never received that. It was a good cause so that was fine, but I was a little interested in the content. One of the presentations was supposed to be on accessible PDFs.