Skip to Main Content Funka Foundation
  • Swedish
  • Search
  • We offer
  • Research projects
  • Assignments
  • What’s up
  • About us
  • Swedish
  • Search
  • We offer
    • Training
      • We are launching more courses!
      • Self-paced training
      • EAA-specific training offer
      • IAAP Professional Certification Preparation Training
        • CPACC certification preparation training
        • WAS certification preparation training
        • ADS certification preparation training
    • Document remediation
    • The missing link – the user perspective on accessibility
    • Action-based accessibility audit
  • Research projects
    • Experience2Business: Turning lived experience into entrepreneurial expertise
    • UNITY: making the justice system easier to understand
    • Approved project in Norway: crisis information for everyone
    • Digital Accessibility for people with dyscalculia
      • Survey on dyscalculia and digital services
    • New project approved: “Easier to make it right”
    • Web accessibility course for people with visual impairments
    • Accessible crisis information
    • Accessible support to victims of crime
    • Training on website feedback strengthens the voice of users
    • Increase cognitive accessibility in digital interfaces
      • Cognitive Accessibility – Insights from an important project
    • Completed projects
      • AI-based and inclusive recruitment
      • Involving users
      • Integration of web accessibility in university education in the EU
      • Nordic knowledge on web accessibility
      • Accessibility – an important part of sports
      • Funka Foundation provides expert support to EU project
      • Stuttering: in focus at last
      • Bridging the gap: Empowering UX-students to address all users’ needs
      • Consumer rights for everyone
      • Accessibility of cookie notifications
        • New research shows how cookie notifications can be more accessible
      • Accessibility in surveys
        • Make your surveys easier to manage for users
      • Expertise based on personal experience
        • Webinar: Expertise based on personal experience
      • European Political Party websites
  • Assignments
    • European policy, legislation and standards
      • Coordination of EAA enforcement
      • While waiting for EN 301 549 – our top tips
      • Accessibility support for procurers
      • What companies need to comply with EAA
      • EAA – insufficient information to consumers
      • Accessible support – new requirements under the Accessibility Act
      • PDF/UA-2 – the updated PDF accessibility standard
      • Research informs new European standards on accessibility
      • Canada adopts the EN301549 – and makes it accessible!
      • European Accessibility Act: implementation regarding e-books
      • The value of a life must be equal
    • Evaluation of the Nordic cooperation on disability
    • European research assignment on assistive technology (AT)
      • Improving assistive technology provision
    • Cognitive accessibility on museum websites
    • EU-funded study on Multimodality
    • Study on AI to support accessibility
    • Framework contract with the whole Stockholm Region
    • IAAP Nordic
    • Completed assignments
      • Access Denied – a democratic issue
      • Digital skills
        • Digital skills for inclusive employment – report published
      • EU platform publishes our paper on user involvement
      • Digital currency dialogue forum
  • What’s up
    • Newsletter
    • News
      • Accessible names from a user perspective
      • False promises about digital accessibility are spreading
      • 20 years of the UNCRPD
      • Celebrating choice – for all
      • Happy GAAD 2026!
      • Challenges in accessibility supported
      • Celebrating the Rare Disease Day – when accessibility is truly for all
      • Safety and accessibility
      • World Braille Day: Celebration or crisis?
    • Free Friday Webinars
      • Great slides are not enough to make your presentation accessible for all
      • Content on images: a common design choice with unexpected consequences
      • Accessible PDF without fixes
      • Focus: accessible content creation
      • The updated EN301549 is here!
      • The standards and the users: What is needed for a PDF to be accessible?
      • ACT rules – update on automatic and manual testing
      • Attitude – approach – accessibility
      • Accessible name – make it or break it
      • EAA – reporting and documentation requirements
      • Signed, Sealed, Accessible: accessibility in public procurement
      • InDesign styles, unlock the accessibility potential
      • Accessible research from design to dissemination
      • AI in recruitment – research results
      • EAA empowers users – the beauty of enforcement
      • When design kills usability – meet the custom cursor
      • Cognitive accessibility in digital interfaces – insights from users
      • Captions, subtitles or transcripts
      • Getting tables right: Clear, accessible, and effective
      • Accessible input fields: From code to user experience
      • Cybersecurity + Accessibility = True
      • EAA Three months on
      • Accessible e-learning
      • Serving all customers: Accessible support services and the European Accessibility Act
      • No barriers, just bar charts: Chart accessibility made easy
      • European standards to support EAA – update
      • Accessible surveys: insights and best practices
      • Best things in life are free – Part 2: Free tools for mobile app accessibility testing
      • Accessible cookie banners: research insights and best practices
      • User involvement: research, best practices and standards
      • The best things in life are free – Free tools for accessibility testing
      • Document remediation – setting up your workflow
      • Understanding Non-Digital Information under the European Accessibility Act
      • Deliver UX and design to developers
      • Formatting for accessibility – and how to make it easier
      • ALT-text – how am I supposed to write it?
      • Brain-friendly web design for a stress-free online experience
      • Five easy steps to improve document accessibility!
      • European Accessibility Act – these are the requirements
      • Accessibility in social media
      • The untapped resource of accessibility features
    • Smart guides
  • About us
    • Join our network of testers
    • Columns
      • Dyslexia, fonts and finding out what works
      • Read aloud text also needs to be clear
      • Lost in translation: decoding yet another ticket machine
      • The worst is …
      • Digital Christmas stress is not inevitable
      • The curse of the custom cursor
      • The good, the bad and the unreadable
      • Start where you are
      • Why are we not getting across?
      • It should be the other way around
      • To think and talk like your customers
      • The never-ending hype of AI
      • “No gritting or snow clearance”
      • An adapted car makes travelling easier and more independent
      • Adolf Ratzka has left us
      • I don’t want to work on creating accessible documents
      • High time to reconsider the use of timers
      • The user at the centre – or possibly in the back seat?
    • Accessibility statement
    • Privacy policy
    • Board of Directors
  • Newsletter
  • News
    • Accessible names from a user perspective
    • False promises about digital accessibility are spreading
    • 20 years of the UNCRPD
    • Celebrating choice – for all
    • Happy GAAD 2026!
    • Challenges in accessibility supported
    • Celebrating the Rare Disease Day – when accessibility is truly for all
    • Safety and accessibility
    • World Braille Day: Celebration or crisis?
  • Free Friday Webinars
    • Great slides are not enough to make your presentation accessible for all
    • Content on images: a common design choice with unexpected consequences
    • Accessible PDF without fixes
    • Focus: accessible content creation
    • The updated EN301549 is here!
    • The standards and the users: What is needed for a PDF to be accessible?
    • ACT rules – update on automatic and manual testing
    • Attitude – approach – accessibility
    • Accessible name – make it or break it
    • EAA – reporting and documentation requirements
    • Signed, Sealed, Accessible: accessibility in public procurement
    • InDesign styles, unlock the accessibility potential
    • Accessible research from design to dissemination
    • AI in recruitment – research results
    • EAA empowers users – the beauty of enforcement
    • When design kills usability – meet the custom cursor
    • Cognitive accessibility in digital interfaces – insights from users
    • Captions, subtitles or transcripts
    • Getting tables right: Clear, accessible, and effective
    • Accessible input fields: From code to user experience
    • Cybersecurity + Accessibility = True
    • EAA Three months on
    • Accessible e-learning
    • Serving all customers: Accessible support services and the European Accessibility Act
    • No barriers, just bar charts: Chart accessibility made easy
    • European standards to support EAA – update
    • Accessible surveys: insights and best practices
    • Best things in life are free – Part 2: Free tools for mobile app accessibility testing
    • Accessible cookie banners: research insights and best practices
    • User involvement: research, best practices and standards
    • The best things in life are free – Free tools for accessibility testing
    • Document remediation – setting up your workflow
    • Understanding Non-Digital Information under the European Accessibility Act
    • Deliver UX and design to developers
    • Formatting for accessibility – and how to make it easier
    • ALT-text – how am I supposed to write it?
    • Brain-friendly web design for a stress-free online experience
    • Five easy steps to improve document accessibility!
    • European Accessibility Act – these are the requirements
    • Accessibility in social media
    • The untapped resource of accessibility features
  • Smart guides
