Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mapping for combobox, textbox and searchbox value #70

Open
joanmarie opened this issue Apr 16, 2020 · 3 comments
Open

Add mapping for combobox, textbox and searchbox value #70

joanmarie opened this issue Apr 16, 2020 · 3 comments
Assignees
Milestone

Comments

@joanmarie
Copy link
Contributor

w3c/aria#1225 added a normative requirement for user agents to expose a value for comboboxes. We need to add a mapping to state where this value should be exposed for each platform.

@jnurthen jnurthen added this to the 1.2 milestone Apr 23, 2020
@spectranaut
Copy link
Contributor

spectranaut commented Apr 12, 2022

Similarly, we need to write value mappings for textbox/searchbox: w3c/aria#1720

See discussion for this issue here: #76 (comment)

@spectranaut spectranaut changed the title Add mapping for combobox value Add mapping for combobox, textbox and searchbox value Apr 14, 2022
@jnurthen jnurthen removed the agenda label May 3, 2022
@spectranaut
Copy link
Contributor

@chlane, the changes reference by Joanie state that the "value" must be exposed to assistive technologies, and specifies how to calculate the value.

In CORE-AAM, we need to add how that value is surfaced in the accessibility APIs. I'm not sure exactly where we should put this section. It might make sense to make a new entries under "sates and properties" (https://w3c.github.io/core-aam/#mapping_state-property_table) with "implicit value attribute for combobox, searchbox and textbox" -- but because every other attribute in that list is an /explicit/ aria- attribute, I'm not sure it belongs there. Maybe it's own separate section immediately following? Maybe it belongs under Special Processing Requiring Additional Calculation

But essentially somewhere we need a table like the following. So the work here is (1) verify these mappings (I just copied them from aria-valuetext) and (2) decide where to put it in core-aam.

Implicit value attribute for combobox, searchbox and textbox

API mapping
MSAA + IAccessible2 Method: IAccessible::get_accValue(): , Object Attribute: valuetext:
UIA Property: Value.Value:
ATK/AT-SPI Object Attribute: valuetext:
AX API Property: AXValueDescription:

@spectranaut
Copy link
Contributor

I realized that it's possible this definition belong in the "role" definition, not the attribute section, for example, some roles include which interfaces should be exposed: https://w3c.github.io/core-aam/#role-map-meter

@spectranaut spectranaut self-assigned this Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants