Subscribe: Comments for WebAIM Blog
http://webaim.org/blog/wp-commentsrss2.php
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
comment screen  comment  content  reader user  reader  screen reader  screen readers  screen  survey results  things  user  web 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Comments for WebAIM Blog

Comments for WebAIM Blog



The WebAIM Web Accessibility Blog



Last Build Date: Thu, 11 Jan 2018 04:01:52 +0000

 



Comment on Screen Reader User Survey #7 Results by Donna

Thu, 11 Jan 2018 04:01:52 +0000

“Screens or parts of screens that change unexpectedly” - are we talking sliders (carousels) here?



Comment on DOJ Withdraws ADA Rulemaking Process by Sid Haas

Wed, 10 Jan 2018 18:15:37 +0000

Excellent post! The intent behind the WCAG guidelines and other web accessibility efforts is to make web sites better for everyone and to ensure that people with disabilities can effectively access content and conduct business online. The magnitude of threat letters sent be a few bad egg law firms has resulted in web accessibility changes being implemented to avoid lawsuits and minimize settlements. It's unfortunate that the DOJ has failed to adopt an official standard for web accessibility "compliance".



Comment on Screen Reader User Survey #7 Results by Jared Smith

Sat, 23 Dec 2017 22:24:42 +0000

Jeffrey - ZoomText certainly is a screen reader. It may primarily be used for magnification, but it definitely has screen reader functionality. We'd love to conduct a truly representative survey of screen reader users, but barring very significant funding to make that happen, we certainly hope these data are helpful and insightful. If not fully representative of all screen reader users, we can at least know that they are representative of the 1792 people that took the time to respond.



Comment on Screen Reader User Survey #7 Results by Jeffrey

Sat, 23 Dec 2017 22:15:47 +0000

Zoomtext isn't a screen reader; so those users likely don't consider themselves screen reader users - which likely is part of the reason you don't see it in the results consistently. The #s on the survey remain low at best and likely can't be considered more than anecdotal when it comes to tool usage because of it.



Comment on Screen Reader User Survey #7 Results by Dallas Dee Brauninger

Fri, 22 Dec 2017 18:56:42 +0000

A reluctant JAWS user after years of W-E, but I am slowly learning. Recent online re-download of update with JAWS technician plus a trip out here to the country by my computer tech yielded positive result after speech stopped. many thanks. Survey results of help to me. Thanks again.



Comment on Screen Reader User Survey #7 Results by David Taylor

Fri, 22 Dec 2017 12:09:57 +0000

Landmarks do not give you a structured way to find different sections of a website, and are almost always redundant. Forinstance, when looking between different sections, even of this site, you need headings to find where they start, not landmarks. Search regions can be found just as easily by looking for an edit control. Aria is something invented and championed by sighted people, not blind people. The main use it has is in making a screen reader behave differently, particularly in app regions. This can sometimes be useful, but often actually causes more problems than it solves, as we can't easily escape from that part of the site to another without extra commands, and even those sometimes get broken. Headings are the most useful for us blind people, and this is something we are fairly close to having standardised, so let's build on it. People have a good idea how to use headings now. Landmarks are not such, and to treat content as one area shows this, it's the content we usually want to navigate around



Comment on Screen Readers and CSS: Are We Going Out of Style (and into Content)? by Philipp

Wed, 15 Nov 2017 14:36:14 +0000

Wouldn’t it be great if there is something like „Browserstack“ but just for screenreader? So you can test different screenreader over different browser (and maybe hardware). 
Does somebody know if there is something like that out there somewhere? If someone is interested —> contact me and i’ll make a project around that ;-) (p.holz@inovex.de)



Comment on Screen Readers and CSS: Are We Going Out of Style (and into Content)? by John Northup

Wed, 08 Nov 2017 16:45:22 +0000

It's tempting to use tabindex and ARIA, but this can turn into a real maintenance issue. We regard ARIA as a tool of last resort, for things that HTML can't do. As for tabindex--we have never seen an implementation of positive tabindex values that didn't just cause more problems. We advise developers to structure HTML in a logical order and to position that content visually as needed with CSS.



Comment on Screen Readers and CSS: Are We Going Out of Style (and into Content)? by Mike

Wed, 08 Nov 2017 11:59:07 +0000

As we know that in CSS3, we have some advanced properties that is used for positioning the elements as well as designing them beautifully. But, usually the designers break the order of content which is visually perfect but not suitable for screen-reader. So, we should prefer using 'tab-index' and aria-* attributes.



Comment on Screen Readers and CSS: Are We Going Out of Style (and into Content)? by Blee Blat

Sun, 24 Sep 2017 03:03:08 +0000

This is not just frustrating for developers, it also is hard for users. I would like it if I could just use one browser/screen reader combination for computers and one for mobile. But sadly, I'm stuck having at least 2 screen readers on the computer and 2 browsers. The phones only have one screen reader handy, so that's all I have on Android and iOS when I was using it. Having to bounce browser /screen reader combinations just because one doesn't read the page accurately is not helpful. I wonder if there's anything we can do for this? How common is it for computer users who don't rely on assistive technology to have to run the same site through multiple browsers to read it effectively? Currently there are weird bugs in some browser screen reader combinations where certain page elements are not read or read incompletely. The only way you know when things are read wrong on some pages is to use another screen reader, or the same screen reader with another browser. This tends to mostly affect CSS or forms, but probably affects other javascript and things. I'm not a web developer, but I could learn if someone thought it'd help. Standards are often ignored anyway, just like legislation. Having a standard doesn't really help. If someone wants to customize the heck out of their system, they will, and you can't test every case. Part of this is up to the user to know how to use the technology, and part of it is the developer having enough compassion to make the best job of writing the pages and code accurately. There's no standard that you could write that will make someone care about something enough to do it. Legislation of anything is likely to have a negative affect anyway especially among caring people. The other problem is that acccessibiliity means nothing if you don't need to use it yourself. I hit the same snag once when I wrote a program that didn't take into account unicode, because I only speak English and have no way to test internationalization. I suspect this happens to developers as well. If they don't know a screen reader user personally, why would they think to make things accessible? You can't legislate altruism, which is what this comes down to. Part of the problem with some screen readers is things like NVDA's "browse mode" which I personally don't like because it breaks every web app with keyboard shortcuts. I happen to like a lot of keyboard shortcuts. Facebook and Google Music are examples where this is particularly annoying. I have a large music library and I'd have a larger feed possibly if that particular site wasn't so cumbersome to navigate and use. But built-in screen readers like Narrator and Voiceover don't receive updates quick enough to keep up with a dynamic web. W3C recommendations can't move fast enough either. It'd be helpful to include things like Orca and Linux because users of those platforms are more likely to be able to help developers fix a lot of the things that are broken. The worst thing you can do is have screen readers parsing HTML because that's where most of the trouble starts. We should discourage that practice. A screen reader is supposed to read the screen and leave it up to the user what to do with the data. Probably the place to start is to get operating system makers to expose accessibility API's in such a way that things like "browse mode" or virtual buffers can never happen. That will get rid of a large class of odd behavior and make sure that the user and the developer both know precisely what markup or code is doing at all times. If this comment is too long or out of place otherwise not helpful, feel free to delete it. Otherwise thank you for reading and I hope the somewhat random and disorganize[...]