-
Notifications
You must be signed in to change notification settings - Fork 9
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
Comments
Similarly, we need to write value mappings for textbox/searchbox: w3c/aria#1720 See discussion for this issue here: #76 (comment) |
@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 But essentially somewhere we need a table like the following. So the work here is (1) verify these mappings (I just copied them from Implicit
|
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: |
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 |
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.
The text was updated successfully, but these errors were encountered: