E-mail List Archives
Re: SC 1.3.5 and input type=date
From: wolfgang.berndorfer
Date: Oct 30, 2023 11:51AM
- Next message: Francisco Magalhães: "Jaws"
- Previous message: Howard Kramer: "Virtual AHG 2023 starts in 7 days"
- Next message in Thread: Patrick H. Lauke: "Re: SC 1.3.5 and input type=date"
- Previous message in Thread: Dean.Vasile@outlook.com: "Re: SC 1.3.5 and input type=date"
- View all messages in this Thread
May be, I haven't yet understood the permissible bending of success criteria in the WCAG in view of inadequate browser support. Can anybody reference relevant passages?
> Whether the browser saves or presents the saved value is outside the scope of WCAG.
Does this mean that using typeÚte for birthday (bday) is no failure although the birthday is not presented effectively?
A value for *bday* is âprogrammatically determinedâ according to 1.3.5. Browsers could implement the data even in an input with typeÚte by sharing the yyyy-mm-dd to input sections for yyyy, mm and dd.
What if a common browser does not separate and support "identifying the expected meaning for form input data" with typeÚte for a birthday?
Have I missed information or is this a gray area?
- Next message: Francisco Magalhães: "Jaws"
- Previous message: Howard Kramer: "Virtual AHG 2023 starts in 7 days"
- Next message in Thread: Patrick H. Lauke: "Re: SC 1.3.5 and input type=date"
- Previous message in Thread: Dean.Vasile@outlook.com: "Re: SC 1.3.5 and input type=date"
- View all messages in this Thread