Utilizing Wave to confirm accessibility. Title at top of form should be formatted as H1 so that assistive screen readers recognize as a title, pre-heading.
We hope this is a simple html fix that would help many users.
Sign in to see the current vote count, add your own vote, or leave a comment.
Agree with this. Many smartsheet forms are not fully passing accessibility checks because of the lack of H1 for titles. Accessibility best practice dictates that heading hierarchy is important for screenreader users.
I work in higher education in web content. I don't like to link to smartsheet forms for the above reason. I tell my internal folks to use some other secure and accessible form until this fix happens. Please make this happen or you will lose many higher education clients.
Any idea if this has been incorporated? I still see the Heading as H2. I really hope they make it accessible for screenreader users!
Problem Smartsheet environments quickly become cluttered with inactive Sheets, Reports, and Dashboards that are no longer viewed or updated. This creates confusion for users and significant overhead for admins, especially in large or regulated environments. There is currently no native way to automatically identify, notify…
It would be beneficial to be able to leverage Smartsheet Automations to make REST API calls. This has many potential use cases, but one I could see is adding users to Smartsheet groups when the are added to a 'roster sheet' in Smartsheet. It would allow us to use the full power of Smartsheet's API within easy to use…
Hi Smartsheet Team and Community, I would like to raise an urgent enhancement request regarding Data Mesh source sheet configuration. This limitation is causing significant operational issues for teams relying on automated updates through APIs and database integrations. 📌 The Problem When the source sheet connected to a…
