Archive index

A11y Slackers Gitter Channel Archive 3rd of July 2017

What fresh hell is THIS now? - Patrick Lauke
  1. zakim-robot
    @zakim-robot
    Jul 03 07:44
    [sri429] any accessible date-time picker controls ?
  2. [sri429] saw a bunch of datepicker but not date time picker
  3. zakim-robot
    @zakim-robot
    Jul 03 08:20
    [iandevlin] Morning all! Quick question, is it recommended to still add role="main" to <main>?
  4. Mallory
    @StommePoes
    Jul 03 12:30
    Only if you're supporting old IEs etc
  5. Otherwise, everyone who knows main isn't Some J Random Block knows it's got a main role
  6. Mallory
    @StommePoes
    Jul 03 12:47
    @iandevlin
  7. zakim-robot
    @zakim-robot
    Jul 03 12:48
    [iandevlin] Which old IEs?
  8. [iandevlin] (and thanks for replying)
  9. zakim-robot
    @zakim-robot
    Jul 03 12:54
    [scottohara] all the old IEs :) edge is cool. take a look here: http://www.html5accessibility.com/
  10. zakim-robot
    @zakim-robot
    Jul 03 13:06
    [iandevlin] @scottohara Ah yes, forgot about that. Thanks!
  11. zakim-robot
    @zakim-robot
    Jul 03 14:03
    [tink] For any developers here... would welcome your comments on this HTML proposal w3c/html#957
  12. [tink] Please comment on the thread itself if you can - it's good to keep the conversation inclusive :)
  13. zakim-robot
    @zakim-robot
    Jul 03 15:29
    [karlgroves] New Blog post
    Extreme Accessibility: Rapid Discovery and Remediation, Part 1: http://blog.tenon.io/extreme-accessibility-rapid-discovery-and-remediation-part-1/
  14. zakim-robot
    @zakim-robot
    Jul 03 16:58
    [sri429] Bump Q: any accessible date-time picker controls ?
  15. zakim-robot
    @zakim-robot
    Jul 03 17:31
    [geekf] @sri429 Have a look at https://github.com/mdehoog/Semantic-UI-Calendar. I haven't tested it from A11y point but keyboard controls work great on it.
  16. zakim-robot
    @zakim-robot
    Jul 03 21:52

    [bbuechel] Given a radio button group (say 4 radio buttons), would having one radio button disabled (disabled=“disabled”) so that the option is visible but not selectable cause any issues for screen readers?

    Testing has shown disabling a radio button prevents normal keyboard navigation from focusing on the disabled one. However, at least with VO and Safari, focusing on the other radio buttons acknowledge the total count in the radio grouping including the disabled one. (ie: 1 of 4…but #4 is disabled so you can’t actually get to it with normal keyboard navigation arrows/tab). Switching out of form mode you can “find” the disabled element and are alerted its label and that it is “dimmed”. This feels clunky.

    Are there more elegant ways of displaying disabled form controls that are also accessible?