The titles in the household editor ask for `your <variable name>` even when there are >1 members in the household

[abhcs]

The title says What is your age? but the inputs ask for multiple ages. The in 2024 phrase repeated beside each box seems unnecessary.

[edited after Max's comment]

[MaxGhenis]

This is due to a generalized question from the text of the variable (not just age). If we want to make this general, we could adjust the question for person-level variables to ask "What are your ages?" (maybe only when the household has multiple members)

[abhcs]

The title does not need to be a question. Instead, we could say

Ages in 2024:

Your age: Your partner's age: ...

Similarly, the employment income section could be modified to

Employment incomes in 2024:

Your income: Your partner's income: ...

The title in the second case could also be Employment incomes for the 2023 tax year:?

The Enter button should say Next because it allows you to move to the next section of the form.

[MaxGhenis]

I think it's conventional to collect this information in the form of questions. For example, our partner MyFriendBen does so.

That said, we are currently inconsistent on this between the household and policy sides.

[anth-volk]

Do we have any sense of what users would prefer? Alternatively, do any of our partners? I mean, if an average user has no preference and equally understands both, I could see it being worthwhile to switch.

[abhcs]

I filled my taxes last week using a web app and was surprised at how smooth my experience was -- they had minimized the work I had to do while collecting information from me. Although our current interface is friendly with questions, we can reduce the burden on the user by asking for all the information on one page:

Year: ____

State: ____

Household details: Name: , Age: , Employment Income: , Self-employment income: , Farm income: ____ (+)

Optional details: ...

The (+) is for adding another member to the household.

[MaxGhenis]

Code for America's tax filing products are also one-to-few questions per screen, and generally use the question approach. They've invested heavily in UX research. I'd be interested in other examples that are also scaleable to the large array of questions we can ask.

We may receive a grant in July that would include a UX research study. I'd suggest we revisit this then.