section508

Can a site REQUIRE Javascript and still be Section 508-compliant?

假如想象 提交于 2019-12-03 05:40:38
I think I understand HOW Javascript has to work in order to be O.K. for section 508. But I have been unable to find an answer to a related question: does my site need to work WITHOUT Javascript in order to be section 508 compliant? To take an extreme case, if users without Javascript cannot log in, does that violate section 508 compliance? And if so, where in the text is that explained? I know that all content has to be accessible with screenreaders, for keyboard-with-no-mouse users, etc. BUT does all content need to be accessible to users without Javascript? Recent surveys have found that a

MVC 4 site 508 compliant

£可爱£侵袭症+ 提交于 2019-12-02 08:28:44
问题 I have spent a lot of time researching this, but perhaps someone point me in the right direction. In need of building an MVC 4 website in which it is 508 Compliant. I did some 508 compliance testing and tag inserts 3 years ago, but I really want to look at doing this again. What are other people using? What tags to look for? What Testing Tools? Any free testing tools? Are AJAX and jQuery and Javascript compliant, I seem to find answers like "it depends" Thus in need of this compliance as the

If an element is wrapped by a label, does the label require the “for” attribute?

笑着哭i 提交于 2019-12-01 19:51:28
Say I have a set of radio <input> s. I'm not a caveman, so I know I need to associate <label> with those <input> s. I'm fond of wrapping the radio buttons within their corresponding labels, for reasons enumerated here . So, for example: <fieldset> <legend>Should I provide a "for" attribute?</legend> <label><input type="radio" name="define_the_for_attribute" id="define_the_for_attribute_yes" value="yes" />Yep, if you know what's good for you</label> <label><input type="radio" name="define_the_for_attribute" id="define_the_for_attribute_no" value="no" />Nah, that would be redundant and

iText 7 PDF accessibility: “Table header cell has no associated subcells”

[亡魂溺海] 提交于 2019-12-01 02:09:38
I am converting HTML to a PDF using iText 7. I need the PDF to be accessible (508 compliant with appropriate tags, etc), but, no matter what markup I put on a table, accessibility checkers give the same error: "Table header cell has no associated subcells". I've tried setting scope, headers, etc... nothing seems to work. Here is an example of one of the tables but all of them have the same issue: <table class="problems" summary="Patient's diagnosed problems and associated ICD codes."> <thead> <tr> <th scope="col" id="problem-header"> Problem </th> <th scope="col" id="icd-code-header"> Code <

Using “label for” on radio buttons

允我心安 提交于 2019-11-28 03:52:30
When using the "label for" parameter on radio buttons, to be 508 compliant *, is the following correct? <label for="button one"><input type="radio" name="group1" id="r1" value="1" /> button one</label> or is this? <input type="radio" name="group1" id="r1" value="1" /><label for="button one"> button one</label> Reason I ask is that in the second example, "label" is only encompassing the text and not the actual radio button. *Section 508 of the Rehabilitation Act of 1973 requires federal agencies to provide software and website accessibility to people with disabilities. Marc W You almost got it.

Using “label for” on radio buttons

大兔子大兔子 提交于 2019-11-27 00:14:04
问题 When using the "label for" parameter on radio buttons, to be 508 compliant*, is the following correct? <label for="button one"><input type="radio" name="group1" id="r1" value="1" /> button one</label> or is this? <input type="radio" name="group1" id="r1" value="1" /><label for="button one"> button one</label> Reason I ask is that in the second example, "label" is only encompassing the text and not the actual radio button. *Section 508 of the Rehabilitation Act of 1973 requires federal