Sii Poland

SII UKRAINE

SII SWEDEN

Back

Sii Poland

SII UKRAINE

SII SWEDEN

Back

20.11.2026

Accessibility starts with letters – how form and content shape the user experience

20.11.2026

Dostępność zaczyna się od liter – jak forma i treść wpływają na doświadczenie użytkownika

Digital accessibility, often abbreviated as a11y, is about designing and building websites and web applications that everyone can use, including people with disabilities.

When creating digital content – social media posts or mobile applications – creators increasingly pay attention to headings, document structure, and the clarity of the message, as these elements directly impact how comfortably information can be consumed.

Less often, however, they reflect on:

  • spelling,
  • sentence structure,
  • font choice,
  • or a seemingly minor detail – the use of uppercase and lowercase letters.

Understandable content as the foundation of communication

The way we present textual content directly affects whether users can read, understand, and interact with it.

On one hand, we aim to make websites and mobile apps visually appealing – with graphics, colors, and design elements that enhance the experience for sighted users. On the other hand, content itself – especially its simplicity or complexity – plays a crucial role in shaping a brand’s image, establishing expertise, and positioning a company as thoughtful and user-focused.

When creating accessible content, it’s important to recognize that users perceive the world differently.

Some cannot see certain or any colors, have visual impairments, or require adjustments such as larger text or higher contrast. Others, due to cognitive challenges, may struggle with complex sentence structures or ambiguous wording. Still others rely on screen readers, which convert text into speech and must preserve meaning and proper reading order within a webpage or application.

Balancing all these needs is challenging – for UX designers, content creators, and software testers alike. Testers, in particular, are responsible for ensuring that applications meet accessibility requirements, are user-friendly, and free of defects.

Preventing accessibility issues in content and language

To avoid common accessibility issues early in the design and content creation process, it’s important to consider:

  • font readability and scalability,
  • appropriate color choices and sufficient contrast,
  • plain language,
  • proper use of uppercase and lowercase letters,
  • clear explanations of abbreviations and consistent communication.

Typography and text scaling on the web

In web design, text scaling is mainly controlled through CSS.

To ensure accessibility, developers should be aware of potential pitfalls:

  • Absolute units (px, pt): Pixels are fixed units. If font sizes are defined in px, browsers strictly follow these settings, ignoring user preferences. This makes reading difficult for people with low vision and violates WCAG 1.4.4 (Resize Text link: Understanding Success Criterion 1.4.4: Resize Text | WAI | W3C).
  • Relative units (rem, em, %): Using relative units like rem, which refer to the root font size, allows text to scale consistently without breaking layouts.
  • Text resizing: According to WCAG guidelines, text (excluding captions and images of text) must be resizable up to 200% without assistive technologies and without loss of content or functionality. In practice, both text and non-text elements should be responsive and adaptable to user preferences.

Additionally, modern standards introduce Reflow (WCAG 1.4.10 – link: Understanding Success Criterion 1.4.4: Resize Text | WAI | W3C). This ensures that when a page is zoomed (e.g., up to 400% on desktop), content reflows so users do not have to scroll in both directions simultaneously – a significant barrier for people with low vision.

Mobile applications and text scaling

Designing for mobile devices requires a different approach. In native apps (iOS, Android), scaling is controlled by the operating system and user preferences – not CSS.

  • iOS and Dynamic Type: Apple’s Dynamic Type lets users select their preferred text size. Developers must support this using built-in text styles (e.g., .body, .headline) or tools like UIFontMetrics. Ignoring these settings prevents users from enlarging text.
  • Android and SP (Scale-independent Pixels): Android uses SP units, which respect user scaling preferences. Using DP instead is a mistake, as it blocks dynamic resizing.

Common accessibility issues on mobile include fixed-height containers and lack of scrollability. When text is enlarged, but containers don’t adapt (e.g., missing wrap_content or proper scroll views), content may be cut off or overlap with other elements.

Uppercase letters and assistive technologies

In Polish, uppercase letters have clearly defined uses – at the beginning of sentences, in proper names, and in abbreviations. Problems arise when uppercase letters are overused, such as in the middle of words or entire sentences – a common practice in marketing to attract attention.

From an accessibility perspective, this can do more harm than good.

Screen reader users experience text differently. These tools interpret and convert text into speech, and proper structure and formatting are essential.

Overusing uppercase letters can lead to:

  • words being spelled out instead of read naturally
  • incorrect interpretation of meaning or language
  • distorted pronunciation, making content harder to understand

This is especially problematic for words with internal capitalization, such as product or feature names. For example, “MRI Scanner” might be read as “Mister Scanner,” completely altering its meaning.

Plain language matters

Accessibility is not just about font size – it’s also about clarity. Plain language is a cornerstone of inclusive communication.

Key principles include:

  • using short sentences to improve comprehension,
  • writing in an active voice and natural tone,
  • avoiding complex vocabulary or replacing jargon with familiar terms,
  • structuring content with headings, bullet points, and logical paragraphs.

These practices support not only users with cognitive challenges but also screen reader users navigating content.

Simplifying with AI tools

Artificial intelligence tools such as Microsoft Copilot, ChatGPT, and Gemini are increasingly being used in the content creation process. They can support authors by simplifying language, shortening overly long sentences, explaining technical concepts, correcting language errors, and suggesting clearer, more user-friendly headings.

AI can also assist in creating alternative text for images, checking terminology consistency, and identifying passages that may be difficult for readers to understand. However, it is important to remember that these tools do not replace expertise in digital accessibility or human judgment.

Content generated with AI should always be reviewed for factual accuracy, compliance with plain language principles, and alignment with the real needs of users, including people who rely on assistive technologies.

The greatest benefits are achieved when artificial intelligence serves as a support tool for the author rather than the sole source of content creation or evaluation.

How to test typography for accessibility

Accessibility testing should begin at the design stage – it can eliminate up to 70% of issues before development.

Basic test method:

  1. Open the page in a browser.
  2. Press Ctrl + Plus (Windows/Linux) or Cmd + Plus (Mac).
  3. Zoom in to 200%.

Check:

  • Is all text visible?
  • Is there horizontal scrolling?
  • Can navigation still be used?
  • Do forms function correctly?
  • Are buttons accessible and unobstructed?

Additional methods:

  • Tools like WAVE (link: WAVE Web Accessibility Evaluation Tools) help analyze heading structure, color contrast, and layout readability.
  • Headings Map (link: HeadingsMap – Microsoft Edge Addons) quickly verifies whether document structure is logical.
  • Testing with screen readers (NVDA, VoiceOver, TalkBack) helps identify issues with capitalization, reading order, and missing alternative text.
Blog Testing Lab Desktop  - Accessibility starts with letters – how form and content shape the user experience

Testing & QA

Ensure the quality, performance, and security of your software with our testing and test automation services.

Testing&QA offering

Summary

At first glance, typography may seem like simply choosing an attractive typeface. In digital accessibility, however, it involves careful management of scaling, attention to technical compatibility with assistive technologies, and consistent use of plain language principles.

Accessibility is an ongoing process – every change in an application can affect how content is perceived. That’s why regular testing and audits are essential to building an inclusive web.

By approaching design with empathy and awareness of diverse user needs, we can create solutions that make digital experiences easier – and better – for everyone.


5/5
Rating
5/5

Leave a comment

Your email address will not be published. Required fields are marked *

You might also like

SUBSCRIBE AND DON'T FALL BEHIND

Blog Newsletter

Show results
Join us Contact us

Ta treść jest dostępna tylko w jednej wersji językowej.
Nastąpi przekierowanie do strony głównej.

Czy chcesz opuścić tę stronę?