Please pick the day that this change takes effect
| JAN 1996 |
|---|
| Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
|
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
This is how a screen reader would read this page to a user:
image image image
Please pick the day that this change takes effect
JAN 1996
Sun Mon Tue Wed Thu Fri Sat
image 1 Monday image 2 Tuesday image 3 Wednesday image 4 Thursday image 5 Friday image 6 Saturday
image 7 Sunday image 8 Monday image 9 Tuesday image 10 Wednesday image 11 Thursday image 12 Friday image 13 Saturday
image 14 Sunday image 15 Monday image 16 Tuesday image 17 Wednesday image 18 Thursday image 19 Friday image 20 Saturday
image 21 Sunday image 22 Monday image 23 Tuesday image 24 Wednesday image 25 Thursday image 26 Friday image 27 Saturday
image 28 Sunday image 29 Monday image 30 Tuesday image 31 Wednesday
image image
If viewed with a
screen reader it would be hard to connect the day of the week with
the particular day of the month on which it fell. Many screen
readers can not read individual columns. Because the user is
forced to read this page one row at a time, there is no easy way
to tell, for example whether the 23rd is a Sunday, Monday,
Tuesday etc.
Have each cell of the table
present both the day of the month, for example 23, and the name
of the day itself, for example Sunday. We wanted to front-load
each entry with the information the user might need first. In
this way, if a person were using a screen reader to find the 23rd
day of the month, he or she could rapidly skim over the unwanted
dates by pressing the right arrow after the number was read and
before the day name had been spoken. In this way, the user would
not have to listen to each entire entry preceding the 23rd.
However, we found that we couldn't fit the date and the complete
day names on the line without the right-most columns scrolling
off of the screen.
Return to the Pick a Day rationale
