E-mail List Archives
Re: Relationship between WCAG and the ARIAinHTMLspecification
From: Steve Green
Date: Aug 7, 2023 11:13AM
- Next message: Steve Green: "Re: Error message summaries, alerts and focus"
- Previous message: Nick Bromley: "Re: Error message summaries, alerts and focus"
- Next message in Thread: glen walker: "Re: Relationship between WCAG and the ARIA in HTML specification"
- Previous message in Thread: tim.harshbarger@deque.com: "Re: Relationship between WCAG and the ARIA inHTMLspecification"
- View all messages in this Thread
It's about minimising the amount of work we need to do. I am suggesting we might start by testing with a combination we expect will exhibit a problem. If it doesn't, there probably isn't much point testing other combinations.
Perhaps "obscure" was the wrong word. I was thinking more of some of the cheaper assistive technologies that perhaps may not handle invalid code nicely. We don't generally test with these because it's difficult enough to test with all the top-end products. But people still use the cheaper products.
And who is to say what proportion of products or combinations need to exhibit a problem before we can report it as a problem? WCAG is silent on this.
Steve
- Next message: Steve Green: "Re: Error message summaries, alerts and focus"
- Previous message: Nick Bromley: "Re: Error message summaries, alerts and focus"
- Next message in Thread: glen walker: "Re: Relationship between WCAG and the ARIA in HTML specification"
- Previous message in Thread: tim.harshbarger@deque.com: "Re: Relationship between WCAG and the ARIA inHTMLspecification"
- View all messages in this Thread