Accessibility
Detailing the difference between implementations to choose the most appropriate solution.
ns-selector
ns-selector
I've been listening to ns-selector
with the NVDA screenreader with Firefox on Windows 10 (apparently that's a popular combination) and I've got it to a place where I believe that it provides exactly what we are after.
I'll check it using IE11, Edge and Chrome to see if there's anything crazy happening.
The conclusion that I've come to is:
When visiting the page and not interacting with the mouse or keyboard, the screenreader will read out the page from start to finish exactly as we would.
When encountering the ns-selector
it'll read this:
This is the label This is the helper text Item one heading Item one subheading Item one paragraph
radio button not checked
clickable
Item one labelItem two heading Item two subheading Item two paragraph
radio button not checked
clickable
Item two label
When I initially interact with the page using the tab
key it'll read this:
This is the label
grouping
This is the helper text Item one labelradio button not checked
Item one heading Item one subheading Item one paragraph1 of 3
Then I use the tab
key to navigate to the next Item and it'll read this:
Item two label
radio button not checked
Item two heading Item two subheading Item two paragraph2 of 3
1.
Morning mate.
I've been listening to our ns-selector with the NVDA screenreader with Firefox on Windows 10 (apparently that's a popular combination) and I've got it to a place where I believe that it provides exactly what we are after. :thumbsup: I'll check it using IE11, Edge and Chrome to see if there's anything crazy happening.
The conclusion that I've come to is:
When visiting the page and not interacting with the mouse or keyboard, the screenreader will read out the page from start to finish exactly as we would. When reading the ns-selector
it'll read this:
ns-selector
it'll read this:This is the label This is the helper text Item one heading Item one subheading Item one paragraph radio button not checked
clickable
Item one label
clickable
Item one labelWhen I initially interact with the page using the tab
key it'll read this:
tab
key it'll read this:This is the label grouping
This is the helper text Item one label radio button not checked
Item one heading Item one subheading Item one paragraph
1 of 3
1 of 3
Then I use the tab
key to navigate to the next ns-selector
and it'll read this:
tab
key to navigate to the next ns-selector
and it'll read this:Item two label radio button not checked
Item two heading Item two subheading Item two paragraph
2 of 3
2 of 3
_blank`
1.
Using VoiceOver on iPhone
Some external page. Link. pause Opens in new window.
2.
Using VoiceOver on iPhone
Take me somewhere. Link.
3.
In this example an additional SVG image asset is used.
Using VoiceOver on iPhone
Some external page, Link.
Manually focus on the next item in the reading list.
Opens in new window.
4.
In this example an additional PNG image asset is used.
Using VoiceOver on iPhone
Some external page, opens in a new window. Link.
5.
Using VoiceOver on iPhone
Some external page, opens in a new window. Link.
6.
Using VoiceOver on iPhone
Read further information within caveat item number one. Link.
7.
Using VoiceOver on iPhone
Opens in a new window. Link.
8.
Using VoiceOver on iPhone
Some external page, opens in a new window. Link.
9.
Including aria-describedby
to associate a separated piece of content
Using VoiceOver on iPhone
Some external page. Link. pause Opens in new window.
10.
Here, I've tried to use our <ns-icon>
component in the same way, but it doesn't render the content into the DOM, if we were to use this technique, we will need to include the functionality
Using VoiceOver on iPhone
Some external page. Link
Last updated
Was this helpful?