wcag

Specifically, once I get the WCAG Anaylsis warnings for a website into my warnings window I can't get rid of them, until I close down studio. When building another project in the same solution they stay there. Anyone got any ideas? I came across this question yesterday looking for an easy answer. While closing the solution works for me, and then rebuilding only the solution I want to see warnings on, I found that doing a "Clean Solution" (right-click solution, select "Clean Solution") will clear the Error List pane (including warnings). Unload/Reload project I regularly get stubborn errors

What would be the best method to code heading/title of <ul> or <ol> ? Like we have <caption> in <table> , and we don't want to make them bold. Is this okay? <p>heading</p> <ul> <li>list item</li> <li>list item</li> <li>list item</li> </ul> Or should headings always be used? <h3|4|5|6>heading</h3|4|5|6> <ul> <li>list item</li> <li>list item</li> <li>list item</li> </ul> Always use heading tags for headings. The clue is in the name :) If you don’t want them to be bold, change their style with CSS. For example: HTML: <h3 class="list-heading">heading</h3> <ul> <li>list item </li> <li>list item <

What is the limit of character to use in alt="text" according to WCAG 2.0? there is no limit explicitly set, but conventionally they are limited to 1024 chars. I believe that I have heard that the search engines will go no further than about 200 characters. What is the use case? There is a longdesc attribute that may be of interest... http://www.w3.org/TR/REC-html40/struct/objects.html#adef-longdesc-IMG WCAG says: Sometimes images are worth a thousand words. Maps, Graphs and Charts are examples of images that contain information necessary to understanding the message of a page but too complex

Does compliance to WCAG 2.0 AA prevent the use of JavaScript? My understanding based on Understanding Conformance is that we can still use JavaScript as long as we don't generate any content that is noncompliant and that we explicitly state we support JavaScript. Is that correct? The short answer is, no, it doesn't. Your understanding is pretty much correct. Clayton A slightly longer answer is that pages can require JavaScript (AKA ECMAScript), but it's better if they don't. Use JavaScript sparingly and carefully. There's a set of guidelines for using JavaScript on WCAG 2.0 compliant pages .