Accessability about vex HOT 5 OPEN

Yes! I would really like to help tackle this as well.

vex.dialog is already in pretty good shape in that it uses real input[button] and input[submit] buttons and allows submission through the native form element. But yes, we should be using aria- attrs, etc.

from vex.

yo @cnecochea want to come give us your .02 ? (or .05 )

from vex.

gladly. when should I be where?

-cris

On Oct 21, 2013, at 3:11 PM, Jeff Dwyer [email protected] wrote:

yo @cnecochea want to come give us your .02 ? (or .05 )

—
Reply to this email directly or view it on GitHub.

from vex.

Anytime, maybe wait a week so @adamschwartz will be back in town. I'd also love your thoughts on messenger, it has a similar issue: HubSpot/messenger#10

from vex.

Hey, I stumbled across this. If you make the following changes, you should have an accessible modal.

• Add ARIA to your overall modal class.
  • role="dialog"
  • aria-label="label here" or aria-labelledby="id of labelling element"— title of the modal
  • aria-describedby="id of description element"— optional, lengthier description of the modal's contents
• Make the exit button a <button> with a title. If you want it to be an "X" add aria-label="close"
• Automatically .focus() the element with role="dialog"
  • Prevent focus from leaving an open dialog (wrap around).

Check out the Incredible Accessible Modal

from vex.