Showing ideas with label accessibility.
Show all ideas
Status:
New Ideas
Submitted on
Aug 30, 2023
06:28 AM
Submitted by
Drew_Nemer
on
Aug 30, 2023
06:28 AM

What is the proposed idea/solution? Instead of having the open or expanded records in the Interface being a top-to-bottom endless scoll, I would like to be able to pages or have the sections be flip to side-by-side How does is solve the user problems? Sometimes the top-to-bottom scroll is not user friendly, having separation of sections into clickable pages in expanded records can make it cleaner How was this validated? Just use existing Sections and make them side by side Who is the target audience? ...
... View more
Submitted on
Mar 01, 2019
08:10 AM
Submitted by
Michelle_Tuten
on
Mar 01, 2019
08:10 AM

Good morning, I did an accessibility test of a form that I built through AirTable and found the following issues that I would like to suggest that you repair. I would like to create a similar form that will be available to the public through our website, but until the accessibility improves, I will not be able to do so. Checkbox box and other input field borders need stronger color contrast. Linked text need stronger color contrast. Markers indicating the Required status of questions do not have strong enough color contrast. Checkbox field needs a label in order for screen reader users to know what “clickable” means. Single Line Text fields should really have programmatically identified labels for screen reader users. Perhaps the title/question as worded in the form could be used as the label. For mulit-select option with the list format, it would be nice if the checkboxes were programmed to be announced as checkboxes to screen reader users. Also, if these options were truly in a list format, a screen reader user should be able to hear “List with [ # ] list items,” before entering the list. For the single-select option with the list format, it would be nice if the radio buttons were programmed to be announced as radio buttons to screen reader users. Also, if these options were truly in a list format, a screen reader user should be able to hear “List with [ # ] list items,” before entering the list. I would like to request that the form design be double checked to make sure it does not cause a keyboard trap when a screenreader/keyboard users tabs through a page in which the form is embedded. In my quick test, it appeared to me that it does cause a keyboard trap prior to submitting a response. Once a response is submitted, the Add another response button is not accessible to the screenreader/keyboard user, but the user is no longer trapped in the iFrame. When required fields are not filled out, the error message does not have strong enough color contrast. Fields that require a URL allow submissions of non-URL content. I think that adding an error message that appears when the submission does not include http:// is good usability, if not accessibility. The Submit button and " Never submit passwords through Airtable forms. Report abuse." message at the bottom of the form, does not have strong enough color contrast. I did not see where the Report Abuse link was included in the Tab order.
... View more
What is the proposed idea/solution? Add hotkeys/shortcuts that allows quickly jumping between pages of a interface. For example: Keys 1-9 opens the page corresponding to the order of the pages in the top bar. How was this validated? N/A Who is the target audience? People that use advanced/large interfaces.
... View more
Status:
New Ideas
Submitted on
Dec 16, 2022
09:16 PM
Submitted by
Sarah_Ford
on
Dec 16, 2022
09:16 PM

What is the proposed idea/solution? Include interface access on Android phones and permit form creation for any type of phone. Or, making the app available on the Windows store in some capacity for PC users. How does it solve the user problems? This would make experience more consistent across all platforms. Interfaces are extremely helpful for transmitting information and using on site for a job. We can set up on the back end in preproduction a clean interface with information that is constantly changing. But, when only 50% of the freelancers we hire have the same kind of phone, it becomes a hindrance in efficiency. Who is the target audience? Anyone who doesn't have a mac or an iPhone. Google Pixels and Samsungs are becoming more prevalent because of availability and pricing, Airtable needs to step into the PC world with accessibility. It will change the user experience dramatically.
... View more
Status:
New Ideas
Submitted on
May 18, 2023
04:42 PM
Submitted by
reagand
on
May 18, 2023
04:42 PM

What is the proposed idea/solution? Add button/option with the ability to print view/sidesheet/full screen ... How does is solve the user problems? it allows the user to print or download a pdf version of the all information in its current layout in the sidesheet without the cutoffs of trying to print the window. Users can print lists and graphs about that record without leaving the interface. Page designer doesn’t work in the interface and has too many limitations. ... How was this validated? ... Who is the target audience? Interface users. ...
... View more
Status:
New Ideas
Submitted on
May 18, 2023
05:10 PM
Submitted by
RonniEloff_VKDe
on
May 18, 2023
05:10 PM

What is the proposed idea/solution? Accounts with Multiple Workspaces: When a specific Workspace is selected from the left navigation bar Please make the the workspace stay selected when you have Open by you and Show all Types selections picked so when you navigate to and from bases it does not go back to all Workspaces showing For example When leaving a specific base through the Go Home at the top of the left of a base you end up with this . ...
... View more
Status:
New Ideas
Submitted on
Jan 08, 2024
06:14 AM
Submitted by
Kim_Trager1
on
Jan 08, 2024
06:14 AM

What is the proposed idea/solution? Align data seperately in each column for linked fields in table mode. ... How does is solve the user problems? Readability. Text normally is left aligned and numbers right aligned. Currently I make separate tables based on readability. However this makes each column completely undynamic. As soon as there is some data that is longer than the defined with of one of the separate column the whole table is skewed and unreadable. ... How was this validated? accross my +20 page designs that makes everything from invoices to assembly manuals ... Who is the target audience? Everyone who needs printed material in a table format. ...
... View more
Status:
New Ideas
Submitted on
Apr 28, 2023
08:27 AM
Submitted by
BespokeBecca
on
Apr 28, 2023
08:27 AM

What is the problem this is addressing? When using forms, we use linked records to make selections - in our case - a certain product to be used when we build out a quote. Unfortunately, the current setup on the forms is limiting the record name. If a record name is extremely long, its getting cut-off and our estimators and sales are making incorrect selections because they don't know the full product name in the system. We can try to come up with abbreviations for many parts in the product name, but that can also lead to confusion and result in the wrong products being selected during the quoting process, producing an inaccurate quote. What is the proposed idea/solution? There are 3 options we can see that would address this issue. Let the record selection screen go wider based on the record names so they don't get cut off. Let the record selection screen wrap the record names, making the record deeper if needed to show the full name. Have the record selection in the live form actually match how it is displayed in the form builder -- to allow a more detailed view with the photo of the product as pictured. How does is solve the user problems? Any of these solutions/suggestions would allow for more details on a linked record to appear so that the correct record could be selected. While I would hope to have option 3 as the solution with the visual representation being used to make sure we are selecting the correct records, Options 1 and 2 (I would assume) would be easier fixes that could be applied to address the problem. Who is the target audience? Our current audience, in our case, is internal usage for employees to select the correct records to compile quotes and work orders with the correct products. Eventually, if something like option 3 was used, this could be used for order systems that are open to consumers and clients, allowing them to make a selection on what they see when words fail them, allowing a clear selection to the product and allowing for more error proof ordering.
... View more
Submitted on
Mar 23, 2022
09:00 PM
Submitted by
Jake_Hensley
on
Mar 23, 2022
09:00 PM

Hey all! This is my first post in the Airtable community and wanted to share one of my product suggestions after about 6 months of using the product. It would be great if the height of the field names row could be adjusted (and text could wrap), so columns can be made more narrow. For example, I have a checkbox field that takes up a lot of space for the sake of the field name. This would be incredibly useful for fitting more information on the screen at once, and eliminating horizontal scroll on tables with many checkboxes. Current Look: Suggested implementation:
... View more
Submitted on
May 22, 2019
02:30 PM
Submitted by
Aaron_Alberto_G
on
May 22, 2019
02:30 PM

Activate an option to scroll horizontally with the mouse wheel. Useful on table view when having lots of fields.
... View more