When no name and extra info is set, it would still add a space. is_empty() would never be true. The space character would be set as label and screen readers are prompted to read it with various output. Fixed by stripping spaces.
This will allow decoupling `display_server.h` from a number of headers in the
codebase which only require those enums and not all the DisplayServer API.
Adds ROLE_REGION to allow controls to be marked as accessibility
regions/landmarks.
- Add `accessibility_region` property to Control
- Add ROLE_REGION to DisplayServer and AccessKit mapping
- Prevent Container/ScrollContainer from overriding region role
- Fix TabContainer to update accessibility when tabs change
- Mark editor docks, main screen, bottom panel, and scene tabs as regions
When TabContainer calls accessibility_update_add_related_controls(), it
triggers _ensure_node() which creates a new AccessKit node. Since the
node pointer was nulled after the previous tree update push, this creates
an empty node without any properties.
TabBar only sets tab properties (name, bounds) when accessibility_item_dirty
is true. After initial setup, dirty=false, so recreated nodes would be
pushed without names, causing screen readers to announce "page tab" without
the tab name.
This fix re-applies the stored name (and name_extra_info) when _ensure_node
creates a new node, ensuring tab names persist across node recreations.
Two fixes for text field accessibility:
1. Fix character count being off by one due to trailing newline always
being appended to the last line. Add `is_last_line` parameter to
`accessibility_create_sub_text_edit_elements()` to control this.
2. Link adjacent TextRuns via `previous_on_line`/`next_on_line` so
screen readers can properly navigate lines. Without these links,
AccessKit treats each TextRun as a separate line, causing incorrect
announcements when arrowing through multi-line text.
