TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I noted that he said they had both types of elements in the UI, but I didn't see him say that both elements had "next" labels.
Where was that?
On 12 Mar 2012, at 23:23, <Brian -dot- Henderson -at- mitchell1 -dot- com> wrote:
> Here's the problem, though. Craig has said that they actually DO have
> both links and buttons on the same screen (Craig, unless there's a
> really good reason for that, you need to see if you can get that
> changed).
>
> If I were the user, my first instinct would be that both "Nexts" would
> do the same thing. But, I would also have in the back of my mind that
> they might not. That little tiny bit of confusion, I think, warrants
> some sort of acknowledgement. If for no other reason than to indicate to
> your users that you've done it on purpose (and that maybe your design
> team isn't a bunch of nitwits).
>
> -BH
>
> -----Original Message----- From: Phil Snow Leopard
>
> It seems unnecessary to me regardless of whether you have links and
> buttons on the same page. If your audience won't be able to visually
> identify 'Next' on the interface easily, I doubt adding the word
> 'button' or 'hyperlink' is going to do anything to help that.
>
> The only case I can see for including the control word is if there were
> two things on the same screen (one button, one hyperlink) that were both
> labelled 'Next' (in which case, as Fred said, you have deeper problems
> that need sorting out). Otherwise, it's just unnecessary verbiage.
>
> --
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
>
> Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
>
>http://bit.ly/doc-to-help
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as philstokes03 -at- googlemail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
>
> Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
Phil Stokes
ààààààààààààààààà
àààààààààà
ààààààààààààààààààààà
àààààààà
ààààààà
àààààààà 10330
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
