@StommePoes that is a good point, and something I wonder also. I still think it is better to read aloud "Heading Level 6" then <h6> or "Paragraph" instead of <p> for a question like "Which is the least semantic of the following HTML tags?" though
that's up to the reader anyway, what it says when it encounters something.
But my question is, why can sighties know that a list of questions means each question is a question?
and why can't SR users figure that out the same way?
It means sighties can skim the questions as they already know they're a question while someone skimming them with an SR gets the repetition of "question, question, question"
@stevefaulkner I believe the <p> is one of the answers of a multiple choice question.
Why did the people at work put an onClick listener on the h3 of our calendar? why? why? arg.
[heidi] hi all. Re: consistent identification (3.2.4), does styling influence this at all? i.e. tabs that look differently across pages, but are all marked up consistently as tabs with aria
My first time running into tabs, they were perfectly JS'd and marked up, but I (and the screen reader user who was paired up with me) struggled badly on them: they were styled to look like links for some reason, so I was tabbing and shift-tabbing like mad and feeling even more the moron than i normally do. The SR user had no idea how tabs worked.
It might depend on the particular widget. A navigation menu looking wildly different per page could be a fail just on cognitive reasons.
There are those who would ask: would someone, because they have a disability, be unable to use this <whatever> because of this visual inconsistancy? I'm personally broader than that, but that's probably the question most people would have you ask yourself/your team.
it is, and it might require user testing-- did users with disabilities consistently fail to be able to use the <whatever>? Or consistently were slowed/prone to mistakes they otherwise would not make?
There is btw a service for (remote-only) testing with users with disabilities... via Loop11, they've hooked up with Knowability to offer a version of the usual Loop11 remote testing but here with users with disabilities.
@StommePoes for the quiz, it’s more I’m trying to control what available answers are read aloud (as HTML content), not how certain HTML elements are read when encountered (see question 5 for example) https://jpdevries.github.io/a11y-quiz/