Archive index

A11y Slackers Gitter Channel Archive 11th of August 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Aug 11 00:44
    [backwardok] is hovering with a mouse while using nvda common (or at least common enough that it should work properly)? trying to gauge whether or not this is just behavior that someone who’s testing would do vs. someone actually using the product would do
  2. zakim-robot
    @zakim-robot
    Aug 11 03:39
    [nschonni] hmm, according to the Facebook photos, i'm the Looper of Gareth Ford. Come to the next CSUN if you want to see what happens when timelines collide
  3. zakim-robot
    @zakim-robot
    Aug 11 13:36
    [quidkid] hey so for a PDF remediation report, they said our fonts weren’t embedded. but after sending a print screen of the embedded fonts, they said we had to add a space after one of our headings. I’m really confused as to how adding a space would affect anything at all accessibility wise. Looking for any insights
  4. [tink] @quidkid I've come across PDFs where a screen reader runs one bit of content into another, so onewordandanother for example.
  5. [tink] Usually that's down to incorrect tagging though. But it's the only thing I can think of gien your description.
  6. zakim-robot
    @zakim-robot
    Aug 11 13:46
    [quidkid] @tink thank you for your response! I was thinking maybe it was a bug in their automated testing system. They said not having a space generates a red flag
  7. [tink] Interesting. So they're suggesting the PDF equivalent of <h1>Some text </h1> instead of <h1>Some text</h1>?
  8. [quidkid] yeah so they fixed it in our web version and they wanted us to fix our print pdf version. and I’m not sure why if they fixed it in the web version they couldn’t do it in the print version. and the only difference we saw was the addition of some times new roman space after our font
  9. [quidkid] so we just did the same in our print version and send it back. not entirely sure if that’s what they wanted especially given I’d imagine they could’ve done that fix themselves too
  10. [tink] I can't figure out why it'd be needed at all in any version, but then PDF a11y isn't my strong suit.
  11. [quidkid] ^my point exactly. of all things to point out for accessibility they didn’t even mention the contrast issues..
  12. [quidkid] i’m not quite sure i trust that accessibilty vendor but it’s the one the client went with and so we are kinda at their mercy
  13. [tink] That happens sometimes :(
  14. zakim-robot
    @zakim-robot
    Aug 11 14:34
    [jv] Do we need to test designs in B&W?
    Is there any eye problem which show everything B&W?
  15. [kivi] Achromatopsia https://aapos.org/terms/conditions/10
  16. zakim-robot
    @zakim-robot
    Aug 11 14:44
    [jv] Is there any website which has data of number of people having a particular disability in the world?
  17. [donnabungard] Achromatopsia affects an estimated 1 in 30,000 people worldwide.
  18. [donnabungard] https://ghr.nlm.nih.gov/condition/achromatopsia#statistics
  19. zakim-robot
    @zakim-robot
    Aug 11 18:08
    [donnabungard] @jv ^