[Bug 9190] New: What effects do fillText and strokeText have on the accessibility fallback (ADOM?)? Should they take a default to also adding it, as by canvas.appendChild(document.createTextNode(s))? (Then maybe add a 5th parameter to allow turning it off) -jJ

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

           Summary: What effects do fillText and strokeText have on the
                    accessibility fallback (ADOM?)?  Should they take a
                    default to also adding it, as by
                    canvas.appendChild(document.createTextNode(s))?  (Then
                    maybe add a 5th parameter to allow turning it off) -jJ
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#text
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


Section: http://www.whatwg.org/specs/web-apps/current-work/#text

Comment:
What effects do fillText and strokeText have on the accessibility fallback
(ADOM?)?  Should they take a default to also adding it, as by
canvas.appendChild(document.createTextNode(s))?  (Then maybe add a 5th
parameter to allow turning it off) -jJ

Posted from: 32.97.110.59


-- 
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 Thursday, 4 March 2010 21:27:30 UTC