‘Name, Role, Value’ requires that the name and role of user components can be understood by technology.


Users who rely on assistive technology, such as a screen reader or magnifier, rely on their technology being able to correctly understand and interact with the components of your website.

For the most part, using standard controls such as those in HTML enables most technologies to interpret and control your website. However, if you have built custom controls, it’s essential they can still be processed by assistive technology.

How to Pass ‘Name, Role, Value’

  • Ensure every component of your website has a name, role or label (this can be visible or hidden).
  • Where a component has a value (for example a radio button can be selected or unselected), the value can be determined by technology.

‘Name, Role, Value’ Tips

A common value is whether an element has focus or not at a given time, and whether that state has changed.

Elements to pay keen attention to include forms and links.

Remember, standard HTML will almost always pass 4.1.2 – Name, Role, Value without further work.

Be wary of third-party plugins or code and make sure these meet the criteria.

Run your website through a HTML validator to spot any minor coding issues to fix.

See Also

Your website has no major code errors

Parsing is the way software like web browsers and assistive technology read and understand a website. It’s important that the different technologies your users use to view your website don’t have trouble parsing your website. Parsing is all about your website’s code.

All your users will benefit from a website built on clean and modern HTML. Your website will work properly in all web browsers and on all kinds of devices, from computers to tablets to smartphones.

Your users who rely on assistive technology will benefit from a well-made website as the technology often relies on HTML parsing. Bad or broken HTML is more likely to cause parsing problems for assistive technology and so increase the chance of users leaving your website.

What to do

This is a wide-ranging guideline, one that changes with time as standards evolve. Your best protection is hiring a web designer who knows parsing well. Find one through recommendations and ask them about their approach to web standards and accessibility.

Here are the most common issues to watch out for:

  • Ensure HTML elements have complete start ( < > ) and end ( </ > ) tags where needed.
  • Nest all HTML elements correctly (for example, list objects within an ordered or unordered list).
  • Use unique Ids.
  • Check that HTML elements don’t contain duplicate attributes.


A good – though not foolproof – way to test your website is a HTML validator tool. A validator gives you an idea of how well technology can parse your website. Use it to create a list of priorities.

See also