Archive index

A11y Slackers Gitter Channel Archive 24th of April 2016

What fresh hell is THIS now? - Patrick Lauke
  1. David Storey
    @dstorey
    Apr 24 01:16
    @nathanhammond (via @zakim-robot). I can provide some coloUr on the MS Edge updates
  2. David Storey
    @dstorey
    Apr 24 01:27
    In IE and early versions of MS Edge, the A11y tree was a subset of the DOM tree. Well it was closer to a shrubbery than a tree really. The DOM was the oldest sub-system left in Trident and EdgeHTML, built for a world where web apps didn't exist and most pages were static. The a11y tree required a lot of custom work to support new features, etc. The new model is closely aligned with the display tree, which makes way more sense. For example if something is [hidden] or display: none, it is still in the DOM, just not displayed. Generated Content, and list items etc. are also in the display tree, but not the DOM. Really what you want is for the accessibility tree to be in sync with the display tree so if something is hidden it is also automatically hidden in the a11y tree too. It means it is more in sync, better performance, less custom work to add new features, and it should get new capabilities like generated content. With that underlying work we've started to update all the mapping of elements (and ARIA) to the equivalent UIA constructs from the HTML AAM and Core AAM specs, and the accessible name/description spec too.
  3. David Storey
    @dstorey
    Apr 24 01:36
    As you can imagine, a whole new architecture and updating support for HTML and Aria is a whole ton of work, but we're nearing the light at the end of the tunnel now. UIA and Narrator are also getting a bunch of improvements. For example https://blogs.msdn.microsoft.com/accessibility/2016/04/11/improvements-to-narrator-in-windows-10/
  4. zakim-robot
    @zakim-robot
    Apr 24 05:25
    [nathanhammond] @dstorey: thank you for the color! The part I was missing was that you were just approximating the DOM tree, and not combining that with all of the other metadata (CSS for example) to generate your a11y tree. Moving the handling later in the pipeline would then definitely make it easier.
  5. Michiel Bijl
    @MichielBijl
    Apr 24 12:11
    @sophieschoice, try typing on a French keyboard layout ;)
  6. stevefaulkner
    @stevefaulkner
    Apr 24 13:22
    FYI @dstorey you can reply to someone by their [bracketed] username e.g. @nathanhammond it will get to them in slack (no need to mention zakim
  7. Jon Metz
    @metzessible
    Apr 24 14:11
    Had a very good question posed to me recently about my PDFUA videos. Someone using Adobe Livecycle was having difficulty making their PDFs conform to PDFUA. Had to explain that Livecycle forms are usually out of the scope of ISO 14289. Even the 508 Refresh makes note of this, when it said, "if applicable".
  8. Jon Metz
    @metzessible
    Apr 24 14:13
    It's important to understand that all accessible PDFs are tagged PDF, but not all tagged PDF are accessible.
  9. Jon Metz
    @metzessible
    Apr 24 14:15
    I sincerely hope that they didn't have a policy requirement that all their PDFs conform to PDFUA.
  10. sophieschoice
    @sophieschoice
    Apr 24 14:56
    @MichielBijl yeah, I know... But I just started a new job, at the Provincie Antwerpen. Administration mainly and nothing webdesign/usability/accessibility at all, but I do hope to become an advocate for it there in time. It's great, but with working in Belgium comes working with azerty-keyboards.... and I am very used to qwerty.
  11. Michiel Bijl
    @MichielBijl
    Apr 24 15:36
    Can't you just get a Mac (and all the benefits it's keyboard/OS has in regards to multilingual input.
  12. sophieschoice
    @sophieschoice
    Apr 24 15:37
    I do have a Mac, but for work I got a Dell laptop...
  13. sophieschoice
    @sophieschoice
    Apr 24 15:38
    I could ask for an 'upgrade', though :P
  14. Michiel Bijl
    @MichielBijl
    Apr 24 19:18
    Would make things easier/
  15. zakim-robot
    @zakim-robot
    Apr 24 22:01
    [fstorr] Does anyone know of a list of application shortcuts/commands for MS Office and Windows Speech Recognition? For example, in Word you can say “click bullets” for an unordered list and “click numbering” for an ordered list. But getting that info seems to be reliant on hovering over the button to get the command name, which is less than optimal. Not having to rely on mouse grids for everything would be beneficial. Thanks :)
  16. zakim-robot
    @zakim-robot
    Apr 24 22:24
    [sotojuan] Hey guys, I am writing a research paper on web accessibility but focusing on the conflicts/conversation/points of tension between accessbility advocates (us!) and the industry in general. Can you guys point me to some resources or people I can contact?
  17. zakim-robot
    @zakim-robot
    Apr 24 22:24
    [sotojuan] oh and /s/guys/friends, sorry
  18. Jon Metz
    @metzessible
    Apr 24 23:53
    [sotojaun] which industry?
  19. Jon Metz
    @metzessible
    Apr 24 23:54
    @stevefaulkner tried the brackets thing, and it isn't working. Can people using zakim see the 'at' symbol?