Re: how to do newlines and how to submit when editing text

I think if I were to try to enunciate a rule it would be:

fields in which it is expected that one should write something comprising
multiple paragraphs, thus more like a document, then enter should create a
new line.
fields in which the text is assumed usually to be short one line comment
then you do ctrl + enter.

Problem with this is it puts a bit of work on people to cognitively realize
what they are working with, document or short line, and that this might
also be less easy for someone to determine if they are visually impaired.

I know I've been hit a few times with enter not being enter in stuff I
think it should be, like LinkedIn comments. I just find it sort of
irritating and was thinking it would be nice to have some guidelines so was
thinking to write an article about it, but was unsure if there already was
something written somewhere in some standard or working group document I
was unaware of.

Thanks,
Bryan Rasmussen

On Sun, Apr 12, 2026 at 8:07 PM bryan rasmussen <rasmussen.bryan@gmail.com>
wrote:

> I just happened to be reading Hacker News and saw this:
> "In text boxes in some applications, enter submits the entered text, and
> ctrl-enter forces a newline (not at my computer, but I think Slack does
> this). In others, it's the other way around"
>
> and thought that stuff has caught me before, I seem to remember there is
> some guideline on pressing enter should submit, but is there a guideline in
> any accessibility standard on how the user should be able to do a new line
> in entering text - and if so which standard is that in?
>
> Thanks,
> Bryan Rasmussen
>