- For keyboard support, use keyboard interface events like keyup, keydown or keypress.
- Another good practice would be to use tabindex=“0” which allows elements other than links and form elements to receive keyboard focus. It places the element in the logical navigation flow, making it behave like a link on the page.
- See to it that client-side view changes are known to screen reader users by announcing the change in page title, using ARIA live regions (ARIA live regions provide a way to programmatically show dynamic content changes such that it can be announced by assistive technologies).
Obviously these are not the only problem/solution to accessibility issues. There is much more to accessibility, maybe a topic for another few blogs. Till then try to keep up with the best practices.