Archive index

A11y Slackers Gitter Channel Archive 6th of July 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jul 06 00:13
    [ugi] @indrekpaas nope. th, td, tr, tfooter, theader, tbody will all inherit the role. But, if you place another table inside that table without the role, its children will be exposed to screen readers.
  2. zakim-robot
    @zakim-robot
    Jul 06 00:19
    [indrekpaas] @ugi Amazing, thanks!
  3. zakim-robot
    @zakim-robot
    Jul 06 13:13

    [michael_lockrey] It's not as accessible as AccessibilityOz's video player skin - which you can embed with a separate audio description track, there's better colour contrast, etc etc...

    So YouTube is still a bit behind the A11y game...

    The beauty of the AccessibilityOz solution is that it's just a skin, you can still retrofit it over a video hosted on YouTube...
    Quick question: are youtube embeds anno 2017 accessible or are there technical issues? In other words is a custom player still needed?

  4. LauraOU
    @LauraOU
    Jul 06 13:54
    @zakim-robot I have one youtube embed that i can access, except for the first button being unlabelled so screen reader users don't know what the button does. The rest of the controls as usual don't come up until after the user has pressed the unlabelled button.
  5. but those are labelled and accessible
  6. zakim-robot
    @zakim-robot
    Jul 06 15:04
    [michiel] We’ve released a new working draft of the ARIA Authoring Practices: https://www.w3.org/TR/wai-aria-practices/
  7. [michiel] All feedback is welcome on the GitHub repo: https://github.com/w3c/aria-practices/issues/
  8. zakim-robot
    @zakim-robot
    Jul 06 19:44
    [jiatyan] UK GDS is looking for opinions re <h2>error summary<h2> superseding <h1>main heading</h1>. alphagov/govuk_elements#510
  9. zakim-robot
    @zakim-robot
    Jul 06 22:38
    [ted_drake] Hi all, I noticed a lack of channels regarding the deaf community, so I created #deaf
  10. zakim-robot
    @zakim-robot
    Jul 06 22:51

    [tessenate] What’s the best way to implement nested checkboxes? e.g.

    [ ] Parent choice 1   [ ] Subchoice 1   [ ] Subchoice 2   [ ] Subchoice 3 [X] Parent Choice 2   [X] Subchoice 1   [ ] Subchoice 2
    

    Right now we have nested fieldsets (which I know is wrong, but easiest to implement with our current component architecture).