Archive index

A11y Slackers Gitter Channel Archive 8th of May 2017

What fresh hell is THIS now? - Patrick Lauke
  1. Damian
    @magga108_twitter
    May 08 11:15
    Is it possible to have Voiceover read a piece of content in a different language? I am able to get it to work for JAWS and NVDA, but not for Voiceover. The language of the page is English, and the language of the part is French. Here is a quick codepen for testing... http://s.codepen.io/dsianprinceton/debug/OmjYXz/NQMzYnngEQJk
  2. zakim-robot
    @zakim-robot
    May 08 11:18
    [hdv] as a VoiceOver user you can set up different voices, but then everything will be read in that voice. As far as I know the right way to let screenreaders recognise things in different languages is the lang attribute, just like you've used it
  3. zakim-robot
    @zakim-robot
    May 08 12:34
    [tink] Worth noting that last time I checked, VO on MacOS didn't do automatic language switching like it does on iOS.
  4. Damian
    @magga108_twitter
    May 08 13:38
    @zakim-robot is there anything in ARIA that would force VO to honor the lang attribute?
  5. zakim-robot
    @zakim-robot
    May 08 13:39
    [tink] It does honour it. But you have to have the language installed/enabled in the OS, and you have to do the switch manually.
  6. [tink] Whereas on iOS it switches automatically.
  7. [tink] But no, nothing in ARIA that can be used to change that behaviour.
  8. [tink] It's a flaw in the screen reader really.
  9. zakim-robot
    @zakim-robot
    May 08 14:29
    [michiel] For those that have some time and want to read or watch some interesting things, I’ve collected interesting accessibility related things in a blog post: https://moiety.me/thinks/more-interesting-accessibility-links.html
  10. zakim-robot
    @zakim-robot
    May 08 15:18
    [michiel] This project by cehfisher looks really interesting: http://a11y-style-guide.com/style-guide/
  11. zakim-robot
    @zakim-robot
    May 08 16:25
    [deathbear] Hi, I have a weird question for everyone. Please bare with me because I haven't had coffee yet and it's very monday. Has anyone ever used a screen reader's text output (eg NVDA's "Speech Viewer" or VoiceOver's text display window) in an integration test?
  12. [deathbear] OR additional question, again, I'm sorry I'm so tired, does anyone use any cool a11y tools in general when writing integration tests?
  13. [deathbear] I found https://github.com/pa11y/ci
  14. zakim-robot
    @zakim-robot
    May 08 16:34

    [karlgroves] > Has anyone ever used a screen reader’s text output (eg NVDA’s “Speech Viewer” or VoiceOver’s text display window) in an integration test?

    I wouldn’t.

  15. [karlgroves] I especially wouldn’t with VoiceOver. It would be an interesting experiment with NVDA. The problem is that you may wind up chasing your tail on things that are AT or browser AAPI implementation deficiencies.
  16. zakim-robot
    @zakim-robot
    May 08 16:46
    [michiel] Something that might be useful: https://help.apple.com/voiceover/info/guide/10.12/#/vo2725
  17. [michiel] Repeat, copy, or save the last spoken phrase
  18. [michiel] But I’ve found that it has incomplete output or has extra stuff in it.
  19. [michiel] I guess that’s due to how VO builds sentences.
  20. [tink] +1 to @karlgroves all the screen reader output gives you, is that particular screen reader's interpretation of what should be spoken. That's only part of the puzzle.
  21. zakim-robot
    @zakim-robot
    May 08 16:54
    [garcialo] @deathbear +1 to @tink @karlgroves. Although, you might be able to use it in regression testing to verify that what is announced by NVDA remains the same when you make changes that shouldn’t impact the front end. If the change is to the front end, then it won’t match exactly…I guess at that point, you could find where the differences occur and use it as a tool to help you find places to focus your manual testing.
  22. [garcialo] Also; nominating @deathbear for best handle.
  23. zakim-robot
    @zakim-robot
    May 08 17:22
    [deathbear] lol
  24. [deathbear] This question came to me from a coworker’s friend who just got a job as a QA tester. I’ve been going back and forth about what exactly they needed to do
  25. [tink] That's a really good suggestion @garcialo. Also +1 on @deathbear as cool nick :)
  26. [deathbear] and it seems like they just want to check focus order for menu navigation.
  27. [deathbear] which is like… that’s a thing you can do. You don’t need text output from a screen reader for that
  28. [deathbear] btw I want to thank yall for being really helpful every time I ask a question in here. I truly appreciate it
  29. [tink] NP it's what this place is for :)
  30. zakim-robot
    @zakim-robot
    May 08 18:15
    [garcialo] I’m just here to make snarky comments.
  31. [michiel] Snarky comments with love.
  32. zakim-robot
    @zakim-robot
    May 08 18:28
    [garcialo] Only snarky love will do
  33. Michael Fairchild
    @mfairchild365
    May 08 19:00
    Doing some research around css display:table. My understanding is that it should not surface table semantics to screen readers, but I found this which says that might not always be the case http://www.456bereastreet.com/archive/201110/using_displaytable_has_semantic_effects_in_some_screen_readers/
  34. zakim-robot
    @zakim-robot
    May 08 19:01
  35. Michael Fairchild
    @mfairchild365
    May 08 19:01
    does anyone know if that is still a problem?
  36. zakim-robot
    @zakim-robot
    May 08 19:01
    [dylanb] There is a list of related products here https://github.com/dequelabs/axe-core/blob/develop/doc/projects.md
  37. [deathbear] oo nice. Thanks @dylanb
  38. zakim-robot
    @zakim-robot
    May 08 19:27
    [pstonier] What’s the precedent for headers in asides? No headers? Start at h1?
  39. zakim-robot
    @zakim-robot
    May 08 20:03
    [johnbhartley] @pstonier you would want to use a header structure that makes sense in your current structure. So if your page is h1 "How to Bake a Pie" an aside with "Ingredients" makes sense as an h2.
  40. [johnbhartley] all h2s support the h1, all h3s would support their respective h2s and so on
  41. [tink] +1 - The <aside> is complementary to the main content, so should slot into the main heading structure.
  42. [pstonier] Got it. Thanks, @johnbhartley and @tink