- From: John Foliot <john.foliot@deque.com>
- Date: Mon, 1 Jun 2020 13:20:20 -0500
- To: Personalization Task Force <public-personalization-tf@w3.org>
- Message-ID: <CAKdCpxwmsbstaXrkrcNmirv1eCn-ch9q5RvTds2Knim8R3q8EQ@mail.gmail.com>
For clarity, did we not agree on our call today to NOT include links to the ARIA Recommendation? I am strongly opposed to linking Personalization to ARIA, because rightly or wrongly, ARIA is perceived as being for screen readers only, and Personalization is for more than screen reader users. (I do understand that once-upon-a-time there was some thinking that *ALL* accessibility "extras" could/should be handled by ARIA, but with the unwritten rule (which the browser vendors guard zealously), that ARIA has ZERO impact on the UI, we cannot achieve that goal today. This has been discussed previously when we explored naming conventions) JF On Mon, Jun 1, 2020 at 9:35 AM Personalization Task Force Issue Tracker < sysbot+tracker@w3.org> wrote: > ACTION-60: Put in informive links - missing aria, acag, coga, and they > all external link > > https://www.w3.org/WAI/APA/task-forces/personalization/track/actions/60 > > Assigned to: Ruoxi Ran > > > > > > > > > -- *​John Foliot* | Principal Accessibility Strategist | W3C AC Representative Deque Systems - Accessibility for Good deque.com "I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"
Received on Monday, 1 June 2020 18:21:14 UTC