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

A11y Accessibility valid markup #53

Open
AutoSponge opened this issue Nov 2, 2017 · 7 comments
Open

A11y Accessibility valid markup #53

AutoSponge opened this issue Nov 2, 2017 · 7 comments

Comments

@AutoSponge
Copy link

Not a single form field has a label. These designs are not usable and the patterns presented should be discouraged.

I suggest adding a validation check like Nu Validator, aXe, lighthouse, etc. to show all the places this markup is invalid.

@dianaprajescu
Copy link
Contributor

Thanks @AutoSponge for your suggestion. This is the first iteration of the Froala Design Blocks and we are continuously looking to improve it. Accessibility is indeed one of the most important aspects we should look into.

@estevanmaito
Copy link

I would like to solve this, as it seems that no one is actively working on it.

blueocto pushed a commit to blueocto/design-blocks that referenced this issue Oct 10, 2019
@sarah-peacock
Copy link

@dianaprajescu Hey, I noticed @blueocto has a pull request for this issue. I'm interested in this update as well, would you mind taking a look?

@nice2meu
Copy link

nice2meu commented Apr 7, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@AutoSponge @dianaprajescu @estevanmaito @nice2meu @sarah-peacock and others