Work on accessibility

[rosswintle]

No description provided.

[rm-code]

I would be really interested in using this for one of our projects, but we have pretty strict guidelines for accessibility.

You probably already know, but here are some things off the top of my head:

• Tabindex for the different option-buttons
• Focus indicators for buttons (so a user with a keyboard can tell which button they have currently selected)
• Let user define (optional) Aria-Labels for the buttons... e.g.:

    1: {
        text: 'Hi! Welcome to Peekobot.',
        options: [
            {
                text: '👋',
                aria-label:'Hello there!',
                next: 2

            }
        ]
    },

• I haven't tested screenreader support yet, but it might need an aria-live region?

Are you looking for help/PRs yet?

[rosswintle]

Thanks so much for your interest and suggested additions. I'm happy with the basics of accessibility, but am not so good on accessibility of highly interactive elements, so I do appreciate any help I can get!

It might be a few days before I get around to working on it again. So if you want to try and make a PR then that's great. If not I'll try and look at it next week. I'd love for it to be accessible!

Also, I'm happy to blow the 100-line limit. I'm using "less than 100 lines" in the description right now, but it doesn't have to be. So don't worry about that if you are making a PR.

Thanks again!

[nikas-belogolov]

if (option.ariaLabel) button.setAttribute("aria-label", option.ariaLabel);