Archive index

A11y Slackers Gitter Channel Archive 30th of May 2016

What fresh hell is THIS now? - Patrick Lauke
  1. Job van Achterberg
    @jkva
    May 30 07:35
    Morning slackers
  2. Job van Achterberg
    @jkva
    May 30 08:40
    For the Dutch-speaking slackers: Hopefully 9292 will finally fix their outline issues, but I'm not holding my breath https://twitter.com/detonite/status/737192688412397568
  3. "We'll send this to the developers", let's hope for something else than "Resolved won't fix"
  4. Job van Achterberg
    @jkva
    May 30 10:48
    tap tap is this thing on?
  5. Mallory
    @StommePoes
    May 30 10:52
    yesh
  6. Job van Achterberg
    @jkva
    May 30 10:53
    Quiet day then
  7. zakim-robot
    @zakim-robot
    May 30 11:23
    [michiel] Morning
  8. Job van Achterberg
    @jkva
    May 30 11:24
    o/
  9. zakim-robot
    @zakim-robot
    May 30 14:45
    [jitendra] Are these kind of custom code ok for screen readers? Found in an angualr.js app? https://scrnshot.s3.amazonaws.com/n2w2n.jpg cc: @marcysutton
  10. zakim-robot
    @zakim-robot
    May 30 15:07
    [karlgroves] Have you tested it with a screen reader? If so, which one(s)?
  11. zakim-robot
    @zakim-robot
    May 30 15:23
    [jitendra] I’m on mac, I m trying to test it with voice over
  12. [karlgroves] You should get a virtual machine with Windows and install NVDA & JAWS as well.
  13. [karlgroves] What do you experience with VoiceOver?
  14. [jitendra] i can reach inside the block by pressing commands
  15. [jitendra] this j-frame is inside a td
  16. zakim-robot
    @zakim-robot
    May 30 16:00
    [karlgroves] As a direct answer to your question: <j-frame> is obviously not a valid element. Invalid elements and attributes by themselves have no inherently bad impact on accessibility. So the next concern is - “What is this thing and what does it do?” What is its name, state, role, and value (NSRV) - or, at least, what does the AT think it is? Does the NSRV imparted by this content make sense in context of its use? If you can interact with it, does the NSRV change appropriately?
  17. [jitendra] Do you mean for screen reader div and j-frame both are same
  18. [jitendra] This is an email web app. which usages Multiple <tbody> inside a <table> for each item in list view.

  19. [karlgroves] > Do you mean for screen reader div and j-frame both are same

    Yup. That’s what the shadow DOM is telling you as well.

  20. [karlgroves] > This is an email web app. which usages Multiple <tbody> inside a <table> for each item in list view.

    Without seeing it, that may make sense. Or may not. Multiple tbody elements certainly don’t make sense but probably not an issue for accessibility.

  21. [jitendra] j-frame in container which renders content of email
  22. zakim-robot
    @zakim-robot
    May 30 16:06
    [karlgroves] Again, how does it perform? What does VO say?
  23. [karlgroves] The markup only matters insofar as how it impacts the user. They could use a <poop> element. It wouldn’t matter at all unless they made the <poop> element do something inaccessible
  24. zakim-robot
    @zakim-robot
    May 30 17:25
    [jitendra] when does using multiple tbody makes sense?
  25. zakim-robot
    @zakim-robot
    May 30 18:26
    [karlgroves] Multiple tbody elements never make sense, IMO.
  26. luis garcia
    @garcialo
    May 30 18:29
    Maybe if you had multiple tables.
  27. James Nurthen
    @jnurthen
    May 30 19:52
    Multiple tbody is allowed though and shouldn't have any accessibility impact other than making checking tools harder to write.
  28. zakim-robot
    @zakim-robot
    May 30 23:32

    [karlgroves] >making checking tools harder to write.

    Man if something like testing multiple tbody elements is hard I’d hate to see what else is challenging

  29. James Nurthen
    @jnurthen
    May 30 23:50
    Just another corner case to remember about.