Tally Forms Improves Keyboard and Screen Reader Accessibility Across Six Fields.

Tally Forms has closed accessibility gaps across six commonly used field types, making its forms easier to complete without a mouse or visual interface. The update improves navigation for keyboard and screen reader users across ranking, time, phone, rating, matrix, and dropdown fields.

The company announced the changes on LinkedIn, describing them as fixes for navigation gaps that created friction when people attempted to fill out forms using assistive technology. Tally’s official changelog groups the accessibility work with its July 14, 2026 update, alongside a redesign of conditional logic.

It is a focused release, but an important one. Form builders often rely on interactive controls that are straightforward with a pointer but harder to operate sequentially with a keyboard. If focus movement is unclear, an option cannot be selected without a mouse, or a screen reader cannot properly interpret a control, respondents may be unable to finish the form at all.

The update applies to several controls that involve more than typing text into a conventional input box:

• Ranking fields, where respondents arrange choices into an order
• Time fields, used to enter or select a time
• Phone fields, which collect telephone numbers
• Rating fields, such as numerical scales
• Matrix fields, which present multiple questions and answer choices in a grid
• Dropdown fields, where respondents select an option from a menu

Tally has not published a field-by-field technical breakdown of the changed interactions. Its announcement specifically says it fixed navigation gaps for keyboard and screen reader users, rather than claiming a new accessibility certification or complete compliance with a particular standard.

That distinction matters. Accessibility is broader than keyboard navigation alone, covering factors such as labels, contrast, error handling, focus visibility, semantic structure, and compatibility across assistive technologies. The latest changes address a meaningful portion of that experience, but form owners should still test their complete forms before publishing them.

For small businesses, accessibility failures can have direct operational consequences. A lead form that cannot be completed by keyboard may lose a prospective customer. An inaccessible registration, application, or feedback survey can exclude respondents and produce less representative data. Since Tally forms are frequently embedded into websites and connected to downstream workflows, a problem at the collection stage can undermine an otherwise well-designed process.

The fixes appear to apply to the respondent experience rather than introducing a new block or setting that creators must enable. Existing forms using the affected field types should therefore be reviewed, particularly longer forms that combine dropdowns, matrices, and rating questions.

Creators can run a basic keyboard test by moving through a published form without touching the mouse, checking whether focus proceeds in a logical order and whether each choice can be selected. Screen reader testing should also confirm that field labels, options, required states, and validation messages are announced clearly. Testing an embedded version is worthwhile too, since the surrounding website can influence focus behavior.

The release fits a broader run of product maintenance and workflow improvements from Tally. The company recently added email notifications for failed integrations, helping creators detect submission delivery problems, and introduced file-based form imports across five formats. Those releases focus on reliability and setup speed; this one concentrates on who can successfully respond.

For builders, the practical takeaway is simple: the platform now offers better navigation across several of its more complex fields, but accessibility still requires deliberate form design and real-world testing.

What is Tally Forms Keyboard and Screen Reader Accessibility?

It is a set of navigation improvements for people who complete Tally forms using a keyboard or screen reader. The update fixes gaps affecting ranking, time, phone, rating, matrix, and dropdown fields.

Which Tally Forms fields were updated?

The announced fixes cover six field types: ranking, time, phone, rating, matrix, and dropdown. Tally has not provided a detailed technical list of every changed keyboard command or screen reader behavior.

Do form creators need to enable the accessibility improvements?

Tally did not announce a new setting or paid-plan requirement for the changes. Creators should still test published and embedded forms with keyboard navigation and, where possible, screen readers to assess the complete respondent experience.