E-mail List Archives
Re: How do users of physical Assistive Technologies accessscreen reader shortcuts?
From: JP Jamous
Date: Oct 6, 2016 5:07AM
- Next message: Patrick H. Lauke: "Re: Vibrating phone on invalid input entry"
- Previous message: Maxability Accessibility for all: "Re: How do users of physical Assistive Technologies access screen reader shortcuts?"
- Next message in Thread: Dan Smith: "Re: How do users of physical Assistive Technologies access screen reader shortcuts"
- Previous message in Thread: Maxability Accessibility for all: "Re: How do users of physical Assistive Technologies access screen reader shortcuts?"
- View all messages in this Thread
Dan,
One easy answer from my experience as a developer and WCAG expert. Do not touch the tabindex unless it is really necessary.
Let the browser handle this based on the DOM structure. You'd make your life and the life of your users better.
I know too many sighted developers do not get this. Some use a value of 0 and others -1. Bottom line, they are all unnecessary.
I just modified a chat app UI for a third-party that services us. Their code was terrible, I have no idea how screen readers were able to make heads and tails out of it. Every Div had a tabindex, role, and that's all they used.no P elements, headings nothing. All divs. It was horrible. The most terrible code I have ever touched in 8 years.
- Next message: Patrick H. Lauke: "Re: Vibrating phone on invalid input entry"
- Previous message: Maxability Accessibility for all: "Re: How do users of physical Assistive Technologies access screen reader shortcuts?"
- Next message in Thread: Dan Smith: "Re: How do users of physical Assistive Technologies access screen reader shortcuts"
- Previous message in Thread: Maxability Accessibility for all: "Re: How do users of physical Assistive Technologies access screen reader shortcuts?"
- View all messages in this Thread