Great post! I don't get why the screen readers don't just care about the HTML though. How do they hook into the page? PS. The NVDA screenshots are out of order.
Screen readers typically look to the Accessibility Tree, a parallel structure to the DOM which I should have mentioned. You can read up on how that works here: smashingmagazine.com/2015/03/web-a...
CSS can impact what gets into the Accessibility Tree, like when display: none hides content from everyone. There are some intricacies happening here that the Chrome team said they were trying to avoid, but NVDA is showing otherwise. That's why it's so important to test in assistive technologies–to see what the potential impact would be on users.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great post! I don't get why the screen readers don't just care about the HTML though. How do they hook into the page? PS. The NVDA screenshots are out of order.
Thanks for the tip, I've fixed the images!
Screen readers typically look to the Accessibility Tree, a parallel structure to the DOM which I should have mentioned. You can read up on how that works here: smashingmagazine.com/2015/03/web-a...
CSS can impact what gets into the Accessibility Tree, like when
display: nonehides content from everyone. There are some intricacies happening here that the Chrome team said they were trying to avoid, but NVDA is showing otherwise. That's why it's so important to test in assistive technologies–to see what the potential impact would be on users.