screen-readers

Is it necessary to have <th> in any table?

由 大憨熊 提交于 2019-12-01 08:22:49
问题 is it necessary to have <th> in any table? even if table has no heading? table has 3 other tag <thead> <tbody> <tfoot> is it necessary to use all even if i have nothing for table footer. Firefox by default add all these in code. and is it necessary , <th> always should be in a <thead> and if I have a heading in content received from client , and heading is from outside the table but related to table then how should i place that heading for table As a above table <h3>Heading of table<h3>

Why are table based sites bad for screen reader users?

由 ╄→尐↘猪︶ㄣ 提交于 2019-12-01 06:47:36
问题 How much easier is it for screen readers to handle <div> based websites as opposed to older <table> based websites, and why are they worse? 回答1: Screen readers assume the content inside a table is tabular, and reads it as such. E.g. "row 1, column 1: (contents)". If you use tables to lay out your site, this won't necessarily make any sense. You are telling the end-client you have data with tabular significance, when you actually don't. By contrast, div have no meaning other than "section", so

What are usability, accessibility, screen-reader or any other development, functionality, cross browser issue with iframe?

由 萝らか妹 提交于 2019-12-01 01:14:02
问题 What are the usability, accessibility, screen-reader, or any other development, functionality, or cross browser issues with <iframe> ? Is there any alternative for <iframe> ? And are there any JavaScript/jQuery or server-side techniques which can decrease the usability, accessibility, or screen-reader issues with <iframe> ? Why has the W3C not included <iframe> in XHTML Strict, while HTML 5 supports <iframe> ? update: I found some good thoughts here also : http://uxexchange.com/questions/1817

How can I make screen readers respond to showing and hiding content in a dynamic web application?

由 此生再无相见时 提交于 2019-11-30 21:03:37
I would like to create an accessible web page which contains a number of components that can be hidden and shown as the user interacts with the page. When a component is shown I expect a screen reader (in this case NVDA) to read the contents of the component. As an example: <html> <body> <div id="comp1" style="display:none;" role="region" tabindex="-1" aria-expanded="false"> <div>This is component 1</div> <button type="button" onclick="ShowComponent(comp2)">Show 2</button> </div> <div id="comp2" style="display:none;" role="region" tabindex="-1" aria-expanded="false"> <div>This is component 2<

aria-label, aria-labelledby and aria-describedby: very unforeseeable behaviour in screenreaders

由 大城市里の小女人 提交于 2019-11-30 15:35:41
问题 I just noticed that although the aria-label , aria-labelledby and aria-describedby attributes are said to work on every element (see https://www.w3.org/WAI/PF/aria-1.1/states_and_properties#aria-describedby), they only seem to work for a few elements like a , and not for e.g. div or p in NVDA and JAWS. I have created a small codepen to demonstrate the issue (browse it using browse and focus mode): https://codepen.io/jmuheim/pen/avWbPe For example, in NVDA, on the a element, the aria-label and

aria-label, aria-labelledby and aria-describedby: very unforeseeable behaviour in screenreaders

由 百般思念 提交于 2019-11-30 14:36:28
I just noticed that although the aria-label , aria-labelledby and aria-describedby attributes are said to work on every element (see https://www.w3.org/WAI/PF/aria-1.1/states_and_properties#aria-describedby ), they only seem to work for a few elements like a , and not for e.g. div or p in NVDA and JAWS. I have created a small codepen to demonstrate the issue (browse it using browse and focus mode): https://codepen.io/jmuheim/pen/avWbPe For example, in NVDA, on the a element, the aria-label and aria-labelledby seem to work in both browse and focus mode. But aria-describedby is only announced in

Placeholder VS Label for input in HTML5

由 三世轮回 提交于 2019-11-30 12:02:24
I'm Making a form with multiple inputs where I need to give lable of form element inside input itself and I'm using like this An example <form class="TTWForm"> <input type="email" name="email" required="required" placeholder="Email Address"> </form> And above code is Valid in W3C validator for HTML5. Does Label not require in HTML 5? If I'm using HTML5 Placeholder to show label inside input is that ok? Does label still required along with placeholder to make it screen reader compatible? HTML validators will not check accessibility. Valid HTML can still be inaccessible or less than optimal.

Why WCAG made 3 level “A”, “AA” and “AAA”?

由 徘徊边缘 提交于 2019-11-30 11:37:50
问题 What is the purpose of making 3 priority level by WCAG? is it like? If client not paying extra or if we don't have much time then go for A If client paying then or if we have time to make site compatible go for at least AA If client paying and needed according to govt. rules then go for AAA If we are making site then which level we should we try to achieve, or we should do only on client request? Although i found these definitions on this site but these are confusing for me • Priority 1: For

Should we put <input> inside <label>? [duplicate]

由 ⅰ亾dé卋堺 提交于 2019-11-30 08:58:12
This question already has an answer here: Should I put input elements inside a label element? 12 answers I saw 2 different method on same form example: on http://www.alistapart.com/articles/prettyaccessibleforms/ why they are using 2 method in first fieldset they are keeping input after label and in 2nd fieldset they are keeping input after label . Why? <fieldset> <legend>Delivery Details</legend> <ol> <li> <label for="name">Name<em>*</em></label> <input id="name" /> </li> <li> <label for="address1">Address<em>*</em></label> <input id="address1" /> </li> <li> <label for="address2">Address 2<

Is it possible to use javascript to detect if a screen reader is running on a users machine?

由 孤者浪人 提交于 2019-11-30 07:57:18
问题 I want to detect whether a screen reader is running on a user's machine to avoid sound clashing with audio tag in html. If so, please provide details on how this could be done. 回答1: You should probably not try to do anything special even if you could detect that a screenreader is running. Even if you get it right for one group of screenreader users, you may get it wrong for another group. It's best to concentrate on writing good clean HTML5 in the first place. Note that not all screenreader
订阅 screen-readers