User Experience for News Websites

Making content readable is one of the easiest things you can do to ensure your content is accessible and provides the best reading experience for a diversity of users. Here are the content dos and don'ts in one image. The left side of the image shows what works. The right side of the image shows what does not work. Here's a short explanation for each one. ✅ Text Alignment Full justification is a problem. It adds unpredictable rivers of uneven white space, which adds friction as the eye can get lost with no guidance from the ends of the lines that are in a straight line. Beware centering text with more than two lines adds friction to the reading experience. Even for people without disabilities. It's because the starting point for each line varies. The eyes work harder to find the next line than they do when the starting point is the same. Be thoughtful about centering. ✅ Paragraphs Some content contains long paragraphs or doesn't add a blank line between paragraphs. In some posts on LinkedIn, a user hits "Enter" only once between paragraphs. That looks like this line, the one before this, and the next one. The blank line helps break up the text for easier reading. Doesn't the blank line make a difference? Keep digital paragraphs about two to five sentences long with a blank line in between. ✅ Bold, Italics, Underline It's OK to italicize a word or two for emphasis or to identify titles of books, shows, and publications. They're not meant for entire sentences or paragraphs. Bold is fine for headlines and headings. But some content has an entire sentence or paragraph in bold. I know they're trying to tell the reader, "If you're going to scan this, here's what's important." Except if the reader wants to read more of it, the bolded text can be distracting. I don't have ADHD and my eyes keep gravitating to the bolded text instead of reading what's before and after it. It's like a tug-of-war. The same goes for underlined text. Underlined text can be hard for some people to read. Do use them for links, but try to limit links to a few words that give context rather than a whole sentence if possible. ❎ UPPERCASE Avoid UPPERCASE as much as possible. Use sentence case, title case, and PascalCase for hashtags and user names. (Capitalize the FirstLetterOfEachWord.) Text in all UPPERCASE has no shape. They all show up as a block. Using lowercase adds shape and improves readability. ✅ Font Style Use simple, clean, sans-serif (no curves and embellishes) fonts for the best reading experience. 🔔 Tap the profile bell to get the next post 👉 Follow #MerylMots to catch my content ❤️ Like this? Repost and comment 📧 Subscribe to an occasional email at meryl[.]net/subscribe #DigitalMarketing #ContentMarketing Image: Content Dos and Don'ts with the left side containing examples of what to do and the right side showing examples of what not to do to make content readable. Clearly, I don't have an eye for design!

Design can only be termed good if it reaches all. Creating beautiful and innovative designs is a key goal for graphic designers. However, even the most visually appealing designs can be inaccessible to some users if they don’t consider various accessibility needs. Low contrast between text and gaudy backgrounds can make it difficult for people with visual impairments or colour blindness to read the content. Decorative fonts can be hard to read for everyone, especially for people with dyslexia or other reading disabilities. So, what do we do to make designs more disability inclusive? 🔍 Understand Diverse Needs: Begin with empathy. Get to know the unique needs and challenges faced by people with disabilities. This understanding will guide your design process to be more inclusive. 🖼️ Accessible Visuals: Use high-contrast colors and clear fonts to make text and images easily readable. 🗣️ Alt Text Matters: Provide descriptive alt text for all images to ensure that screen readers can convey the content to visually impaired users, making your designs more inclusive. 🎨 Responsive Design: Design with flexibility by creating layouts that adapt seamlessly across different devices and screen sizes, including those used by people with disabilities. ♿ Universal Symbols: Use universally recognized symbols and icons to communicate important information. 💬 Inclusive Language: Choose words that respect and acknowledge people with disabilities. Avoid ableist language and ensure your message is positive and empowering. 👩💻 User Testing with Disabled Communities:  Involve people with disabilities in your testing process. Their feedback is invaluable in creating designs that truly meet their needs. Embracing disability inclusion in our designs is the next step to making the world a better place. Let me know of more design inclusive strategies in the comments below! #inclusive #design #accessibility #uxdesign #a11y #disabilityinclusion #universaldesign #webaccessibility #empathyindesign #userexperience #designthinking