A web developer with orange headphones on their head. Photo.

Accessible names from a user perspective

An accessible name is the programmatic label that assistive technology use to identify an element. It tells users what a button, link, form field, or other interactive control is called, even when that name isn’t visible on screen.

In accessibility, conversations about accessible names often focus on screen readers. Buttons need labels, images need alternative text, and form fields need names.

All of this is true, but screen readers are only part of the story.

Accessible names are also used by voice control software, Braille displays, switch control solutions and other assistive technology. The same accessible name can be perceived very differently depending on how someone interacts with a page. What works well for one group of users may create challenges for another.

Accessible names and voice control

Different users experience accessible names in different ways. Some users only hear them through a screen reader. Others both see the interface and hear speech output. Users with motor impairmens and users who have reading- and writing impairments who primarily interact visually may depend on accessible names, based on what assistive technology they prefer.

Voice control users are a good example. They see what is written on the screen, but when they speak a command, the software matches what they say against the accessible name (at code level) rather than the visible label.

This relationship between visible labels and accessible names is one of the reasons behind the “Label in Name” requirement in EN 301 549 and WCAG.

The criterion requires that the accessible name contains the visible label so that users can speak what they see and successfully interact with controls.

Imagine a menu button with no visible label, only the familiar hamburger icon. Most voice control users would probably think of it as a menu and try a command such as “Click menu”. However, if the accessible name is “Open main navigation panel”, the software may be looking for something entirely different.

