Add explicit value calculations for textbox and searchbox role

[spectranaut]

A textbox has a value according to the spec: A type of input that allows free-form text as its value. But ARIA does not specify how the value is calculated and CORE-AAM does not specify how the implicit value is translated into the accessibility APIs.

Combobox's value is specified and we will probably want to follow the same convention.

Whatever we specify for textbox probably will apply to searchbox as well.

[chlane]

When looking at how a combobox is currently named, it leads to the definition of a button as seen below.

Otherwise, the value of the combobox is represented by its descendant elements and can be determined using the same method used to compute the name of a button from its descendant content.

The button definition doesn't link to https://www.w3.org/TR/accname-1.1/.

Is it reasonable to link to the accname calculation rather than the button definition?

@spectranaut can I work on this one?

[spectranaut]

yeah feel free! I'll put you on as assigned.

I agree is makes more sense to link to the accname calculation.

[chlane]

@spectranaut I decided not to link to the accname calculation since it goes beyond looking at descendant content for a value.

[chlane]

@spectranaut @jnurthen Please look at https://github.com/chlane/aria_calculations_textbox_searchbox_1/commit/fdc7e866edffa0c8038cf58971e5d37874b4979a

[chlane]

@spectranaut can this be closed since PR 1783 was approved?

[pkra]

Re-opening since this looked like an accidental close across forks. #1871 is the local PR, I believe.

[spectranaut]

We are now discussion this issue in accname, in this issue: w3c/accname#200

Maybe we should close this as a duplicate, or leave it open in case someone searches this repo?

[pkra]

Maybe we should close this as a duplicate, or leave it open in case someone searches this repo?

I'd say let's close then. Searching closed issues will surface this.