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!
Can someone confirm this? I received a Smartsheet form from a client and it looks there there is a H1 tag in the forms now … is this an accurate assessment? I do see, though, the title of the form got flagged by WAVE as a "possible heading" because it was not in the H1 element. I do not actively work in Smartsheet so if it's something the client needs to do to fix this, let me know. Thank you!
We need the ability to duplicate (copy) an existing dynamic view to other sheets. We use templates and Smartsheet Control center, but when creating a new sheet (using SCC or Save As New) the dynamic view(s) are not also copied/duplicated. This creates a LOT of manual re-work. It'd be great if, from the Dynamic View…
I'm proposing an added feature to CANCEL an update request without necessarily deleting it, this way we can maintain the history of requests even when they aren't acted upon by the recipient. Sometimes users elect to update rows in grid view rather than from their emails/notifications, or they'll respond to the 20th update…
Currently, browser search (Ctrl+F) in Smartsheet dynamic and timeline views only works on records that are visible on the screen. Because these views use virtualized rendering, users cannot search across the full dataset without manually scrolling. This creates inefficiencies when working with large sheets, increases the…
