E-mail List Archives
Regarding SC 1.3.1
From: Eilana Benish
Date: May 9, 2022 9:26AM
- Next message: chagnon@pubcom.com: "Totara LMS"
- Previous message: Sumit Patel: "Voiceover with Table"
- Next message in Thread: glen walker: "Re: Regarding SC 1.3.1"
- Previous message in Thread: None
- View all messages in this Thread
Hello everybody
I am testing a system Which provides Lessons And exercises For students.
This system Should be accessible To meet WCAG 2.0 Level A and AA
In every topic There is 10 buttons in the shape of Rounded square Icons for
each exercise, That can be navigated with the keyboard And they have labels
for screen readers To indicate The number of the exercise.
Keyboard navigation is good with the tab and shift+tab keys and the arrow
keys
The buttons are clearly labeled for the screen readers
focus visible on the buttons when navigating is good
but there is no indication with text such as tooltip or title.
The question is, is it enough two add a visible tooltip or a title- so the
text for the button can be seen with mouse hover and when a button receives
keyboard focus?
I see this implementation for example in the Gmail app for the web, when
the text for the settings button for example can be seen with mouse hover
and when that button receives keyboard focus…
The company that I am testing this application tells me that if not they
should go back to the design stage two change the design of that part…
So is this implementation like in the Gmail app meets success criteria
1.3.3 Sensory Characteristics?
https://www.w3.org/WAI/WCAG21/Understanding/sensory-characteristics.html
Thanks in advance
Eilana Benish
- Next message: chagnon@pubcom.com: "Totara LMS"
- Previous message: Sumit Patel: "Voiceover with Table"
- Next message in Thread: glen walker: "Re: Regarding SC 1.3.1"
- Previous message in Thread: None
- View all messages in this Thread