-
Notifications
You must be signed in to change notification settings - Fork 799
-
Notifications
You must be signed in to change notification settings - Fork 799
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
WCAG20 compatibility #601
Comments
@Noino We will work on this. I think it is important to support WCAG20. We will discuss this issue and I will comeback. Thank you, |
@andrewtelnov Woah, quick answer too. |
@Noino I've fixed a set of compatibility issues. Could you check it in the nearest release? |
@tsv2013 Sorry for the delayed response. The chrome addon reports this code block (and the similar ones for that question)
Generated from this json
as flagged with error:
And also alert (this same alert appears where radio buttons are used):
There are some others listed too but these are the only errors it reports. I've also attached the pdf report from achecker.ca which lists 60 known problems with this sample form. achecker_2017-10-10_10-22-45.pdf Source code for this report:
|
@Noino This markup
is used to support bootstrap material design skin, because it requires specific DOM structure. We need to discuss the fix with the team. |
…label (label tag is required for material design)
@Noino @andrewtelnov I've added dummy span as a temporary measure to suppress the error. As for fieldset tag - if this warning is not crucial, I wouldn't like to add extra markup on the page. |
I believe that it is necessary to fieldset radio buttons, and even checkboxes that are part of a multiple choice question.
|
What is the status of this issue? It seems like there has been some progress, but the changes are still underway? |
@okkuweb I've fixed all errors shown by WCAG20 validators. There are still some warnings. Some of them require markup changes and adding additional markup. The markup changes can became "breaking changes". I'd like to evaluate warnings cruciality to fix most crucial ones to minimize markup changes. |
@tsv2013 Thanks for your hard work. Seems you've got pretty much all of them down. Really only fieldsets remaining as far as i can see, and i'm not sure how you are supposed to accomplish that within matrix tables, but in my form "6. question2" and "7. question3" you have a One thing i noticed trying that same form through achecker.ca again (even though it seems to not understand html5 very well) was that I'm getting a duplicate id "sp_100" which i don't think is valid html. |
@Noino Thank you for the valueable feedback! I'll fix remaining issues and update this thread. Hope it will be soon. |
@Noino I've added fieldset tags with necessary 'legend' tags inside. Thank you for cooperation |
The lastest change (8578f4f) seems to be missing in jquery and angular? |
@Noino jquery and angular libraries are based on the the react code. They're just wrappers. |
@tsv2013 Alright. Thought it might have been the case since i was seeing some complaints about fieldsets missing still, but turns out it was a cache issue, hard reload fixed almost all. Sorry for resurrecting a closed ticket, should've noticed this before |
Are you requesting a feature, reporting a bug or ask a question?
Bug/Feature
What is the current behavior?
The html generated does not conform to WCAG20 (https://www.w3.org/TR/WCAG20/) standards, and it therefor unusable by people with certain disabilities
What is the expected behavior?
That the html generated would confirm to WCAG20 and be usable by everyone.
How would you reproduce the current behavior (if this is a bug)?
Make a form, any kind of form, copy the resulting html to a validator
here: https://achecker.ca/checker/index.php
or using an extension: https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
Specify your
The text was updated successfully, but these errors were encountered: