See the parent issue #8205 for more information about the general problem. This issue is for discussing and agreeing on expected behaviour, and then tracking implementation. Tasks: - [x] Apply the correct [ARIA roles and properties](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques) to the DOM elements that represent the field - [x] Provide [accessible names and descriptions](https://www.w3.org/WAI/ARIA/apg/practices/names-and-descriptions/) to the DOM elements that represent the field - [x] Make sure the field works both during editing and during display (not editing) - [x] Describe the correct keyboard shortcuts to move into and out of editing mode when on a single instance of the field (e.g. enter, space, and esc) - Implementation may happen in the keyboard nav code or repository Resources: - [ARIA: textbox role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/textbox_role) - [Blockly text input field documentation](https://developers.google.com/blockly/guides/create-custom-blocks/fields/built-in-fields/text-input)
See the parent issue #8205 for more information about the general problem.
This issue is for discussing and agreeing on expected behaviour, and then tracking implementation.
Tasks:
Resources: