THanks this is the info I was looking for. So, generally it is not as bad as being completely inaccessible, but perhaps annoying. :) Although most of the web is annoying anymore, so can't be all that bad. :) Thanks for the feedback.
On Apr 23, 2012, at 12:14 PM, Chris Blouch wrote: > The main issue with Ajax is that updates to the page are not noticed by the > screen reader unless the developer moves focus to the changed content or sets > a live region attribute on the container. This isn't something mere users can > fix other than setting a hotspot on the area so changes can be noticed. > Another snag is when a part of the page is 'rotating content' where they tick > through some stuff like top news stories or the like. This can be quite > disorienting if you're in the middle of reading and focus suddenly gets > yanked to the next story because things ticked. Usually there is a pause > button which stops the ticking, but not always. > > CB > > On 4/21/12 8:22 PM, Scott Howell wrote: >> All, >> >> Has anyone encountered problems accessing sites using ajax? I cannot think >> of a site immediately that heavily uses ajax. If you know of one I can try >> VO out with, please let me know. This is a slightly urgent request. >> >> Thanks, >> > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to macvisionaries@googlegroups.com. > To unsubscribe from this group, send email to > macvisionaries+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
