Closed ninavizz closed 2 years ago
(moving what had been the item's main text to a comment, so this can become and be tracked as an Epic)
...perhaps a team meeting to discuss & solicit more ideas from all, in the weeks ahead?
To facilitate easier discovery of information/functionality for users; ensure actions, messaging, and instructive bits are all in the correct spots
For forthcoming user testing, note ideas in main SD repo labeled Goal: Improve Source Experience.
Discussed these things in UX Meeting 25 Apr & 02 May: https://docs.google.com/document/d/1toZmKi1Oyjy7UTXyj_U7lI3IPV8stQtjVhHVlWL5Ils/edit?usp=sharing
Then, Erik made this awesome draft: https://docs.google.com/document/d/1ft71JmAV8ZnNgqIprKvGW8v8BRCwQuj89QiOFTwC1uY/edit?usp=sharing
<alt>
tag textTBD
come and offer some! :)
Closing, as 2021's SI Redesign meets the majority of these needs—and the lone need it does not meet the need for, I will be creating a separate ticket for.
Goals
This issue is for near-term updates to do to the Source Experience, in advance of a larger project to re-think the complete Source journey. Each checkbox item below, is described in comment(s) below and to be tackled in subordinate tickets.
No Testing Needed (so, ASAdevP)
These recommendations are made either from existing/known issues, or standard ux best practices
Global
<alt>
text edit<alt>
tag sayingSecureDrop
on a newsroom's logo adds to the confusionalt
tag, seconds before an image appears; and makes this a more notable/significant UI element than on standard web pages. See 0:20 and 0:30 in this video screencast of AlJazeera's SecureDrop loading w/in Tor.<alt>
tag should just beLogo
.<alt>
tag should inclide the name of the newsroom, such asNew York Times Logo
H1
and has no container for where messages wd live if they existed.bottom-border
orbackground-color
on aninline-block
attributes vs standard HTML<a>
underline.hr
Submit Page
Get Codename, Index, Journalist footer
After User Testing Validation