Archive index

A11y Slackers Gitter Channel Archive 17th of October 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Oct 17 15:54
    [vyku] a general question should the logos on home page be considered as a decorative image? and skip screen reader focus if it is not clickable?
    Debate is that if it is not clickable don't have a ALT+text
    some argue if it is clickable on other page it is should be clickable on home page and screen reader accessible.
  2. [rselzer] wouldn't you want the first focusable item on your home page after skip to content to be the name of your site?
  3. zakim-robot
    @zakim-robot
    Oct 17 16:01
    [vyku] we read the title of the page and if the title is explaining what the site is about then I personally think we don't need to
  4. [svinkle] @vyku A logo should always have an alt value matching that of the text or name of the site. Providing a link back to the homepage is a bonus for folks who need to get back and start their task over. Also aligns nicely with WCAG 2.4.5 (https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-mult-loc.html).
  5. [svinkle] The title of the page would be reserved for the primary h1 element, describing the page purpose/content. The logo does not represent the page purpose.
  6. [rselzer] @vyku actually yeah that makes sense, I agree
  7. [vyku] thanks @svinkle never looked in to 2.4.5 going through it. Thanks for the info
  8. powrsurg
    @powrsurg
    Oct 17 18:14
    https://blogs.windows.com/msedgedev/2017/10/17/edgehtml-16-fall-creators-update/
  9. "Hear the web read out loud"
  10. Looks like Edge is getting its own screen reader?
  11. zakim-robot
    @zakim-robot
    Oct 17 18:15
    [eric] I believe it’s tighter support with/for Narrator
  12. zakim-robot
    @zakim-robot
    Oct 17 19:25
    [svinkle] Hey @info! :wave:
  13. [info] hello! :) better late than never
  14. zakim-robot
    @zakim-robot
    Oct 17 20:04
    [herin] :question: Hi, Have any one identified that ajax search results not being updated in Chrome accessibility tree? Is there any workaround for this? Firefox and IE seems to be fine.
  15. zakim-robot
    @zakim-robot
    Oct 17 20:15
    [svinkle] @herin Do you have an example where you’re experiencing this?
  16. zakim-robot
    @zakim-robot
    Oct 17 22:13
    [caesar] Sound like one for alice if and when it can be repro
  17. zakim-robot
    @zakim-robot
    Oct 17 23:59
    [laura.ciporen] Hello, helpful people! I've been experiencing a problem in PPT recently and I'm hoping someone here has a solution to it. We often have links in our PPTs that take you from one slide to another. We insert them by adding a hyperlink and then choosing "place in this document" and then the slide to which we want the link to take users. It used to be that when the slide was read it would say "link" at that link and then if you hit "enter" it would activate the link. Now, however, the link is neither announced nor possible to activate even if you tab to it. Sometimes however, when I hit "enter" on a link to which I have tabbed, JAWS tells me that there are no pointers on the slide. It is very strange! I've even checked the actions options and it is set to "mouse click". Does anyone have any thoughts or similar experiences? PPT 2010, JAWS 18, though this started when we were still on JAWS 17, I believe.