WICG/aom

Issues

• Explainer: WebDriver Extension for Accessible Nodes, etc. (potential solution for #197)

  #203 opened a year ago by cookiecrook
  32

• Read only `window.getComputedStyle()` equivalent for accessible state

  #212 opened 6 months ago by Westbrook
  6

• Reference Target feedback: nesting inside <label> and other implicit relationships

  #209 opened 7 months ago by annevk
  1

• Reference Target feedback: nit

  #208 opened 8 months ago by annevk
  0

• Computing the Accessible Backing Node, or a similar test-only interface

  #197 opened 2 years ago by cookiecrook
  28

• Encapsulation-preserving IDL Element reference attributes

  #195 opened 2 years ago by alice
  10

• RFC: Semantic Delegate "Explainer"

  #199 opened 2 years ago by alice
  0

• ARIA element reflection across non-descendant/ancestor shadow roots

  #192 opened 3 years ago by nolanlawson
  28

• Content attribute to import/export IDs across shadow boundaries

  #169 opened 4 years ago by rniwa
  36

• Shadow inputs in Form-Associated Custom Elements should be allowed to be hidden from AOM

  #196 opened 2 years ago by bennypowers
  0

• Confirmation of Action: (ariaNotify) general feedback for consideration

  #187 opened 3 years ago by travisleithead
  7

• getComputedAccessibleNode() doesn't expose any enumerable property

  #122 opened 2 years ago by liambutler
  2

• Remove ARIA reflection spec in this repo and point to ARIA editor's draft

  #194 opened 3 years ago by mrego
  0

• Confirmation of Action: notification API should be available on elements too

  #180 opened 3 years ago by travisleithead
  1

• IDL element references attributes names

  #191 opened 3 years ago by mrego
  1

• update caniuse

  #190 opened 3 years ago by jnurthen
  0

• AOM and controlling screen reader

  #186 opened 3 years ago by khsbory
  1

• Thoughts on/review of CloseWatcher proposal and relation to synthesized events

  #184 opened 3 years ago by domenic
  8

• Should getComputedAccessibleNode() take a node, instead of an element?

  #185 opened 3 years ago by aleventhal
  4

• Clarification of purpose of synthesized keyboard events

  #183 opened 3 years ago by jaragunde
  0

• Assistive tech : screenreader speech events?

  #125 opened 6 years ago by brennanyoung
  2

• Using serialised AOM as snapshot for UI testing

  #182 opened 3 years ago by arestov
  2

• Are there any plans to create mappings similar to those in MathML-AAM?

  #171 opened 4 years ago by kevinbarabash
  0

• report associated pointerId for a selectionchange

  #170 opened 4 years ago by rektide
  0

• Consider user action event for multi-select

  #167 opened 4 years ago by cookiecrook
  2

• Add user action event for expand/collapse on a treeitem

  #166 opened 4 years ago by jnurthen
  2

• Element activation and synthesized events

  #168 opened 4 years ago by chrisosaurus
  2

• Ambiguity of which key events to synthesize

  #142 opened 6 years ago by cookiecrook
  3

• Can I Use page is out of date for Chrome

  #159 opened 5 years ago by clottman
  1

• Spec source file uses "section autolinks" incorrectly, they'll start breaking

  #158 opened 5 years ago by tabatkins
  0

• Support multiple aria-details ids

  #157 opened 5 years ago by aleventhal
  1

• Reflection polyfill guidance

  #156 opened 5 years ago by jonathantneal
  0

• Status check...

  #147 opened 5 years ago by marcoscaceres
  7

• Accessibility Events Status (re: privacy)

  #144 opened 6 years ago by michaelcpuckett
  2

• Phase 1A implementations?

  #141 opened 6 years ago by LJWatson
  1

• Brainstorming space for specifying the accessibility tree

  #143 opened 6 years ago by alice
  8

• Should we expose "accessibility focus" to the web app?

  #116 opened 6 years ago by minorninth
  2

• Support for AOM in assistive technologies

  #139 opened 6 years ago by TechThomas
  4

• Reflection: Delete Editor's Note about placeholder spelling

  #140 opened 6 years ago by carmacleod
  0

• Exposing description in the AccessibleNode

  #138 opened 6 years ago by NickColley
  2

• Would like to use image

  #130 opened 6 years ago by haltersweb
  2

• Would like to author for accessibility and have that affect CSS

  #133 opened 6 years ago by nigelmegitt
  0

• Assistive tech: Control of the language / locale of screen reader output

  #128 opened 6 years ago by ptrin
  0

• Web component semantics

  #127 opened 6 years ago by alice
  14

• Broken link from Phase 3 draft

  #126 opened 6 years ago by brennanyoung
  0

• AccessibleNode should be defined as [SameObject] in webidl

  #121 opened 7 years ago by asurkov
  0

• Notes for March 28 f2f

  #112 opened 7 years ago by alice
  1

• Will it bring more circle dependencies or memory leak issues?

  #113 opened 7 years ago by Jinjiang
  3

• Why the ARIA attribute overrides the AccessibleNode property?

  #114 opened 7 years ago by Jinjiang
  1

• Event listeners on computed tree?

  #108 opened 7 years ago by alice
  0