WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: What are the semantics in html?

for

From: R.U. Steinberg
Date: Jul 9, 2020 9:46AM

Different screen readers have different support for ARIA and not all
assistive technology users can afford to upgrade their systems to the
latest versions of things.

I agree with Mike that semantically correct, native HTML is best. Something
like <button> has built in functionality and is easily recognizable by
assistive technology compared to <span role="button">



On Thu, Jul 9, 2020 at 9:40 AM Moore,Michael (Accessibility) (HHSC) <
<EMAIL REMOVED> > wrote:

> Hi Vsevolod,
>
> You asked what semantics are in HTML.
>
> The simplest answer is that semantics tell you what something is.
>
> HTML elements for paragraphs, links, headings, lists, list items, tables,
> data cells, header cells, different types of form fields and other objects
> all exist to provide user agents like browsers and screen readers with
> information that allows them to provide useful information about the
> structure and nature of the object. Browsers do this through the default
> visual display of the item and screen reading software conveys this
> information through sound or braille.
>
> This information makes it easier for the user to navigate through the
> page, understand how different items are related, and how to interact with
> controls, links and form fields.
>
> In cases where an object is created using elements that do not provide
> information about what it is. "Non-Semantic" elements, then the developer
> can provide that information through ARIA role attributes. Using elements
> that provide the meaning without the need for ARIA role attributes is
> preferred but some frameworks and code libraries don't properly use the
> markup. This does not make them inaccessible or non-compliant with WCAG but
> the additional role attributes need to be present and need to be correct.
> > > > >