Feature Links accessibility validation

Open Malvoz opened this issue 4 years ago • 1 comments

Ensure feature links work and make sense to keyboard and screen reader users: https://maps4html.org/experiments/linking/features/

It might be a good idea to produce some questions for a tester, similar to https://github.com/Maps4HTML/Web-Map-Custom-Element/issues/335?

Nov 30 '21 07:11 Malvoz

Now that features links are focused on activation (https://github.com/Maps4HTML/Web-Map-Custom-Element/issues/580), their featurecaptions are announced together with the link role which may be confusing to users since they've just activated that link. Question is if #580 was the right thing to do, and if so, should it be conveyed to users that they've pressed the link already? aria-pressed is only valid on buttons. Perhaps aria-current (whether set to "true" or "location") is appropriate, or even aria-disabled?

But maybe focusing the features (the feature links) themselves is not the correct thing to do after all, considering that with https://github.com/Maps4HTML/Web-Map-Custom-Element/pull/636 it may make more sense than before to focus the map container?

Jan 10 '22 05:01 Malvoz