"🌍 Crafting Inclusive UX Writing for a Global Audience Designing for a global audience transcends mere translation. It requires a deep understanding of cultural nuances, linguistic structures, and user expectations. Here's how UX writers and content designers can create experiences that resonate across diverse markets: 🧭 Key Concepts Translation: Converting text from one language to another. Localization: Adapting content to align with cultural, regional, and linguistic nuances. Internationalization: Designing content and systems to support multiple languages and regions from the outset. 📊 Global User Insights English users constitute approximately 26% of internet users. Top languages online include Chinese, Spanish, Arabic, and Portuguese. User preference leans towards content in their native language. Text length variations: French texts can be 20% longer, while Japanese texts may be 30–60% shorter than their English counterparts. ✅ Best Practices for UX Writers Design for Expansion: Allocate at least 30% additional space to accommodate text expansion in translations. Pseudolocalization: Use this technique to test how your UI handles different languages and scripts. Flexible UI: Ensure your design can handle varying text lengths, directions (LTR and RTL), and character sets. Cultural Sensitivity: Be mindful of colors, symbols, and imagery that may have different connotations across cultures. Inclusive Language: Use gender-neutral terms and avoid idioms or colloquialisms that may not translate well. 🚫 Common Pitfalls to Avoid Flags for Language Selection: Flags represent countries, not languages. Use language names instead. Assuming Name Structures: Not all cultures use first and last names. Opt for a single ""Full Name"" field when possible. Overlooking Context: Provide translators with context to ensure accurate and meaningful translations. 🔍 Deep Dive into Cultural Nuances Arabic Interfaces: Often require increased line spacing for readability. Chinese Users: Prefer dense information layouts. German Audiences: Expect detailed and comprehensive information to establish trust." Read also Designing Cross-Cultural and Multi-Lingual UX ( https://lnkd.in/d-7WFrMF) by Vitaly Friedman

People often say what they think they should say. I had a great exchange with 👋 Brandon Spencer, who highlighted the challenges of using qualitative user research. He suggested that qual responses are helpful, but you have to read between the lines more than you do when watching what they do. People often say what they think they should be saying and do what they naturally would. I agree. Based on my digital experiences, there are several reasons for this behavior. People start with what they know or feel, filtered by their long-term memory. Social bias ↳ People often say what they think they should be saying because they want to present themselves positively, especially in social or evaluative situations. Jakob's Law ↳ Users spend most of their time on other sites, meaning they speak to your site/app like the sites they already know. Resolving these issues in UX research requires a multi-faceted approach that considers what users say (user wants) and what they do (user needs) while accounting for biases and user expectations. Here’s how we tackle these issues: 1. Combine qualitative and quantitative research We use Helio to pull qualitative insights to understand the "why" behind user behavior but validate these insights with quantitative data (e.g., structured behavioral questions). This helps to balance what users say with what they do. 2. Test baselines with your competitors Compare your design with common patterns with which users are familiar. Knowing this information reduces cognitive load and makes it easier for users to interact naturally with your site on common tasks. 3. Allow anonymity  Allow users to provide feedback anonymously to reduce the pressure to present themselves positively. Helio automatically does this while still creating targeted audiences. We also don’t do video. This can lead to more honest and authentic responses. 4. Neutral questioning We frame questions to reduce the likelihood of leading or socially desirable answers. For example, ask open-ended questions that don’t imply a “right” answer. 5. Natural settings Engage with users in their natural environment and devices to observe their real behavior and reduce the influence of social bias. Helio is a remote platform, so people can respond wherever they want. The last thing we have found is that by asking more in-depth questions and increasing participants, you can gain stronger insights by cross-referencing data. → Deeper: When users give expected or socially desirable answers, ask follow-up questions to explore their true thoughts and behaviors. → Wider: Expand your sample size (we test with 100 participants) and keep testing regularly. We gather 10,000 customer answers each month, which helps create a broader and more reliable data set. Achieving a more accurate and complete understanding of user behavior is possible, leading to better design decisions. #productdesign #productdiscovery #userresearch #uxresearch

People Do Read: Busting the Myth The truth about reading habits: From UX studies to digital marketing insights: Realities about how people interact with content: → Scanning First: 79% of users scan a page before reading. Your content must grab attention fast. Visual Appeal Matters: → 70% of people prefer visual content over text. Enhance readability with images and graphics. Clear and Concise Writing: → 55% of readers spend less than 15 seconds on a page. Keep your message short and impactful. Engaging Headlines: → 80% of visitors read headlines, only 20% read the rest. Craft compelling headlines to draw readers in. Effective Use of Subheadings: → 50% increase in readability with subheadings. Break up text for easier scanning. Bullet Points for Clarity: → 45% better retention with bullet points. Make key points stand out. Interactive Content Boosts Engagement: → 60% more engagement with interactive content. Incorporate quizzes, polls, and videos. Mobile Optimization is Crucial: → 70% of users read on mobile devices. Ensure your content is mobile-friendly. Personalized Content: → 60% higher engagement with personalized content. Tailor your message to your audience. Storytelling Captivates: → 80% of people remember stories. Use storytelling to make your content memorable. Are you ready to make your content more readable?

User behavior is more than what they say - it’s what they do. While surveys and usability tests provide valuable insights, log analysis reveals real interaction patterns, helping UX researchers make informed decisions based on data, not just assumptions. By analyzing interactions - clicks, page views, and session times - teams move beyond assumptions to data-driven decisions. Here are five key log analysis methods every UX researcher should know: 1. Clickstream Analysis - Mapping User Journeys Tracks how users navigate a product, highlighting where they drop off or backtrack. Helps refine navigation and improve user flows. 2. Session Analysis - Seeing UX Through the User’s Eyes Session replays reveal hesitation, rage clicks, and abandoned tasks. Helps pinpoint where and why users struggle. 3. Funnel Analysis - Identifying Drop-Off Points Tracks user progression through key workflows like onboarding or checkout, pinpointing exact steps causing drop-offs. 4. Anomaly Detection - Catching UX Issues Early Flags unexpected changes in user behavior, like sudden drops in engagement or error spikes, signaling potential UX problems. 5. Time-on-Task Analysis - Measuring Efficiency Tracks how long users take to complete actions. Longer times may indicate confusion, while shorter times can suggest disengagement.

Your website is not a book. Stop using pure black◼️for text. Pure black (#𝟬𝟬𝟬𝟬𝟬𝟬) creates a rough contrast. It makes reading fatiguing + strains the eyes. Especially on longer user-sessions. And if users are uncomfortable reading your content.. Guess what? They'r out of there. Here’s how to fix it: 𝗙𝗼𝗿 𝘁𝗲𝘅𝘁 ↳ Swap #000000 for softer shades like #333333 or #444444 𝗙𝗼𝗿 𝗯𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱𝘀 ↳ Use deep grays like #212121 ( ChatGPT uses it btw ). 𝗙𝗼𝗿 𝗮𝗰𝗰𝗲𝘀𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆 ↳ Run your color choices through a contrast checker. These subtle tweaks: ✅ Improve readability ✅ Reduce strain, and ✅ Make your site feel more polished. The easier it is to read = the longer people stay. More comfort = More conversions.

Rapid testing is your secret weapon for making data-driven decisions fast. Unlike A/B testing, which can take weeks, rapid tests can deliver actionable insights in hours. This lean approach helps teams validate ideas, designs, and features quickly and iteratively. It's not about replacing A/B testing. It's about understanding if you're moving in the right direction before committing resources. Rapid testing speeds up results, limits politics in decision-making, and helps narrow down ideas efficiently. It's also budget-friendly and great for identifying potential issues early. But how do you choose the right rapid testing method? Task completion analysis measures success rates and time-on-task for specific user actions. First-click tests evaluate the intuitiveness of primary actions or information on a page. Tree testing focuses on how well users can navigate your site's structure. Sentiment analysis gauges user emotions and opinions about a product or experience. 5-second tests assess immediate impressions of designs or messages. Design surveys collect qualitative feedback on wireframes or mockups. The key is selecting the method that best aligns with your specific goals and questions. By leveraging rapid testing, you can de-risk decisions and innovate faster. It's not about replacing thorough research. It's about getting quick, directional data to inform your next steps. So before you invest heavily in that new feature or redesign, consider running a rapid test. It might just save you from a costly misstep and point you towards a more successful solution.

We’re all about diversity, right? Well, one thing I’ve noticed is that there’s a curious lack of conversation about how to test and design for neurodiversity. We talk about how we can ensure accessibility, but what about ensuring accessibility in terms of cognitive ability? Studies show that up to 20% of the population is neurodivergent. As more information emerges about how diverse human brain function can be (and how this diversity can be the basis of many unique strengths), it’s time that we started exploring how we can ensure cognitive accessibility in digital experiences. Neurodiversity exists on a wide spectrum, everything from dyslexia to autism spectrum disorders. For researchers and businesses designing with neurodiversity in mind, I have a few tips to guide the process. 1. Be mindful of sensory thresholds when conducting research with neurodiverse users. Minimize environmental elements that could be overwhelming for individuals with sensory processing disorders, such as bright lights, intense animation, and loud sounds. 2. Keep user interfaces simple and to the point. Be intentional about creating a visual hierarchy that gives clear directives. Using legible fonts helps keep users focused. Give your neurodiverse users the option to adjust some features during their digital usability experience—font size, background color, screen contrast, etc. This takes into account the fact that neurodiversity is unique to each individual and that digital experiences will vary from user to user. 3. Throughout testing, provide clear and consistent feedback to users as they move through the digital experience. Give plenty of visual and auditory cues to actively eliminate ambiguity around what actions lead to what results. If you’re ready to start integrating these principles into your products, an accessibility audit could be a good place to start, or you could initiate a pilot project focused on enhancing cognitive accessibility. These practical steps will help your designs and applications become more accommodating for neurodiverse users.

I’ve been getting more requests for “accessible” brand and website design, where visuals, colors, and layouts are optimized for people of all abilities. Unfortunately, accessibility is often treated as a checkbox rather than a genuine commitment. Some organizations rush into changes for appearances, without fully understanding how to create an experience that truly benefits all users. Instead of treating accessibility as a checkbox, I recommend… → Understanding your community’s diverse readability and usability needs → Having an honest conversation with your team around what it’ll take to be – and maintain – WCAG compliance (remember there are 3 levels: A, AA, or AAA) → Involving users with disabilities to review your brand and test your site for insights automated tools might miss → Running accessibility audits monthly using tools like Wave or Axe, and have a plan for how to address their recommendations The truth is, building an accessible brand or website impacts more than just design. It requires additional effort from your team—training in accessible design, testing and reworking copy for readability, adding alt text to images, user testing, frequent accessibility audits, and much more to consider. Have you felt this shift, too?