Firefox 57 will be less chatty to screen readers in some situations

Over the last few days, I landed two changes to Firefox which change how we expose implicit landmarks of some HTML5 elements. This is to make screen readers a bit less chatty in certain situations.

For many years, Firefox has exposed certain new HTML5 elements like <header>, <footer>, <nav>, <main>, or <aside> with their corresponding WAI-ARIA landmark semantics. This way, when authors used these elements, screen readers that already knew about WAI-ARIA landmarks would just expose these transparently and give blind and visually impaired users the benefit of easier navigation on pages.

However, over time, it has become apparent that some landmarks were over-exposed and the semantics didn’t really fit the real-world use cases. To that end, the WAI-ARIA 1.1 and HTML 5.1 specifications were updated to reflect this feedback from screen reader users.

Firefox 57, due to be released in the fall, and currently available as a Nightly build, will follow that spec and reduce chattiness for screen reader users. The two changes I worked on over the last couple of days, and the second of which I landed this morning, are:

  1. The <section> element will now only be exposed as a region landmark if it has been explicitly named via WAI-ARIA or the title attribute. So not every <section> element will be announced as a region by assistive technologies any more, only those who were named by the author.
  2. The <header> and <footer> elements will now only be exposed as header and footer, and banner and ContentInfo landmarks respectively, if these elements are direct descendants of the body tag, and therefore are scoped for the whole page. If they are descendants of other sectioning or sectioning root elements, their meaning is changed to be sections, and no landmark is exposed any more.

These are just two of several more changes that make Firefox accessibility more compatible with WAI-ARIA 1.1 and HTML 5.1. Other changes include better correctness for certain WAI-ARIA widgets and their attributes, better exposure with more modern roles on ATK/Linux, and more. Some of these changes are already in Firefox 56, which is currently in beta and will be released in a few weeks. These changes were contributed by long-time community member Joanie.

We hope you’ll enjoy these changes when they land on your desktop! 🙂

16 thoughts on “Firefox 57 will be less chatty to screen readers in some situations

    1. According to the name calculation algorithm spec, it is. Was new to me, too, and to be on the safe side, I‘d always use and recommend to use aria-label.


  1. Can you clarify “direct descendants of the body tag”? Do you mean any header or footer that is a child of the body element, or any header or footer whose nearest sectioning or sectioning-root ancestor is the body element?


  2. Do I understand it correctly that header and footer can be descendants of the body element, not just child elements? So is fine and it is announced, but isn’t. That’s reasonable.


    1. Sorry, the tags were swallowed.

      Do I understand it correctly that header and footer can be descendants of the body element, not just child elements? So body, div, header is fine and it is announced, but body, section, header isn’t. That’s reasonable.


    2. Yes. The header and footer elements can be children of sectioning and sectioning root elements as well. But only if the body elements is a direct ancestor of header or footer, these will be announced as banner or content info respectively.


    1. Unfortunately, Firefox’s support for MacOS is not complete, and due to resource constraints, this won’t change in the foreseeable future. If it works in Safari and/or Chrome on MacOS, you should be good. Firefox is best tested on Windows and Linux, using NVDA and Orca respectively.


  3. Hi Marco, its quite shitty with new Firefox and NVDA. Mozilla did a bad job. It seems, that you are copying the Politics of Microsoft Edge, publish the rubbish and look later on a11<y. I will change to Chrome.


Leave a Reply to Johnnes Cancel reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.