James Craig

> everything I read classifies full keyboard access as an accessibility feature Presumably this mention is referring to FKA in a specific context, such as iOS? There’s nothing about the...

> Yes. Is there something about other AT that prohibits its use by people without disabilities? No, but since the AT for severe disabilities is optimized for those with a...

Thanks @domenic for attending today. Rehashing the key points as I recall them while still fresh. We didn't come around to a specific path forward on whether something like CloseWatcher...

We should keep the longer name for clarity. No modern DOM APIs use an abbreviated name. Even long names like `document.getElementsBySelector()` are usually just aliased in frameworks, e.g. `$()`

**Keep as-is** - autocomplete - busy (busy has utility outside the context of live regions) - checked - colspan - current - disabled - errormessage (rename or work into error/announcement...

**Consider keeping but with a better name in AOM. Values (including valuetext) might also be combined into a better accessible value API** - valuemax -> max - valuemin -> min...

**Any deprecated properties should not be included. Currently that list is:** - dropeffect - grabbed

**relationship attrs should use object reference arrays** - activedescendant -> `Node focusProxy`? (needs a better name) - controls -> `Array controlsEements[]` (also needs a better name b/c people think of...

**live regions should be superseded by a better announcement API** - atomic - live - relevant

**collections should be superseded by better data provider API as a native Web Platform API or a non-declarative accessibility-specific JavaScript API** - colcount - colindex - rowcount - rowindex -...