[Bug 14419] when canvas isn't supported, or for blind users, the canvas element's content should be displayed, so excluding input types like text and select is discriminatory

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14419

Frank Olivier <franko@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |franko@microsoft.com

--- Comment #4 from Frank Olivier <franko@microsoft.com> 2011-10-11 02:13:08 UTC ---
Splitting the OR and addressing the two statements:
"when canvas isn't supported - the canvas element's content should be
displayed, so excluding input types like text and select is discriminatory"
If the UA doesn't support canvas, the 'fallback' content is displayed. At the
moment there is nothing in the spec that prohibits authors from adding input
type=text in this scenario; but I would imagine that they would create the same
solution for non-canvas UAs and a11y fallback content scenarios.

"For blind users - the canvas element's content should be displayed, so
excluding input types like text and select is discriminatory"
As Tab points out, recreating text editing in canvas is not possible; the
author would not be able to recreate all the features on the UA's platform that
aid text entry/editing.

Limiting input type=text in this scenario makes sense, as we don't want authors
created halfbaked solutions where better alternatives are clearly available. 

FWIW I have not seen any projects where authors are recreating text
input/editing with canvas.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 11 October 2011 02:13:11 UTC