Naming things to improve accessibility

I like the this wrap-up statement from Hidde de Vries:

In modern browsers, our markup becomes an accessibility tree that ultimately informs what our interface looks like to assistive technologies. It doesn’t matter as much whether you’ve written this markup:

• in a .html file
• in Twig, Handlebars or Nunjucks
• as the <template> in a Vue Single File Component
• exported in the JSX of your React component
• outputted by a weird legacy CMS

It is which markup that determines if your site is pleasurable to experience for AT users. In short: it’s the markup that matters

As a front-end developer, you'll find yourself writing markup in lots of different places with lots of different technologies. I think it behooves you think of how best to write it regardless of where and how.

Direct Link to Article — Permalink

The post Naming things to improve accessibility appeared first on CSS-Tricks.

from CSS-Tricks https://hiddedevries.nl/en/blog/2019-04-18-naming-things-to-improve-accessibility?utm_source=CSS-Weekly&utm_campaign=Issue-360&utm_medium=email

The blog post Naming things to improve accessibility Find more on: Instant Web Site Tools.com Blog

source https://www.instant-web-site-tools.com/2019/05/01/naming-things-to-improve-accessibility/