Ability to add custom design/styling to custom forms and request queues (i.e. font size, font weight, color, etc), also support WCAG 2.1 AA compliance

[#1]

Description:

I'd like the ability to have a little bit of control over the look and feel of custom forms, particularly how they are displayed when used as a request queue. Ideally we'd be able to adjust font size, font weight, color, bolding, etc.  Even if we could apply a default font-size for the form, and selectively bold some text, that would be a huge improvement. 

Additionally, a complaint I've received multiple times is that the font size for a question is smaller than the font size for an option within that question.  If we could change the font size we could fix this ourselves. Or, if it's easier, make the question font-size match that of the options below it.  Example:

Why is this feature important to you -
There are new rules that go into effect in April 2026 around accessibility of internal and external documents for Government agencies. All documents must be WCAG 2.1 AA complaint. Depending on your reading of the guidelines the current request queue forms may not be in compliance.  More information here:  https://www.ada.gov/resources/2024-03-08-web-rule/

How would you like the feature to work -
I can think of a few different ways to address this:

1.) Allow admins to set a default font size for request queue forms and be able to selectively bold descriptive text in forms.

2.) Give us complete control over the font size, color, etc, on a per-question basis.

3.) As a stopgap, increase the font-size of the question label to match that of the options below it, and ensure request queue forms meet all other WCAG 2.1 AA guidelines.  

Current Behaviour:
We have no control over the design of custom form/request queue design, and current request queue forms may not be WCAG 2.1 AA compliant.

[#2]

I echo everyone's comments. Our organization would benefit from a "descriptive text" field like Dustin says, but what's more beneficial and necessary for our company is having rich text abilities for the end user to edit the "answers" in the field.

We currently have to rely on email and/or word docs to convey and communicate necessary information that we can't format well in custom forms.

Having a separate rich text paragraph field is not beneficial and would cause more work to rebuild all of our custom forms and it would break our reports/data. It would actually be a bit of a nightmare and almost not worth doing.

It would be amazing to have that rich text formatting applied to all existing text fields.

[#3]

Echoing the previous comments, as-is this feature has very limited benefits. Workfront needs to figure out a way to make it possible to add this feature to existing text fields. We have hundreds of existing text fields and we will certainly not mess around trying to replace them with new fields just to get rich text. Good start, but more work is needed on this.

[#4]

I see you mention this is a phase 1 but I want to add to the general thoughts others have expressed as well.

1. The fact that it is a NEW field is just plain unhelpful. I am never going to update all my fields in my forms to this.
2. Bold, Underline and Italic is not enough. Numbering, aligning, tables, etc. As others here have mentioned.

Not sure what later phases were planning, but this feature has a long way to go. thank you!

[#5]

I guess this will be another very similar comment. It is good to see bold, italic and underline are there, but other things like bulleting, numbering, tables, its also needed.

[#6]

Since I upvoted this one, I'll pipe-in. I haven't had a chance to go to Preview and test (just watched video), but it looks like others have done quite the good job at that already. :)

1. The feature I was looking for was not an RTF field for users to fill-out (though that is cool and a nice-to-have).
2. If this "RTF field" means creating a new field, it's worthless for any existing form, which is a shame. The level of effort to put in a new field, swap out the old one, and the logistics of moving the data in the process makes it non-viable. Someone should make this swap-n-place, simply an option toggle for any text field.
3. What I wanted was the ability to go big/small/bold/italic/etc. for the static parts of custom forms. Right now only form name, section name, and mandatory fields have any style (bold, slightly bigger and bold-orange, etc.). But what if I want to organize differently? Or make a particular question in red? Or emphasize certain words in Descriptive Text fields? Or want section headers to be styled per our corporate guidelines?

So I guess this means I'll need to get back into Idea Exchange and start the process over for what I thought this was going to be. *shrug*

Cool on the RTF for user fill-out portions though; something I can keep in mind in the future. But please implement #2 above or those of us with pre-existing forms are going be rather non-plussed and just have to turn around and ask for yet another Idea to make this an option for ALL text fields, not it's own type.

[#7]

I wanted to chime in to add my feedback that this is not what I was looking for. Workfront needs to figure out a way to make it possible to add this feature to existing text fields. There are MANY existing text fields and I don't have the time/staff to replace them with new fields just to get rich text.

[#8]

I agree with comments made by others. I was really hoping that this new feature would allow administrators to bold, underline or italicize text on the form itself rather than allowing end users to apply formatting to their answers. The issue for us is that we really need a way to call attention to the submitter and provide guidance on what we are expecting them to enter in the text fields. And ideally this could be done by updating the existing fields rather than having to create new ones.

Hopefully we will see this in future phases.

[#9]

Ditto to many of the comments so far, this is not what I voted for so really quite disappointing. The formatting of custom forms is an area Workfront as a tool really let's itself down. It's one of the main aspects I receive complaints about from our users who find the custom forms crude and difficult to read / work with. Some simple formatting functionality is long overdue and this doesn't really address this.

[#10]

Thanks for this clarification, Jeremy! Very helpful. Please reach out when you are looking for feedback as you develop the new capabilities.

[#11]

Will do, Alyssa — thanks!