E-mail List Archives
Re: landmarks/regions
From: Steve Green
Date: Oct 5, 2021 10:01PM
- Next message: Steve Green: "Re: interface has a search bar that is actually a button. WHY?????"
- Previous message: Jerra Strong: "UNLV Hiring Accessibility Specialist"
- Next message in Thread: Glen Walker: "Re: landmarks/regions"
- Previous message in Thread: David Engebretson Jr.: "Re: landmarks/regions"
- View all messages in this Thread
I have just done a quick test with JAWS 2019, JAWS 2021 and NVDA 2021. I don't get the same results as you, but I get different results with each screen reader when testing the same page. All the landmarks are in the accessibility tree, so it seems that the screen readers are choosing to ignore some of them.
There are a lot of permutations of html element, "role" attribute and presence or absence of an accessible name, so quite a bit of testing will be required to work out what is happening unless the screen reader vendors have published anything in the release notes.
We always test for the use of landmarks when doing a WCAG audit, but we don't use a screen reader to do so - we use a bookmarklet and manual code inspection.
Steve Green
Managing Director
Test Partners Ltd
- Next message: Steve Green: "Re: interface has a search bar that is actually a button. WHY?????"
- Previous message: Jerra Strong: "UNLV Hiring Accessibility Specialist"
- Next message in Thread: Glen Walker: "Re: landmarks/regions"
- Previous message in Thread: David Engebretson Jr.: "Re: landmarks/regions"
- View all messages in this Thread