DIAGRAM F2F Developer Minutes 03.01.2019
Developers WG Recap – We talked about ideas for the next year or so and got some great ideas. Neil took notes on and we will flesh out. We put together some interest on working on those over a series of calls over the next year to do prototyping or trying to identify the gaps so those are well understood for other groups to proceed on iteration.
Potential tools to do in final year:
Doug: detail ARIA and SVG interactions because of recent regressions
- Need to detail what should and write tests
Jesse: Need what should happen with content editable.
- Define capabilities and shortcomings
- Can provide examples – eg, reading vs writing
- Maybe get some funding from Facebook for NVDA development/implementation of what happens
Mike: What can we do about Open SCAD (3D printing) to make it work with braille displays:
- What can be done to make the tools accessible
Evan: Poet doesn’t have a way to make image descriptions accessibile (“enhanced visual descriptions”)
- Working on their own, but can contribute to open source
John: beyond text, do we know what works and what doesn’t work?
Sina: ASSETS publishes some studies. Apple probably does but doesn’t publish.
John: diagrams are a problem. No standard about screen readers do with SVG.
Sina: Probably not in tools domain
Sina: Some work done on making SVG maps accessible. Should we look at that?
Jesse: Another idea… Swedish keyboards map important keys (@ and other keys are remapped – can be problems during login)
Doug: I looked and four years ago, there was no way to say I really want this keyboard mapping.
Sina: differences between aria-label and what you want something different for braille (e.g., an abbreviation). There is a github issue on it and members of the group and comment on that and poke holes in it.
Neil: aria-live doesn’t deal with braille well. E.g, math because it has separate braille code.
Sina: make sure the full calculation (e.g, accessible name calculation pre-aria-live calculation). Could follow same rules as aria-label.
Evan: Music and chemistry are other non-text examples.
Doug: I’d join a call to coordinate accessible data visualization group to get accessible output.
Jason (DCMP): Not developer, but could get some of my developers to work on things
Evan: I’d be willing to be on calls about image description and contenteditable.
Jesse: a could chance we (Facebook) will be an open source keymap registration (deal with switched language mappings).
Content Editable
- Attribute DOM element
- Allows that div to get keyboard editable cursor etc.
- Move around document, bold/italic etc.
- Reading/writing mode simultaneous
- Would edit html live and could re
render the content
- created
- Draft JS (rich wisiwig editing) Jupyter NoteBook
Sina to test with AT What are the A11y issues Popular editors VS Code Keyboard Mapping Guide the implementing come up with some cases Evaluation of those cases Keymapping.js (express one keyboard mapping)
- Multiple disabilities
- Blind, wheelchair
- Switch based input (short/long presses)
- 4 words / min typing
- Could get him up to 20 - 30 wpm
- T9 (texting 2009 )
- Split keyboard 0
- 6 then 7
- 9 *0#
- 360 multiple
- audio source how to expose this to the User
- Stereo audio.
- BiNeural audio positioning 3D Audio / video overlays
- ASL over AR
- Smart Headphones IMU (as you turn your head will give a 3D audio experience)
- Avatar to help convey visual information
DIAGRAM Center Website http://diagramcenter.org