From the user’s perspective there is no obvious way to know this. The expected command may fail, even though the button has an accessible name. Instead, the user might need to display labels, show numbered markers or use a navigation grid to activate the control. The task is still possible, but it requires a lot more effort.

Illustrated cartoon caracter looking like a hamburger menu, asking ”What did you call me?” Speech bubbles: ”Toggle navigation”, ”Open main navigation drawer”, ”Open mobile menu”, ”hamburgermenu”.

Beyond “Label in Name”

Meeting the requirement Label in name is important, but it isn’t always enough.

Different voice control solutions match names in different ways. Some use exact matching and expect users to speak the entire accessible name. Apple’s Voice Control on iOS and macOS often work this way. Others can match the beginning of a name, while some use partial or fuzzy matching and can find words elsewhere in the label. In our testing, Android’s Voice Access often behaved more like this. Some solutions can also take semantic information into account.

The result is that the position of words inside a name can affect how easy it is to use.

Consider a search field with the accessible name “Enter your search text”. The word “search” is present, so the control may satisfy the Label in Name-requirement. However, some voice control solutions may struggle because the important word appears late in the name, while others may expect users to say the entire phrase.

Another example is a menu icon with the accessible name “Toggle navigation”. The control meets the “Label in Name” requirement, but how many users would naturally think to say “Toggle navigation” when they want to open a menu? Most would probably try “Menu” or “Open menu” first.

These examples illustrate the difference between compliance and real accessibility. A control can satisfy minimum legal accessibility requirements and still make it hard or almost impossible to use as intended.

Do screen reader users need all that extra information?

It is common to add additional words to accessible names in an attempt to provide more context. The intention is usually good. However, screen readers already provide a lot of information through semantics. A correctly coded search field is announced as a search field, an expandable menu can communicate its state through attributes such as aria-expanded, and checkboxes can communicate whether they are checked or unchecked.

As a result, the extra wording added to accessible names is not always necessary. Sometimes it simply makes the name longer and, to be honest, no one enjoys an unnecessarily chatty screen reader.

Long accessible names can also create challenges for Braille display users. Braille displays have a limited number of cells, and some mobile displays can be very small. When names become unnecessarily long, more of the display is used by information that may not actually help the user.

When users see one thing and hear another

Many assistive technology users both see and hear the interface. They may look at a button labelled “Menu” while hearing “Open main navigation”. The visible label says one thing while the accessible name says another.

When the extra wording doesn’t add meaningful information, users are left with more information to process without a clear benefit. The result can be increased cognitive load.

What can designers and developers do?

One of the simplest ways to improve accessible names is to think about them early in the design process.

For designers, that often means using visible labels whenever possible instead of relying on icons alone. Visible labels make controls easier to understand and provide a clear foundation for accessible names. When a control doesn’t have a visible label, designers can help by defining the intended accessible name and documenting it through annotations.

For developers, it means understanding how accessible names are calculated and being careful when using ARIA attributes that replace native labels.

It’s particularly important to understand that aria-label and aria-labelledby override native labels. If a button already has a visible label, adding an aria-label doesn’t add information to the accessible name. It replaces it.

When additional explanation is needed, aria-describedby is often a better option. Rather than changing the accessible name, it provides supplementary information that screen readers can announce after the name. Users who need that additional context can access it, while the accessible name itself remains short and predictable.

Accessible names are part of the user experience

Accessible names are often treated as something that only matters to screen reader users. In reality, they affect a much wider group of people, including voice control users, Braille display users and people who combine multiple assistive technology.

The same accessible name can be experienced in very different ways depending on the technology being used. That’s why accessible names are not just a technical requirement. They’re part of the user experience.

Keeping them simple, keeping them consistent and thinking carefully before giving a control an accessible name that differs from its visible label can make a big difference.

Recording from our Free Friday webinar series: “Accessible names – make it or break it” with Malin Hammarberg

Contact us

Funka Foundation
Ekhammarkroken 3
SE-184 63 AAkersberga
Sweden

info@funkafoundation.org

Follow us

  • LinkedIn
  • X (Twitter)
  • YouTube

Learn more

  • Subscribe to our newsletter
  • Proud leader of IAAP Nordic
  • Accessibility statement

© 2026 Stiftelsen Funka

The Funka Foundation is registered with and supervised by the Stockholm County Administrative Board. VAT: SE802425236601. Registration/organisational number: 802425-2366