Re: ATools List - submit form

Hi Hidde,

Thanks for reactions. Reply below.

On 9/13/2019 1:36 PM, Hidde de Vries wrote:
> Hi Shawn,
> 
> Thanks for your email!
> 
>> +1 [strong] for providing separate options for "I don't know" and "Not applicable" (per EOWG telecon today)
> 
> Thanks, an updated version of the page with tthese fields split out is currently on its way to Netlify for deployment,.
> 
>> I think there should be a comment box available all the time, not just when select "Partially".
>> Rationale: Tool submitters might have useful comments they want to include for other options.
> 
> I'm worried that too many comments will make reviewing the list really difficult and make the comparing harder.

Ah, yeah, good point.

> 
> While I agree tool submitters probably have useful comments, I think the ideal for a user is less comments to read through. But that might also be something I can solve in the UI, we can hide it initially or something.

I like that idea -- that comments are hidden by default and users can choose to show individual comments or all comments.

> 
> I'll think about this.
> 
>> Maybe label the box "Comments" or "Additional Information" instead of "Description"?
> 
> My rationale here was that people are describing how the feature is implemented, rather than commenting.

OK!

~Shawn

> 
>> Possibly we could make it optional for other options and required for "Partially" -- although I'm not sure it's worth that complexity. I think OK to be optional for Partially, too.
> 
> Hm, good point… thinking about it… maybe optionally will give most result? I guess we'd rather have people state a tool partially has a feature without comments than not at all?
> 
>> I don't think it's necessary to include the additional text ("You selected partial support. Partial support is better than no support at all! Please describe what your support looks like: “accessible templates are available, but it is really hard to find them.") -- it's not worth the added words *and* we don't want to have to write examples for each!
> 
> I'm trying to make it easy to understand what we want, and give people some direction of what an ideal submission looks like. I _think_ that could be done with one good example that is used across all different features.
> 
> I'll give this some more thought.
> 
>> My 2 cents for now. :-)
> 
> Much appreciated!
> 
> Hidde
>    
>>
>> Best,
>> ~Shawn
>>
>>
> 
>

Received on Friday, 13 September 2019 18:59:34 UTC